You-fix

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

chapter02/aboutlfs.xml

@@ -2,8 +2,8 @@
 <title>About $LFS</title>
 
 <para>
-Please read the following carefully: throughout this book you will
-frequently see the variable name $LFS. $LFS must at all times be
+Please read the following carefully: throughout this book 
+the variable name $LFS will frequently be used. $LFS must at all times be
 replaced by the directory where the partition that contains the LFS system 
 is mounted. How to create and where to mount the partition will be
 explaind in full detail later on in chapter 4. In my case, the LFS 
@@ -14,13 +14,14 @@ cp inittab /mnt/lfs/etc.
 </para>
 
 <para>
-It's important that you do this no matter where you read it; be it in
-commands you enter on the prompt, or in a file you edit or create.
+It's important that this is done no matter where it is read; be it in
+commands entered on the prompt, or in a file edited or created.
 </para>
 
 <para>
-If you want, you can set the environment variable LFS. This way you can
-literally enter $LFS instead of replacing it by something like
+Another possible solution is to set the environment variable LFS.
+This way the $LFS can be entered literally instead of replacing it by 
+something like
 /mnt/lfs. This is accomplished by running: export LFS=/mnt/lfs.
 </para>
 
@@ -31,20 +32,21 @@ automatically.
 </para>
 
 <para>
-Do not forget to set the $LFS variable at all times. If you haven't set
-the variable and you use it in a command, $LFS will be ignored and whatever
+Do not forget to set the $LFS variable at all times. If 
+the variable is not set and is used it in a command, $LFS will be ignored 
+and whatever
 is left will be executed. The command cp inittab $LFS/etc without the $LFS
 variable set will result in copying the inittab file to the /etc
-directory, which will overwrite your system's inittab. A file like inittab 
-isn't that big a problem as it can easily be restored, but if you would 
-make this mistake during the installation of the C Library, you could
-damage things.
+directory, which will overwrite the host-system's inittab. A file like inittab 
+isn't that big a problem as it can easily be restored, but if 
+this mistake is made during the installation of the C Library, things might
+be damaged
 </para>
 
 <para>
 One way to make sure that $LFS is set at all times is adding it to
-your /root/.bash_profile and/or /root/.bashrc file(s) so that every time you
-'su' to install LFS, the $LFS variable is set for you.
+the /root/.bash_profile and/or /root/.bashrc file(s) so that every time a
+'su' to root is done to install LFS, the $LFS variable is set for.
 </para>
 
 </sect1>

chapter02/bootscripts.xml

@@ -7,7 +7,7 @@ process, not to mention very error-prone.
 </para>
 
 <para>
-To save you guys and girls some time, you can download the bootscripts
+To save some time, the bootscripts can be downloaded
 from <ulink
 url="http://download.linuxfromscratch.org/bootscripts/">
 http://download.linuxfromscratch.org/bootscripts/</ulink> or <ulink

chapter02/commands.xml

@@ -4,18 +4,20 @@
 <para>
 LFS Commands is a tarball containing files which list the installation
 commands for the packages installed in this book. These files can be
