Small grammar adjustments.

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

chapter05/lockingglibc.xml

@@ -39,8 +39,8 @@ all in. Or you can edit the specs file by hand if you want to: just replace
 
 <para>Lastly, there is a possibility that some include files from the host
 system have found their way into gcc's private include dir. This can happen
-because of GCC's "fixincludes" process which part of the GCC build. We'll
-explain more about this further on in this chapter.  For now, run the
+because of GCC's "fixincludes" process which runs as part of the GCC build.
+We'll explain more about this further on in this chapter.  For now, run the
 following commands to eliminate this possibility.</para>
 
 <para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>

chapter05/whystatic.xml

@@ -43,13 +43,14 @@ memory space, disk space, and recompile time.</para>
 
 <para>But if dynamic linking saves so much space, why then are we linking
 the first two packages in this chapter statically? The reason is to make them
-independent from the libraries on your host system. And the point in that is
-that, if you are pressed for time, you could skip the second passes over GCC
-and Binutils, and just use the static versions to compile the rest of this
-chapter and the first few packages in the next. As in the next chapter we
-will be chrooted to the LFS partition and your host system's Glibc won't be
-available, the programs from GCC and Binutils will need to be self-contained,
-that is statically linked.</para>
+independent from the libraries on your host system. The advantage is that, if
+you are pressed for time, you could skip the second passes over GCC and
+Binutils, and just use the static versions to compile the rest of this chapter
+and the first few packages in the next. In the next chapter we will be
+chrooted to the LFS partition and once inside the chroot environment, the host
+system's Glibc won't be available, thus the programs from GCC and Binutils
+will need to be self-contained, i.e. statically linked. However, we strongly
+advise <emphasis>against</emphasis> skipping the second passes.</para>
 
 </sect1>