Small textual frobbings, and removing an unneeded {,share/}.

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

chapter01/changelog.xml

@@ -6,15 +6,19 @@
 
 <itemizedlist>
 
+<listitem><para>February 19th, 2004 [alex]: Chapter 5 - Stripping: Removed
+an unnecessary "{,share/}" from the documentation's <command>rm</command>
+command.</para></listitem>
+
 <listitem><para>February 14th, 2004 [jeremy]: Chapter 6 - Upgraded Less
-to 382</para></listitem>
+to 382.</para></listitem>
 
 <listitem><para>February 14th, 2004 [jeremy]: Chapters 5 & 6 - Upgraded
 ncurses to version 5.4, and removed references to etip patch.</para></listitem>
 
 <listitem><para>February 12th, 2004 [jeremy]: Chapter 6 - Removed explicit
 paths from the pwconv and grpconv commands, since /usr/sbin is part of
-the default path</para></listitem>
+the default path.</para></listitem>
 
 <listitem><para>February 9th, 2004 [alex]: Chapter 6 - Moved the Bootscripts
 installation section to chapter 7.</para></listitem>

chapter05/chapter05.xml

@@ -590,10 +590,9 @@ of binaries.</para>
 would be destroyed and you would have to build the three toolchain packages
 all over again.</para>
 
-<para>To save another couple of megabytes, you can throw away all the
-documentation:</para>
+<para>To save another 30 MB, you can remove all the documentation:</para>
 
-<screen><userinput>rm -rf /tools/{,share/}{doc,info,man}</userinput></screen>
+<screen><userinput>rm -rf /tools/{doc,info,man}</userinput></screen>
 
 <para>You will now need to have at least 850 MB of free space on your LFS
 file system to be able to build and install Glibc in the next phase. If you can

chapter06/chapter06.xml

@@ -359,13 +359,13 @@ file records the bad login attempts.</para>
 
 <para>Now that the new and final C libraries have been installed, it's time to
 adjust our toolchain again. We'll adjust it so that it will link any newly
-compiled program against these new libraries. This is in fact the same we did
-in the "Adjusting" phase in the beginning of the previous chapter, even though
-it looks like the reverse: then we guided the chain from the host's
-<filename class="directory">{,/usr}/lib</filename> to the new
+compiled program against these new libraries. This is in fact the same thing we
+did in the "Adjusting" phase in the beginning of the previous chapter, even
+though it looks like the reverse: then we guided the chain from the host's
+<filename class="directory">/{,usr/}lib</filename> to the new
 <filename class="directory">/tools/lib</filename>, now we guide it from that
 same <filename class="directory">/tools/lib</filename>
-to the LFS's <filename class="directory">{,/usr}/lib</filename>.</para>
+to the LFS's <filename class="directory">/{,usr/}lib</filename>.</para>
 
 <para>First we adjust the linker. For this we retained the
 source and build directories from the second pass over Binutils. Install the
@@ -380,7 +380,7 @@ source and build directories from the second pass in
 don't have access to them, don't worry, all is not lost. Just ignore the above
 command. The result will be that the next package, Binutils, will link against
 the C libraries in <filename class="directory">/tools</filename> rather
-than <filename class="directory">{,/usr}/lib</filename>. This is not ideal,
+than in <filename class="directory">/{,usr/}lib</filename>. This is not ideal,
 however, our testing has shown that the resulting Binutils program binaries
 should be identical.</para></note>
 

index.xml

@@ -2,8 +2,8 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
 			"/usr/share/docbook/docbookx.dtd" [
 
-<!ENTITY version "CVS-2004-02-14">
-<!ENTITY releasedate "February 14th, 2004">
+<!ENTITY version "CVS-2004-02-19">
+<!ENTITY releasedate "February 19th, 2004">
 <!ENTITY milestone "5.2">
 <!ENTITY nbsp " ">