Changeset 2ebdd8c

Timestamp:

10/21/2022 10:30:09 PM (18 months ago)

Author:

Thomas Trepl (Moody) <thomas@…>

Branches:

multilib

Children:

ebe10f6

Parents:

a8af0c8 (diff), a0ed201 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Automatic merge of trunk into multilib

Files:

• chapter01/askforhelp.xml (modified) (7 diffs)
• prologue/errata.xml (modified) (1 diff)

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>
 

prologue/errata.xml

@@ -14 +14 @@
   and enhanced. Security warnings and bug fixes may become available after
   the LFS book has been released. To check whether the package versions or
-  instructions in this release of LFS need any modifications to accommodate
-  security vulnerabilities or other bug fixes, please visit
+  instructions in this release of LFS need any modifications—to repair
+  security vulnerabilities or to fix other bugs—please visit
   <ulink url="&errata;"/>
   before proceeding with your build. You should note any
-  changes shown and apply them to the relevant section of the book as you
-  progress with building the LFS system.</para>
+  changes shown and apply them to the relevant sections of the book as you
+  build the LFS system.</para>
 
   <para>In addition, the Linux From Scratch editors maintain a list of security
-  vulnerabilities discovered after a book was released. To check whether there
-  are any active security vulnerabilities, please visit
-  <ulink url="&secadv;"/> prior to proceeding with your build. You should note
-  any advisories and perform the steps to fix any security vulnerabilities as
-  you progress with building the LFS system.</para>
+  vulnerabilities discovered <emphasis>after</emphasis> a book has been released. To see
+  whether there  are any known security vulnerabilities, please visit
+  <ulink url="&secadv;"/> before proceeding with your build. You should also continue
+  to consult the advisories, and fix any security vulnerabilities, even
+  when the LFS system has been completely constructed.</para>
 
 </sect1>