Fixed some typo's

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

chapter05/installasuser.xml

@@ -9,7 +9,7 @@ to happen, for example because the $LFS environment variable is not
 set. Overwriting some files from your host system will most likely
 cause all kinds of problems, so it's a good idea to be logged in as
 an unprivileged user during chapter 5. To make sure the environment
-is as clean as possible, we'll create a new user lfs that can be
+is as clean as possible, we'll create a new user "lfs" that can be
 used while building the static installation. Issuing the following
 commands as root will create a new user "lfs":</para>
 
@@ -45,10 +45,10 @@ internationalization.</para>
 
 <para>When your host distribution uses a glibc version older than 2.2.4,
 having $LC_ALL set to something else than "C" or "POSIX" while working
-through chapter 5 may cause trouble when you've exited the chrooted
-environment of chapter 6 and try to return to it. By setting this to
-"POSIX" ("C" is an alias for "POSIX") we ensure that everything will
-work as expected in the chrooted environment.</para>
+through chapter 5 may cause trouble when you exit the chroot environment
+of chapter 6 and try to return to it. By setting this to "POSIX" ("C"
+is an alias for "POSIX") we ensure that everything will work as expected
+in the chroot environment.</para>
 
 </sect1>
 

chapter05/whystatic.xml

@@ -8,22 +8,21 @@ based to one of the LFS mailing lists.</para>
 <para>When making (compiling) a program, rather than having to rewrite all the
 functions for dealing with the kernel, hardware, files, etc. every time you
 write a new program, all these basic functions are instead kept in libraries.
-glibc, which you install later, is one of these major libraries, which contain
-code for all the basic functions programs use, like opening files, printing
-information on the screen, and getting feedback from the user. When the
-program is compiled, these libraries of code are linked together with the new
-program, so that it can use any of the functions that the library
+glibc, which you install later, is one of these major libraries, which
+contains code for all the basic functions programs use, like opening files,
+printing information on the screen, and getting feedback from the user. When
+the program is compiled, these libraries of code are linked together with the
+new program, so that it can use any of the functions that the library
 has.</para>
 
-<para>However, these libraries can be very large (for example, libc.a
-from can often be around 2.5MB), so you may not want a separate copy of 
-each library attached to the
-program. Just imagine if you had a simple command like ls with an extra 2.5MB
-attached to it! Instead of making the library an actual part of the
-program, or Statically Linked, the library is kept a separate file,
-which is loaded only when the program needs it. This is what we call Dynamically
-Linked, as the library is loaded and unloaded dynamically, as the program needs
-it.</para>
+<para>However, these libraries can be very large (for example, libc.a from
+can often be around 2.5MB), so you may not want a separate copy of each
+library attached to the program. Just imagine if you had a simple command
+like ls with an extra 2.5MB attached to it! Instead of making the library
+an actual part of the program, or statically linked, the library is kept a
+separate file, which is loaded only when the program needs it. This is what
+we call dynamically linked, as the library is loaded and unloaded dynamically,
+as the program needs it.</para>
 
 <para>So now we have a 1kb file and a 2.5MB file, but we still haven't saved any
 space (except maybe RAM until the library is needed). The REAL advantage to