minor textual changes

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

chapter02/download.xml

@@ -6,10 +6,10 @@ packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
 
 <para>I use the convention of having a $LFS/usr/src/sources directory.
 Under sources, I have the directory 0-9 and the directories a
-through z. A package like sysvinit-2.78.tar.gz is stored under
-$LFS/usr/src/sources/s/. A package like bash-2.04.tar.gz is stored under 
-$LFS/usr/src/sources/b/, and so forth. This convention does not have to be
-followed, of course; I was just giving an example. It's better to keep 
+through z. A package like sysvinit-&sysvinit-version;.tar.bz2 is stored under
+$LFS/usr/src/sources/s/. A package like bash-&bash-version;.tar.bz2 is stored 
+under  $LFS/usr/src/sources/b/, and so forth. This convention does not have to 
+be followed, of course; I was just giving an example. It's better to keep 
 the packages out of $LFS/usr/src and move them to a subdirectory, so 
 we'll have a clean $LFS/usr/src directory in which we will unpack the 
 packages and work with them.</para>

chapter02/install.xml

@@ -31,8 +31,8 @@ running:</para>
 
 <para>Some tar programs (most of them nowadays but not all of them) are
 slightly modified to be able to use bzip2 files directly using either
-the I or the y tar parameter, which works the same as the z tar parameter
-to handle gzip archives. The above construction works no matter how
+the I, the y or the j tar parameter, which works the same as the z tar 
+parameter to handle gzip archives. The above construction works no matter how
 your host system decided to patch bzip2.</para>
 
 <para>If a file is just tar'ed, it is unpacked by running:</para>