-used to dump to your shell and install the packages, though some files 
-need to be modified (for example when you install the console-tools 
-package you need to select your keyboard layout file which can't be guessed).
+used to dump to a shell and install the packages, though some files 
+need to be modified (for example when the console-tools package is 
+installed it is needed to select the keyboard layout file which can't be
+guessed).
 </para>
 
 <para>
 These files can be used to quickly find out which commands have been
-changed between the different LFS versions as well. You can download the
+changed between the different LFS versions as well. A user just downloads the
 lfs-commands tarball for this book version and the previous book version 
-and run a diff on the files. That way you can see which package have 
-updated installation instructions so you can modify your own scripts, or 
-reinstall a package if you deem necessary.
+and run a diff on the files. That way it is possible to see which packages
+have 
+updated installation instructions and he can modify his own scripts, or 
+reinstall a package if it seems necessary.
 </para>
 
 <para>

chapter02/download.xml

@@ -2,28 +2,29 @@
 <title>How to download the software</title>
 
 <para>
-Throughout this document I will assume that you have stored all the
-packages you have downloaded somewhere in $LFS/usr/src.
+Throughout this document I 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 you'll find the directory 0-9 and the directories a
+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 
-$LFS/usr/src/sources/b/ and so forth. You don't have to follow this 
-convention of course, I was just giving an example. It's better to keep 
+$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>
 
 <para>
-The next chapter contains the list of all the packages you need to download,
+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, store the files temporarily somewhere where you want and remember
-to copy them to $LFS/usr/src/ when you have finished the chapter in which 
-you prepare a new partition (chapter 4).
+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 got finished.
 </para>
 
 </sect1>

chapter02/install.xml

@@ -2,19 +2,19 @@
 <title>How to install the software</title>
 
 <para>
-Before you can actually start doing something with a package, you need
-to unpack it first. Often you will find the package files being tar'ed and
-gzip'ed. (You can determine this by looking at the extension of the file.
+Before a user can actually start doing something with a package, he needs
+to unpack it first. Often the package files are tar'ed and
+gzip'ed. (that can 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 tell you how to do that once, in this section. 
-There is also the possibility  that you have the ability of downloading 
-a .tar.bz2 file. Such a file is tar'ed and compressed with the bzip2 program. 
+to untar an archive. I will tell how to do that once, in this section. 
+There is also the possibility  that a .tar.bz2 file can be downloaded.
+Such a file is tar'ed and compressed with the bzip2 program. 
 Bzip2 achieves a better compression than the commonly used gzip does. In 
-order to use bz2 archives you need to have the bzip2 program installed. 
+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 your system. If not, install it using 
-your distribution's installation tool.
+high it is already installed on the host-system. If not, it's installed using 
+the distribution's installation tool.
 </para>
 
 <para>
@@ -28,7 +28,7 @@ To start with, change to the $LFS/usr/src directory by running:
 </literallayout></blockquote>
 
 <para>
-When you have a file that is tar'ed and gzip'ed, you unpack it by
+If a file is tar'ed and gzip'ed, it is unpacked by
 running either one of the following two commands, depending on the
 filename format:
 </para>
@@ -42,7 +42,7 @@ filename format:
 
 
 <para>
-When you have a file that is tar'ed and bzip2'ed, you unpack it by
+If a file is tar'ed and bzip2'ed, it is unpacked by
 running:
 </para>
 
@@ -60,7 +60,7 @@ to handle gzip archives.
 </para>
 
 <para>
-When you have a file that is tar'ed, you unpack it by running:
+If a file is just tar'ed, it is unpacked by running:
 </para>
 
 <blockquote><literallayout>
@@ -71,15 +71,15 @@ When you have a file that is tar'ed, you unpack it by running:
 
 <para>
 When the archive is unpacked a new directory will be created under the
-current directory (and this document assumes that you unpack the archives
-under the $LFS/usr/src directory). You have to enter that new directory
-before you continue with the installation instructions. So every time the
-book is going to install a program, it's up to you to unpack the source
+current directory (and this document assumes that the archives are unpacked
+under the $LFS/usr/src directory). A user has to enter that new directory
+before continuing with the installation instructions. So every time the
+book is going to install a program, it's up to the user to unpack the source
 archive.
 </para>
 
 <para>
-When you have a file that is gzip'ed, you unpack it by running:
+f a file is gzip'ed, it is unpacked by running:
 </para>
 
 <blockquote><literallayout>
@@ -89,13 +89,14 @@ When you have a file that is gzip'ed, you unpack it by running:
 </literallayout></blockquote>
 
 <para>
-After you have installed a package you can do two things with it. You can
-either delete the directory that contains the sources or you can keep it.
-If you decide to keep it, that's fine with me. But, if you need the same package
-again in a later chapter, you need to delete the directory first before using
-it again. If you don't do this, you might end up in trouble because old
-settings will be used (settings that apply to your normal Linux system but
-which don't always apply to your LFS system). Doing a simple make clean
+After a package is 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, it might end up in trouble because old
+settings will be used (settings that apply to the normal Linux 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. 
 The configure script can also have files lying around in various 
 subdirectories which aren't always removed by a make clean process.
@@ -104,8 +105,8 @@ subdirectories which aren't always removed by a make clean process.
 <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 you don't want to remove, unless you are not going to
-compile any software anymore.
+directory that should not be removed, unless no software is to be compiled
+anymore.
 </para>
 
 </sect1>