1 files changed, 11 insertions, 10 deletions
diff --git a/chapter06/m4-inst.xml b/chapter06/m4-inst.xml
index ef29a5d65..68e24e824 100644
--- a/chapter06/m4-inst.xml
+++ b/chapter06/m4-inst.xml
@@ -14,16 +14,16 @@ Install M4 by running the following commands:
 </literallayout></blockquote>
 
 <para>
-If you're base system is running a 2.0 kernel and your Glibc version is
-2.1 then you will most likely get problems executing M4 in the
+If the base system is running a 2.0 kernel and the Glibc version is
+2.1 then a user will most likely get problems executing M4 in the
 chroot'ed environment due to incompatibilities between the M4 program,
-Glibc-2.1 and the running 2.0 kernel. If you have problems executing the 
-m4 program in the chroot'ed environment (for example when you install 
-the autoconf and automake packages) you'll have to exit the chroot'ed 
+Glibc-2.1 and the running 2.0 kernel. If he has problems executing the 
+m4 program in the chroot'ed environment (for example when he installs 
+the autoconf and automake packages) he'll have to exit the chroot'ed 
 environment and compile M4 statically. This way the binary is linked 
-against Glibc 2.0 (if you run kernel 2.0 you're Glibc version is 2.0 as 
+against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as 
 well on a decent system. Kernel 2.0 and Glibc-2.1 don't mix very well) 
-and won't give you any problems. 
+and won't give any problems. 
 </para>
 
 <para>
@@ -42,9 +42,10 @@ commands:
 </literallayout></blockquote>
 
 <para>
-Now you can re-enter the chroot'ed environment and continue with the
-next package. If you wish to recompile M4 dynamically, you can do that
-after you have rebooted into the LFS system rather than chroot'ed into it.
+Now the chroot'ed environment can be re-entered and the
+next package an be installed. If M4 should be re-compiled dynamically,
+this can be done 
+after having rebooted into the LFS system rather than chrooting into it.
 </para>
 
 <blockquote><literallayout>