You

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

17 files changed, 60 insertions, 54 deletions

diff --git a/chapter07/checkfs.xml b/chapter07/checkfs.xml
index 2350a0056..762bfacae 100644
--- a/chapter07/checkfs.xml
+++ b/chapter07/checkfs.xml
@@ -2,7 +2,7 @@
 <title>Creating the checkfs script</title>
 
 <para>
-Create a new file <filename>/etc/init.d/checkfs</filename> containing
+A new file <filename>/etc/init.d/checkfs</filename> is created containing
 the following:
 </para>
 
diff --git a/chapter07/createdirs.xml b/chapter07/createdirs.xml
index 0831e7874..6b54ae3fe 100644
--- a/chapter07/createdirs.xml
+++ b/chapter07/createdirs.xml
@@ -3,7 +3,7 @@
 
 <para>
 We need to start by creating a few extra directories that are used by
-the boot scripts. Create these directories by running:
+the boot scripts. These directories are created by running:
 </para>
 
 <blockquote><literallayout>
diff --git a/chapter07/fstab.xml b/chapter07/fstab.xml
index 182bad0ba..63f9e305a 100644
--- a/chapter07/fstab.xml
+++ b/chapter07/fstab.xml
@@ -4,7 +4,7 @@
 <para>
 In order for certain programs to be able to determine where certain
 partitions are supposed to be mounted by default, the /etc/fstab file is
-used. Create a new file <filename>/etc/fstab</filename> containing the
+used. A new file <filename>/etc/fstab</filename> is created containing the
 following:
 </para>
 
@@ -23,8 +23,9 @@ proc /proc proc defaults 0 0
 </literallayout>
 
 <para>
-Replace &lt;LFS-partition designation&gt;, &lt;swap-partition
-designation&gt; and &lt;fs-type&gt; with the appropriate values
+&lt;LFS-partition designation&gt;, &lt;swap-partition
+designation&gt; and &lt;fs-type&gt; have to be replaced with the appropriate
+ values
 (/dev/hda2, /dev/hda5 and reiserfs for example).
 </para>
 
diff --git a/chapter07/functions.xml b/chapter07/functions.xml
index dbed6710d..49ce64c76 100644
--- a/chapter07/functions.xml
+++ b/chapter07/functions.xml
@@ -2,7 +2,7 @@
 <title>Creating the functions script</title>
 
 <para>
-Create a new file <filename>/etc/init.d/functions</filename> containing
+A new file <filename>/etc/init.d/functions</filename> is created containing
 the following:
 </para>
 
diff --git a/chapter07/halt.xml b/chapter07/halt.xml
index f7849ad0b..92264f5ab 100644
--- a/chapter07/halt.xml
+++ b/chapter07/halt.xml
@@ -2,7 +2,7 @@
 <title>Creating the halt script</title>
 
 <para>
-Create a new file <filename>/etc/init.d/halt</filename> containing the
+A new file <filename>/etc/init.d/halt</filename> is created containing the
 following:
 </para>
 
diff --git a/chapter07/loadkeys.xml b/chapter07/loadkeys.xml
index bc17fd19d..a3feb387b 100644
--- a/chapter07/loadkeys.xml
+++ b/chapter07/loadkeys.xml
@@ -2,9 +2,10 @@
 <title>Creating the loadkeys script</title>
 
 <para>
-You only need to create this script if you don't have a default 101 keys
-US keyboard layout. Create a new file 
-<filename>/etc/init.d/loadkeys</filename> containing  the following:
+A user only needs to create this script if he don't have a default 101 keys
+US keyboard layout. A new file 
+<filename>/etc/init.d/loadkeys</filename> containing  the following has to be
+created:
 </para>
 
 <literallayout>
diff --git a/chapter07/mountfs.xml b/chapter07/mountfs.xml
index f0fdf7a78..ce80b5c24 100644
--- a/chapter07/mountfs.xml
+++ b/chapter07/mountfs.xml
@@ -2,7 +2,7 @@
 <title>Creating the mountfs script</title>
 
 <para>
-Create a new file <filename>/etc/init.d/mountfs</filename> containing
+A new file <filename>/etc/init.d/mountfs</filename> is created containing
 the following:
 </para>
 
diff --git a/chapter07/rc.xml b/chapter07/rc.xml
index 1e58003c2..989b6c8ac 100644
--- a/chapter07/rc.xml
+++ b/chapter07/rc.xml
@@ -3,7 +3,7 @@
 
 <para>
 The first main bootscript is the <filename>/etc/init.d/rc</filename> script. 
-Create a new file <filename>/etc/init.d/rc</filename> containing the
+A new file <filename>/etc/init.d/rc</filename> is created containing the
 following: </para>
 
 <literallayout>
diff --git a/chapter07/setclock.xml b/chapter07/setclock.xml
index 9e5992c39..11809c770 100644
--- a/chapter07/setclock.xml
+++ b/chapter07/setclock.xml
@@ -2,20 +2,21 @@
 <title>Creating the setclock script</title>
 
 <para>
