Changeset a0ed201

Timestamp:

10/21/2022 07:05:59 PM (18 months ago)

Author:

David Bryant <davidbryant@…>

Branches:

11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/update-glibc

Children:

2ebdd8c, 6219892, ad85e5b, fc60dac

Parents:

eaf26ea

Message:

Edited fpr idiom and style. Broke up a couple of run-on sentences.
Mr. Webster says it's "up-front". Reworked one sentnece to avoid
using a colon after the verb "to be".

File:

• chapter01/askforhelp.xml (modified) (7 diffs)

chapter01/askforhelp.xml

@@ -14 +14 @@
   this book, please check the FAQ page at <ulink url="&faq-root;#generalfaq"/>.
   Questions are often already answered there. If your question is not
-  answered on this page, try to find the source of the problem. The
+  answered on that page, try to find the source of the problem. The
   following hint will give you some guidance for troubleshooting:
   <ulink url="&hints-root;errors.txt"/>.</para>
@@ -24 +24 @@
   assistance through the mailing lists and IRC (see the <xref
   linkend="ch-intro-resources"/> section of this book). However,
-  we get several support questions every day and many of them can be easily
-  answered by going to the FAQ and by searching the mailing lists first.
-  So, for us to offer the best assistance possible, you need to do some
-  research on your own first. That allows us to focus on the more unusual
+  we get several support questions every day, and many of them could have been easily
+  answered by going to the FAQ or by searching the mailing lists first.
+  So, for us to offer the best assistance possible, you should first do some
+  research on your own. That allows us to focus on the more unusual
   support needs. If your searches do not produce a solution, please include
-  all relevant information (mentioned below) in your request for help.</para>
+  all the relevant information (mentioned below) in your request for help.</para>
 
   <sect2>
@@ -35 +35 @@
 
     <para>Apart from a brief explanation of the problem being experienced,
-    the essential things to include in any request for help are:</para>
+    any request for help should include these essential things:</para>
 
     <itemizedlist>
@@ -51 +51 @@
       </listitem>
       <listitem>
-        <para>The exact error message or symptom being received</para>
+        <para>The exact error message, or a clear decription of the problem</para>
       </listitem>
       <listitem>
@@ -61 +61 @@
       <para>Deviating from this book does <emphasis>not</emphasis> mean that
       we will not help you. After all, LFS is about personal preference.
-      Being upfront about any changes to the established procedure helps us
+      Being up-front about any changes to the established procedure helps us
       evaluate and determine possible causes of your problem.</para>
     </note>
@@ -85 +85 @@
     the <command>configure</command> script and the <command>make</command>
     run can be helpful. It is not necessary to include the entire output, but
-    do include enough of the relevant information. Below is an example of the
-    type of information to include from the screen output from
-    <command>make</command>:</para>
+    do include all of the relevant information. Here is an example of the
+    type of information to include from the <command>make</command> screen
+    output.</para>
 
 <screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
@@ -113 +113 @@
 <screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
 
-    <para>This is not enough information to properly diagnose the problem
+    <para>This is not enough information to diagnose the problem,
     because it only notes that something went wrong, not
     <emphasis>what</emphasis> went wrong. The entire section, as in the
     example above, is what should be saved because it includes the command
-    that was executed and the associated error message(s).</para>
+    that was executed and all the associated error messages.</para>
 
     <para>An excellent article about asking for help on the Internet is
     available online at <ulink
-    url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read and
-    follow the hints in this document to increase the likelihood of getting
+    url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read this document,
+    and follow the hints. Doing so will increase the likelihood of getting
     the help you need.</para>