Fix English idiom / clarify "General Instructions" section.

1 files changed, 20 insertions, 21 deletions

diff --git a/part3intro/generalinstructions.xml b/part3intro/generalinstructions.xml
index ac2bcc675..f3285bc17 100644
--- a/part3intro/generalinstructions.xml
+++ b/part3intro/generalinstructions.xml
@@ -11,29 +11,29 @@
 
   <title>General Compilation Instructions</title>
 
-  <para>When building packages there are several assumptions made within
-  the instructions:</para>
+  <para>Here are some things you should know about building each package:</para>
 
   <itemizedlist>
 
   <listitem>
-    <para>Several of the packages are patched before compilation, but only when
+    <para>Several packages are patched before compilation, but only when
     the patch is needed to circumvent a problem. A patch is often needed in
-    both this and the following chapters, but sometimes in only one location.
+    both the current and the following chapters, but sometimes, when the same package
+    is built more than once, the patch is not needed right away.
     Therefore, do not be concerned if instructions for a downloaded patch seem
     to be missing.  Warning messages about <emphasis>offset</emphasis> or
     <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do
-    not worry about these warnings, as the patch was still successfully
+    not worry about these warnings; the patch was still successfully
     applied.</para>
   </listitem>
 
   <listitem>
-    <para>During the compilation of most packages, there will be several
-    warnings that scroll by on the screen. These are normal and can safely be
-    ignored.  These warnings are as they appear&mdash;warnings about
+    <para>During the compilation of most packages, some
+    warnings will scroll by on the screen. These are normal and can safely be
+    ignored.  These warnings are usually about
     deprecated, but not invalid, use of the C or C++ syntax. C standards change
-    fairly often, and some packages still use the older standard. This is not a
-    problem, but does prompt the warning.</para>
+    fairly often, and some packages have not yet been updated. This is not a
+    serious problem, but it does cause the warnings to appear.</para>
   </listitem>
 
   <listitem>
@@ -69,25 +69,25 @@
         symbolic link to <command>gawk</command>.</para></listitem>
 
         <listitem override='bullet'><para><command>/usr/bin/yacc</command> is a
-        symbolic link to <command>bison</command> or a small script that
+        symbolic link to <command>bison</command>, or to a small script that
         executes bison.</para></listitem>
 
       </itemizedlist>
     </important>
 
     <important>
-      <para>To re-emphasize the build process:</para>
+      <para>Here is a synopsis of the build process.</para>
 
       <orderedlist numeration="arabic" spacing="compact">
         <listitem>
           <para>Place all the sources and patches in a directory that will be
-          accessible from the chroot environment such as
+          accessible from the chroot environment, such as
           <filename class="directory">/mnt/lfs/sources/</filename>.<!-- Do
           <emphasis>not</emphasis> put sources in
           <filename class="directory">/mnt/lfs/tools/</filename>. --></para>
         </listitem>
         <listitem>
-          <para>Change to the sources directory.</para>
+          <para>Change to the <filename class="directory">/mnt/lfs/sources/</filename> directory.</para>
         </listitem>
         <listitem id='buildinstr' xreflabel='Package build instructions'>
           <para>For each package:</para>
@@ -97,22 +97,21 @@
               to be built.  In <xref linkend="chapter-cross-tools"/> and
               <xref linkend="chapter-temporary-tools"/>, ensure you are
               the <emphasis>lfs</emphasis> user when extracting the package.</para>
-              <para>All methods to get the source code tree being built
-              in-position, except extracting the package tarball, are not
-              supported. Notably, using <command>cp -R</command> to copy the
+            <para>Do not use any method except the <command>tar</command> command
+              to extract the source code. Notably, using the <command>cp -R</command>
+              command to copy the
               source code tree somewhere else can destroy links and
-              timestamps in the sources tree and cause building
-              failure.</para>
+              timestamps in the source tree, and cause the build to fail.</para>
             </listitem>
             <listitem>
               <para>Change to the directory created when the package was
               extracted.</para>
             </listitem>
             <listitem>
-              <para>Follow the book's instructions for building the package.</para>
+              <para>Follow the instructions for building the package.</para>
             </listitem>
             <listitem>
-              <para>Change back to the sources directory.</para>
+              <para>Change back to the sources directory when the build is complete.</para>
             </listitem>
             <listitem>
               <para>Delete the extracted source directory unless instructed otherwise.</para>