Update

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

2 files changed, 16 insertions, 19 deletions

diff --git a/chapter02/download.xml b/chapter02/download.xml
index 7744c4efe..a895230e6 100644
--- a/chapter02/download.xml
+++ b/chapter02/download.xml
@@ -9,8 +9,8 @@ packages that were downloaded are placed somewhere in $LFS/usr/src.
 <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 as sysvinit-2.78.tar.gz is stored under
-$LFS/usr/src/sources/s/. A package as bash-2.04.tar.gz is stored under 
+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 
 the packages out of $LFS/usr/src and move them to a subdirectory, so 
@@ -22,9 +22,9 @@ packages and work with them.
 The next chapter contains the list of all the packages that need to be
 downloaded,
 but the partition that is going to contain our LFS system isn't created yet.
-Therefore, the files are temporarily stored somewhere else and later 
-copied to $LFS/usr/src/ when the chapter in which 
-the new partition is prepared has been finished.
+Therefore, the files are temporarily stored somewhere else (it's up to
+you to decide where this 'else' is) and later moved to $LFS/usr/src/ when 
+the chapter in which the new partition is prepared has been finished.
 </para>
 
 </sect1>
diff --git a/chapter02/install.xml b/chapter02/install.xml
index bfdb58b4d..15dbb6f5f 100644
--- a/chapter02/install.xml
+++ b/chapter02/install.xml
@@ -4,17 +4,9 @@
 <para>
 Before you can actually start doing something with a package, you need
 to unpack it first. Often the package files are tar'ed and
-gzip'ed. (That can be determined by looking at the extension of the file.
-Tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
-example.) I'm not going to write down every time how to ungzip and how 
-to untar an archive. I will explain how to do that once, in this section. 
-There is also the possibility that a .tar.bz2 file could be downloaded.
-Such a file would be tar'ed and compressed with the bzip2 program. 
-Bzip2 achieves a better compression than the more commonly used gzip does. 
-In order to use bz2 archives, the bzip2 program needs to be installed. 
-Most if not every distribution comes with this program, so chances are 
-high it is already installed on the host system. If not, it's installed 
-using the distribution's installation tool.
+gzip'ed or bzip2'ed. I'm not going to write down every time how to
+unpack an archive. I will explain how to do that once, in this 
+section. 
 </para>
 
 <para>
@@ -71,7 +63,7 @@ If a file is just tar'ed, it is unpacked by running:
 </literallayout></blockquote>
 
 <para>
-When the archive is unpacked, a new directory will be created under the
+When ab archive is unpacked, a new directory will be created under the
 current directory (and this book assumes that the archives are unpacked
 under the $LFS/usr/src directory). Please enter that new directory
 before continuing with the installation instructions. Again, every time
@@ -106,7 +98,7 @@ If a file is bzip2'ed, it is unpacked by running:
 </literallayout></blockquote>
 
 <para>
-After a package is installed, two things can be done with it:
+After a package has been installed, two things can be done with it:
 either the directory that contains the sources can be deleted,
 or it can be kept. If it is kept, that's fine with me, but if the 
 same package is needed again in a later chapter, the directory 
@@ -118,9 +110,14 @@ always guarantee a totally clean source tree.
 </para>
 
 <para>
+So, save yourself a lot of hassle and just remove the source directory
+immediately after you have installed it.
+</para>
+
+<para>
 There is one exception to that rule: don't remove the Linux kernel source
 tree. A lot of programs need the kernel headers, so that's the only
-directory that should not be removed, unless no software is to be compiled
+directory that should not be removed, unless no package is to be compiled
 anymore.
 </para>