Various text fixes:

- a wrong chapter in toolchain notes, and various text precisions
the option explanations of chapter 8 glibc (was labelled WIP)

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

part3intro/toolchaintechnotes.xml

@@ -309,15 +309,15 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
     and generally does not rely on toolchain defaults.</para>
 
     <para>As said above, the standard C++ library is compiled next, followed in
-    <xref linkend="chapter-cross-tools"/> by all the programs that need
-    themselves to be built. The install
-    step of libstdc++ uses the <envar>DESTDIR</envar> variable to have the
+    <xref linkend="chapter-temporary-tools"/> by all the programs that need
+    themselves to be built. The install step of all those packages uses the
+    <envar>DESTDIR</envar> variable to have the
     programs land into the LFS filesystem.</para>
 
-    <para>In <xref linkend="chapter-temporary-tools"/> the native lfs
-    compiler is built. First binutils-pass2,
-    with the same <envar>DESTDIR</envar> install as the other programs is
-    built, and then the second pass of GCC is constructed, omitting libstdc++
+    <para>At the end of <xref linkend="chapter-temporary-tools"/> the native
+    lfs compiler is installed. First binutils-pass2 is built,
+    with the same <envar>DESTDIR</envar> install as the other programs,
+    then the second pass of GCC is constructed, omitting libstdc++
     and other non-important libraries.  Due to some weird logic in GCC's
     configure script, <envar>CC_FOR_TARGET</envar> ends up as
     <command>cc</command> when the host is the same as the target, but is