text updates

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

5 files changed, 36 insertions, 37 deletions

diff --git a/chapter02/aboutlfs.xml b/chapter02/aboutlfs.xml
index 8533f7382..2ff9da689 100644
--- a/chapter02/aboutlfs.xml
+++ b/chapter02/aboutlfs.xml
@@ -3,10 +3,10 @@
 
 <para>Please read the following carefully: throughout this book 
 the variable $LFS will be used frequently. $LFS must at all times be
-replaced by the directory where the partition that contains the LFS system 
+replaced with the directory where the partition that contains the LFS system 
 is mounted. How to create and where to mount the partition will be
-explained in full detail in chapter 4. In my case, the LFS 
-partition is mounted  on /mnt/lfs.</para>
+explained in full detail in chapter 4. For example, let's assume that 
+the LFS partition is mounted on /mnt/lfs.</para>
 
 <para>For example when you are told to run a command like
 <userinput>./configure --prefix=$LFS</userinput> you actually have to
@@ -16,7 +16,7 @@ execute <userinput>./configure --prefix=/mnt/lfs</userinput></para>
 commands entered in a shell, or in a file edited or created.</para>
 
 <para>A possible solution is to set the environment variable LFS.
-This way $LFS can be entered literally instead of replacing it by 
+This way $LFS can be entered literally instead of replacing it with 
 /mnt/lfs. This is accomplished by running <userinput>export
 LFS=/mnt/lfs</userinput>.</para>
 
diff --git a/chapter02/bootscripts.xml b/chapter02/bootscripts.xml
index 96cd852c6..5caa5014d 100644
--- a/chapter02/bootscripts.xml
+++ b/chapter02/bootscripts.xml
@@ -1,7 +1,7 @@
 <sect1 id="ch02-bootscripts">
 <title>Download the bootscripts</title>
 
-<para>Typing out all the bootscripts in chapters 7 and 9 can be a long, tedious
+<para>Typing out all the bootscripts in chapter 7can be a long, tedious
 process, not to mention very error-prone.</para>
 
 <para>To save some time, the bootscripts can be downloaded from <ulink
diff --git a/chapter02/commands.xml b/chapter02/commands.xml
index 566fde592..4cbb0f4af 100644
--- a/chapter02/commands.xml
+++ b/chapter02/commands.xml
@@ -5,7 +5,7 @@
 commands for the packages installed in this book.</para>
 
 <para>These files can be used to quickly find out which commands have
-been changed between the different LFS versions as well. Download the
+been changed between the different LFS versions. Download the
 lfs-commands tarball for this book version and the previous book
 version and run a diff on the files. That way it is possible to see which
 packages have updated installation instructions, so any scripts you may 
@@ -13,13 +13,16 @@ have can be modified, or you can reinstall a package if you think that
 necessary.</para>
 
 <para>A side effect is that these files can be used to dump to a shell and 
-install the packages, though some files need to be modified (for 
-example, when the kbd package is installed, you needed to select the 
-keyboard layout file, because it can't reliably be guessed). Keep in
-mind, please, that these files are not checked for correctness,
-integrity and so forth. There may be bugs in the files (since they are
-manually created, typo's are often inevitable) so do check them and
-don't blindly trust them.</para>
+install the packages, though some files need to be modified (where
+certain settings can't be guessed and depend on user preference or
+system hardware). Keep in mind, please, that these files are not
+thoroughly checked for correctness. There may be bugs in the files (since 
+they are manually created at the moment) so do check them and don't 
+blindly trust them.</para>
+
+<para>If you decide to use the commands to automatically install a
+package and it doesn't work, try reading the book's instructions
+instead before you ask for help on the mailinglist.</para>
 
 <para>The lfscommands can be downloaded from <ulink
 url="&http-root;/lfs-commands/">&http-root;/lfs-commands/</ulink> 
diff --git a/chapter02/download.xml b/chapter02/download.xml
index b8e76fa41..117ae4d4e 100644
--- a/chapter02/download.xml
+++ b/chapter02/download.xml
@@ -1,25 +1,20 @@
 <sect1 id="ch02-download">
 <title>How to download the software</title>
 
-<para>Throughout this document, I will assume that all the
+<para>Throughout this document, we will assume that all the
 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
+<para>A convention you could use is having a $LFS/usr/src/sources directory.
+Under sources, you can create the directory 0-9 and the directories a
 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>
+under  $LFS/usr/src/sources/b/, and so forth.</para>
 
 <para>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 (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>
+downloaded, but the partition that is going to contain our LFS system isn't 
+created yet. Therefore, you should store the files somewhere else 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 ca6374a92..aa2856abf 100644
--- a/chapter02/install.xml
+++ b/chapter02/install.xml
@@ -8,8 +8,8 @@ simple life, use bash.</para>
 
 <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 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 
+gzip'ed or bzip2'ed. We're not going to write down every time how to
+unpack an archive. We'll explain how to do that once, in this 
 section.</para>
 
 <para>To start with, change to the $LFS/usr/src directory by running:</para>
@@ -58,15 +58,16 @@ can be used they need to be uncompressed first.</para>
 
 <para><screen><userinput>bunzip2 filename.bz2</userinput></screen></para>
 
-<para>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 
-needs to be deleted first before using it again. If this is not done, 
-you might end up in trouble because old settings will be used (settings 
-that apply to the host system but which don't always apply to 
-the LFS system). Doing a simple make clean or make distclean does not 
-always guarantee a totally clean source tree.</para>
+<para>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. We highly recommend deleting it. If you don't do this and
+try to re-use the same source later on in the book (for example re-using
+the source trees from chapter 5 for use in chapter 6), it may not work
+as you expect it to. Source trees from chapter 5 will have your host
+distribution's settings, which don't always apply to the LFS system
+after you enter the chroot'ed environment. Even running something like
+<emphasis>make clean</emphasis> doesn't always guarantee a 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>