Grammar updates

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

chapter05/installasroot.xml

@@ -2,8 +2,8 @@
 <title>Install all software as user root</title>
 
 <para>
-It's best if the user logs in as root or su's to root when installing these
-files. That way he is assured that all files are owned by user and
+It's best to log in as root or su's to root when installing the
+packages. That way you are assured that all files are owned by user and
 group root (and not owned by the userid of the non-root user), and if a
 package wants to set special permissions, it can do so without problems
 due to non-root access.
@@ -16,7 +16,7 @@ feel it's safe to ignore that recommendation and compile as user root
 anyway. Hundreds of people using LFS have done so without any problems
 whatsoever, and we haven't encountered any bugs in the compile processes
 that cause harm. So it's pretty safe (never can be 100% safe though, so
-it's up to the user what he ends up doing).
+it's up to you what you ends up doing).
 </para>
 
 </sect1>

chapter05/introduction.xml

@@ -3,10 +3,10 @@
 
 <para>
 In the following chapters we will install all the software that belongs to 
-a basic Linux system. After a user is done with this chapter he has a 
-fully working Linux system. The remaining chapters deal with setting up 
-networking, creating the boot scripts and adding an entry to lilo.conf so 
-that the LFS system can be booted.
+a basic Linux system. After you're done with this and the next chapter,
+you'll have a fully working Linux system. The remaining chapters deal 
+with creating the boot scripts, making the LFS system bootable and
+setting up basic networking.
 </para>
 
 <para>
@@ -27,23 +27,17 @@ package and in Appendix A as well.
 </para>
 
 <para>
-We're about to start with installing the first set of packages. These
-packages will be, as previously explained, linked statically.
+During the installation of various packages, you will more than likely see
+all kinds of compiler warnings scrolling by on the screen. These are 
+normal and can be safely ignored. They are just that, warnings (mostly 
+about improper use of the C or C++ syntax, but not illegal use. It's just 
+that, often, C standards changed and packages still use the old standard 
+which is not a problem).
 </para>
 
 <para>
-During the installation of various packages, the user will most likely see
-compiler warnings scrolling by on the screen. These are normal and can
-be safely ignored. They are just that, warnings (mostly about improper
-use of the C or C++ syntax, but not illegal use. It's just that, often, C
-standards changed and packages still use the old standard which is not a
-problem).
-</para>
-
-<para>
-Before we start, it should be made sure the LFS environment variable was 
-setup 
-if it was planned to be used, by running the following command:
+Before we start, make sure the LFS environment variable is setup
+properly if you decided to make use of it. Run the following:
 </para>
 
 <blockquote><literallayout>
@@ -52,5 +46,10 @@ if it was planned to be used, by running the following command:
 
 </literallayout></blockquote>
 
+<para>
+Check to make sure the output contains the correct directory to the LFS
+partition's mount point (/mnt/lfs for example).
+</para>
+
 </sect1>
 

chapter06/chroot.xml

@@ -7,7 +7,7 @@ rest of the software we need.
 </para>
 
 <para>
-Enter the following command to enter the chroot'ed environment. From
+Enter the following commands to enter the chroot'ed environment. From
 this point on there's no need to use the $LFS variable anymore, because
 everything a user does will be restricted to the LFS partition (since / is
 actually /mnt/lfs but the shell doesn't know that).
@@ -32,14 +32,14 @@ like vim and less to operate properly.
 Now that we are inside a chroot'ed environment, we can continue to
 install all the basic system software. You have to make sure all the
 following commands in this and following chapters are run from within the 
-chroot'ed environment. If you ever leave this environment for a reason
-(say when rebooting or something) please remember to mount $LFS/proc 
-again like you just did and re-enter chroot before continuing with the
+chroot'ed environment. If you ever leave this environment for any reason
+(when rebooting for example) please remember to mount $LFS/proc 
+again and re-enter chroot before continuing with the
 book.
 </para>
 
 <para>
-Note that the bash prompt will contain "I have no name!". This is
+Note that the bash prompt will contain "I have no name!" This is
 normal because Glibc hasn't been installed yet.
 </para>