Applied Alex\'s grammar patch

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2082 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 23 insertions, 21 deletions

diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
index fec62f4b3..dfe834c24 100644
--- a/chapter06/introduction.xml
+++ b/chapter06/introduction.xml
@@ -7,29 +7,31 @@ constructing our LFS system in earnest.  That is, we chroot into
 our temporary mini Linux system, create some auxiliary things,
 and then start installing all the packages, one by one.</para>
  
-<para>The installation of all the software is pretty straightforward, and
-you will probably think it would be so much easier and shorter to give
-the generic installation instructions for a package here and only explain
-in full the installation of those packages that require an alternate
-method. Although we agree with that, we choose to give the 
-full instructions for each and every package, simply to avoid any 
-possible confusion and errors.</para>
+<para>The installation of all this software is pretty straightforward,
+and you will probably think it would be much shorter to give here
+the generic installation instructions and explain in full only the
+installation of those packages that require an alternate method.
+Although we agree with that, we nevertheless choose to give the 
+full instructions for each and every package, simply to minimize
+the possibilities for mistakes.</para>
 
-<para>If you plan to use compiler optimization for the packages
-installed in this chapter, take a look at the optimization hint 
-at <ulink url="&hints-root;optimization.txt"/>.
-Compiler optimization can make a program run
-faster, but may also cause compilation problems. If you run into problems
-when using optimization, always try it without optimization to see if 
-the problem persists.</para>
+<para>If you plan to use compiler optimizations in this chapter,
+take a look at the optimization hint at
+<ulink url="&hints-root;optimization.txt"/>.
+Compiler optimizations can make a program run faster, but they
+may also cause compilation difficulties. If a package refuses
+to compile when using optimization, try to compile it without
+optimization and see if  the problem goes away.</para>
 
-<para>Please refrain from installing more than one package at a time, even
-if it may save you time (especially with dual CPU machines). If you install
-the wrong package at the wrong time, it may hard-wire program paths to
-<filename class="directory">$LFS/static</filename> which will cause the
-programs to stop working once the static directory is removed. The order
-packages are installed in this chapter have to be followed exactly to be
-sure nothing is hard-wiring the static paths.</para>
+<para>The order in which packages are installed in this chapter has
+to be strictly followed, to ensure that no program gets a path referring
+to <filename class="directory">/static</filename> hard-wired into it.
+For the same reason, <emphasis>do not </emphasis> compile packages
+in parallel.  Compiling in parallel may save you some time (especially on
+dual-CPU machines), but it could result in a program containing a
+hard-wired path to <filename class="directory">/static</filename>,
+which will cause the program to stop working when the static directory
+is removed.</para>
 
 </sect1>