You

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

1 files changed, 14 insertions, 13 deletions

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>