-The following script is only for real use when your hardware clock (also
+The following script is only for real use when the hardware clock (also
 known as BIOS or CMOS clock) isn't set to GMT time. The recommended
-setup is setting your hardware clock to GMT and have the time converted
-to localtime using the /etc/localtime symbolic link. But if you run an
-OS that doesn't understand a clock set to GMT (most notable are
-Microsoft OS'es) you might want to set your clock to localtime so that
+setup is setting the hardware clock to GMT and having the time converted
+to localtime using the /etc/localtime symbolic link. But if an
+OS is run that doesn't understand a clock set to GMT (most notable are
+Microsoft OS'es) a user might want to set the clock to localtime so that
 the time is properly displayed on those OS'es. This script will reset
 the kernel time to the hardware clock without converting the time using
 the /etc/localtime symlink.
 </para>
 
 <para>
-If you want to use this script on your system even if you have your
-hardware clock set to GMT, then change the UTC variable below to the
+If a user wants to use this script on the system even if the 
+hardware clock is set to GMT, then the UTC variable below has to be changed
+ to the
 value of <emphasis>1</emphasis>.
 </para>
 
@@ -82,8 +83,9 @@ UTC=1
 </literallayout>
 
 <para>
-If your hardware clock (also known as BIOS or CMOS clock) is not set to
-GMT time, than set the UTC variable in the /etc/sysconfig/clock file to
+If the hardware clock (also known as BIOS or CMOS clock) is not set to
+GMT time, then the UTC variable in the /etc/sysconfig/clock file needs to be 
+set to
 the value <emphasis>0</emphasis> (zero).
 </para>
 
diff --git a/chapter07/symperm.xml b/chapter07/symperm.xml
index 044f29d7a..f8195aea7 100644
--- a/chapter07/symperm.xml
+++ b/chapter07/symperm.xml
@@ -2,9 +2,9 @@
 <title>Setting up symlinks and permissions</title>
 
 <para>
-Give these files the proper permissions and create the necessary symlinks
-by running the following commands. If you did not create the loadkeys
-and setclock scripts, make sure you don't type them in the commands
+These files get the proper permissions and the necessary symlinks are created
+by running the following commands. If a user did not create the loadkeys
+and setclock scripts, he has to make sure not to type them in the commands
 below.
 </para>
 
diff --git a/chapter07/sysklogd.xml b/chapter07/sysklogd.xml
index 74e8b9d6d..bad6e6450 100644
--- a/chapter07/sysklogd.xml
+++ b/chapter07/sysklogd.xml
@@ -2,7 +2,7 @@
 <title>Creating the sysklogd script</title>
 
 <para>
-Create a new file <filename>/etc/init.d/sysklogd</filename> containing
+A new file <filename>/etc/init.d/sysklogd</filename> is created containing
 the following:
 </para>
 
diff --git a/chapter07/template.xml b/chapter07/template.xml
index 0c062ca30..37a1363f2 100644
--- a/chapter07/template.xml
+++ b/chapter07/template.xml
@@ -2,7 +2,7 @@
 <title>Creating the template script</title>
 
 <para>
-Create a new file <filename>/etc/init.d/template</filename> containing
+A new file <filename>/etc/init.d/template</filename> is created containing
 the following:
 </para>
 
diff --git a/chapter07/usage.xml b/chapter07/usage.xml
index a2e9adf92..c236bfec0 100644
--- a/chapter07/usage.xml
+++ b/chapter07/usage.xml
@@ -4,7 +4,7 @@
 <para>
 Linux uses a special booting facility named SysVinit. It's based on a
 concept of <emphasis>runlevels</emphasis>. It can be widely different 
-from one system to another, so  don't assume that because things 
+from one system to another, so it can not be assumed that because things 
 worked in &lt;insert distro name&gt; they should work like that in LFS 
 too. LFS has it's own way of doing things, but it respects generally 
 accepted standards.
@@ -14,8 +14,8 @@ accepted standards.
 SysVinit (which we'll call <emphasis>init</emphasis> from now on) works 
 using a runlevels scheme. There are 7 (from 0 to 6) runlevels
 (actually, there are more runlevels but they are for special cases and 
-generally not used. Read the init man page for those details), and each 
-one of those corresponds to the things you want your computer to do when 
+generally not used. The init man page describes those details), and each 
+one of those corresponds to the things the computer is supposed to do when 
 it starts up. The default runlevel is 3. Here are the descriptions of the 
 different runlevels as they are often implemented:
 </para>
@@ -33,7 +33,7 @@ different runlevels as they are often implemented:
 <para>
 The command used to change runlevels is <userinput>init
 &lt;runlevel&gt;</userinput> where &lt;runlevel&gt; is 
-the target runlevel. For example, to reboot the computer, you'd issue
+the target runlevel. For example, to reboot the computer, a user would issue
 the init 6 command. The reboot command is just an alias, as is the halt
 command an alias to init 0.
 </para>
@@ -46,8 +46,9 @@ before any runlevel is executed and runs the scripts listed in
 
 <para>
 There are a number of directories under /etc that look like like rc?.d
-where ? is the number of the runlevel and rcS.d. Take a look at one of 
-them (after you finish this chapter that is, right now there's nothing
+where ? is the number of the runlevel and rcS.d. A user might take a look
+at one of 
+them (after this chapter is finished, right now there's nothing
 there yet). There are a number of symbolic links. Some begin with an K, 
 the others begin with an S, and all of them have three numbers following 
 the initial letter. The K means to stop (kill) a service, and the S means 
@@ -87,22 +88,22 @@ These are descriptions of what the arguments make the scripts do:
 
 <listitem><para>
 <emphasis>reload</emphasis>: The configuration of the service is updated. 
-Use this after you have modified the configuration file of a service, when 
-you don't need/want to restart the service.
+This is used after the configuration file of a service was modified, when 
+the service doesn't need to be restarted.
 </para></listitem>
 
 <listitem><para>
-<emphasis>status</emphasis>: Tells you if the service is running and with 
+<emphasis>status</emphasis>: Tells if the service is running and with 
 which PID's.
 </para></listitem>
 
 </itemizedlist>
 
 <para>
-Feel free to modify the way the boot process works (after all it's your
-LFS system, not ours). The files here are just an example of how you
-can do it in a nice way (well what we consider nice anyway. You may
-hate it).
+Feel free to modify the way the boot process works (after all it's the users
+LFS system, not ours). The files here are just an example of how it can be 
+done 
+in a nice way (well what we consider nice anyway. A user may hate it).
 </para>
 
 </sect1>
diff --git a/chapter08/introduction.xml b/chapter08/introduction.xml
index e64986577..d1c95d498 100644
--- a/chapter08/introduction.xml
+++ b/chapter08/introduction.xml
@@ -3,8 +3,8 @@
 
 <para>
 This chapter will make LFS bootable. This chapter deals with building a
-new kernel for our new LFS system and adding the proper entries to LILO
-so that you can select to boot the LFS system at the LILO: prompt.
+new kernel for the new LFS system and adding the proper entries to LILO
+so that the LFS system can be selected for booting at the LILO: prompt.
 </para>
 
 </sect1>
diff --git a/chapter08/kernel.xml b/chapter08/kernel.xml
index 77db00cda..d60fe0767 100644
--- a/chapter08/kernel.xml
+++ b/chapter08/kernel.xml
@@ -9,9 +9,10 @@ the most recent kernel sources available.
 
 <para>
 Building the kernel involves a few steps: configuring it and compiling
-it. There are a few ways to configure the kernel. If you don't like the
-way this book does it, read the <filename>README</filename> file and find out
-what your other options are. Run the following commands to build the
+it. There are a few ways to configure the kernel. If a user doesn't like the
+way this book does it, he should read the <filename>README</filename>
+file and find out
+what the other options are. The following commands are run to build the
 kernel:
 </para>
 
diff --git a/chapter08/lilo.xml b/chapter08/lilo.xml
index 381f2dc56..c998387b2 100644
--- a/chapter08/lilo.xml
+++ b/chapter08/lilo.xml
@@ -3,7 +3,7 @@
 
 <para>
 In order to being able to boot from this partition, we need to update our
-/etc/lilo.conf file. Add the following lines to lilo.conf by running:
+/etc/lilo.conf file. The following lines get added to lilo.conf by running:
 </para>
 
 <literallayout>
@@ -18,12 +18,12 @@ image=/boot/lfskernel
 </literallayout>
 
 <para>
-&lt;partition&gt; must be replaced by your partition's designation (which
+&lt;partition&gt; must be replaced by the partition's designation (which
 would be /dev/hda5 in my case).
 </para>
 
 <para>
-Now update the boot loader by running:
+Now the boot loader gets updated by running:
 </para>
 
 <blockquote><literallayout>
diff --git a/chapter08/reboot.xml b/chapter08/reboot.xml
index 4ced41b8f..2a71dd631 100644
--- a/chapter08/reboot.xml
+++ b/chapter08/reboot.xml
@@ -3,16 +3,16 @@
 
 <para>
 Now that all software has been installed, bootscripts have been created, 
-it's time for you to reboot your computer. Shutdown your system with
-shutdown -r now and reboot into LFS. After the reboot you will have a normal
-login prompt like you have on your normal Linux system (unless you use XDM or
-some sort of other Display Manger (like KDM - KDE's version of XDM).
+it's time to reboot the computer. The system is shutdown with
+shutdown -r now and rebooted into LFS. After the reboot a normal
+login prompt like on the normal Linux system comes up (unless XDM or
+some sort of other Display Manger is used (like KDM - KDE's version of XDM)).
 </para>
 
 <para>
-One thing remains to be done and that's setting up networking. After you
-rebooted and finished the next chapter of this book your LFS system is
-ready for use and you can do with it whatever you want.
+One thing remains to be done and that's setting up networking. After having
+rebooted and finished the next chapter of this book the LFS system is
+ready for use and can be used to do with it whatever is wanted.
 </para>
 
 </sect1>