You's

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

chapter05/kernel-inst.xml

@@ -10,7 +10,7 @@ compile package that need the kernel.
 </para>
 
 <para>
-Create the kernel configuration file by running the following command:
+The kernel configuration file is created by running the following command:
 </para>
 
 <blockquote><literallayout>

chapter05/proc.xml

@@ -10,7 +10,7 @@ the kernel itself.
 </para>
 
 <para>
-Mount the proc file system under $LFS/proc by running the following command:
+The proc file system is mounted under $LFS/proc by running the following command:
 </para>
 
 <blockquote><literallayout>

chapter05/pwdgroup.xml

@@ -7,7 +7,7 @@ it needs an entry in the /etc/passwd and /etc/group file. Besides the
 group root a couple of other groups are recommended and needed by
 packages. The groups with their GID's below aren't part of any standard.
 The LSB only recommends besides a group root a group bin to be present
-with GID 1. Other group names and GID's can be chosen by yourself. Well
+with GID 1. Other group names and GID's can be chosen by the user. Well
 written packages don't depend on GID numbers but just use the group
 name, it doesn't matter all that much what GID a group has. Since there
 aren't any standards for groups I won't follow any conventions used by

chapter05/tar-inst.xml

@@ -2,9 +2,9 @@
 <title>Installation of Tar</title>
 
 <para>
-If you want to be able to directly use bzip2 files with tar, use the tar
+To be able to directly use bzip2 files with tar, use the tar
 patch avaiable from the LFS FTP site. This patch will add the -y option
-to tar which works the same as the -z option to tar (which you can use
+to tar which works the same as the -z option to tar (which can be used
 for gzip files).
 </para>
 

chapter06/netkitbase.xml

@@ -18,7 +18,7 @@ Install Netkit-base by running the following commands:
 <para>
 There are other files in the <filename
 class="directory">etc.sample</filename> directory which might be of
-interest to you.
+interest to the user.
 </para>
 
 </sect2>

chapter06/nettools.xml

@@ -2,8 +2,8 @@
 <title>Installing Net-tools</title>
 
 <para>
-Edit the <filename>Makefile</filename> file and edit the CFLAGS variable
-if you want to add compiler optimzations.
+The <filename>Makefile</filename> file CFLAGS variable has to be edited
+if compiler optimzations should be added.
 </para>
 
 <para>

chapter07/ethnet-symperm.xml

@@ -2,7 +2,7 @@
 <title>Setting up permissions and symlink</title>
 
 <para>
-Set the proper file permissions and create the necessary symlink by
+The proper file permissions and the necessary symlinks are set or created by
 running the following commands:
 </para>
 

chapter07/ethnet.xml

@@ -2,12 +2,12 @@
 <title>Creating the /etc/init.d/ethnet script</title>
 
 <para>
-This section only applies if you are going to configure a network card.
-If you're not, skip this section.
+This section only applies if a user is going to configure a network card.
+If not, this section can be skipped.
 </para>
 
 <para>
-Create a new file <filename>/etc/init.d/ethnet</filename> containing the
+A new file <filename>/etc/init.d/ethnet</filename> is created containing the
 following:
 </para>
 
@@ -119,7 +119,7 @@ esac
 <title>Adding default gateway to /etc/sysconfig/network</title>
 
 <para>
-If you require a default gateway to be setup, run the following command:
+If a default gateway is required to be setup, the following command does that:
 </para>
 
 <literallayout>
@@ -131,7 +131,7 @@ GATEWAY=192.168.1.2
 </literallayout>
 
 <para>
-Change GATEWAY to match your network setup.
+GATEWAY needs to be changed to match the network setup.
 </para>
 
 </sect2>
@@ -143,11 +143,11 @@ Change GATEWAY to match your network setup.
 Which interfaces are brought up and down by the ethnet script depends on
 the files in the /etc/sysconfig/network-scripts directory. This
 directory should contain files in the form of ifcfg-x where x is an
-identification number (or whatever you choose to name it).
+identification number (or whatever a user named it).
 </para>
 
 <para>
-First create the network-scripts directory by running:
+First the network-scripts directory is created by running:
 </para>
 
 <blockquote><literallayout>
@@ -158,8 +158,8 @@ First create the network-scripts directory by running:
 
 <para>
 
-Now, create new files in that directory containing the following.
-The following creates a sample file ifcfg-eth0:
+Now, new files are created in that directory containing the following.
+This creates a sample file ifcfg-eth0:
 </para>
 
 <blockquote><literallayout>
@@ -176,7 +176,8 @@ BROADCAST=192.168.1.255
 </literallayout></blockquote>
 
 <para>
-Of course, change the values of those four variables in every file to
+Of course, the values of those four variables have to be changed 
+in every file to
 match the proper setup. Usually NETMASK and BROADCAST will remain the
 same, just the DEVICE IP variables will change per network interface. If 
 the ONBOOT variable is set to yes, the ethnet script will bring it up 

chapter07/hosts.xml

@@ -2,7 +2,7 @@
 <title>Creating the /etc/hosts file</title>
 
 <para>
-If you want to configure a network card, you have to decide on the
+If a network card is to be configured, a user has to decide on the
 IP-address, FQDN and possible aliases for use in the /etc/hosts file. An
 example is:
 </para>
@@ -14,8 +14,8 @@ example is:
 </literallayout></blockquote>
 
 <para>
-Make sure the IP-address is in the private network IP-address range.
-Valid ranges are:
+It should made sure that the IP-address is in the private network
+IP-address range. Valid ranges are:
 </para>
 
 <blockquote><literallayout>
@@ -33,14 +33,14 @@ be www.linuxfromscratch.org
 </para>
 
 <para>
-If you're not going to use a network card, you still need to come up with a
+If a user is not going to use a network card, he still needs to come up with a
 FQDN. This is necessary for programs like Sendmail to operate correctly (in
 fact; Sendmail won't run when it can't determine the FQDN).
 </para>
 
 <para>
-If you don't configure a network card, create a new file
-<filename>/etc/hosts</filename> by running:
+If a network card is not going to be configured, a new file
+<filename>/etc/hosts</filename> is created by running:
 </para>
 
 <literallayout>
@@ -56,8 +56,8 @@ If you don't configure a network card, create a new file
 </literallayout>
 
 <para>
-If you do configure a network card, create a new file
-<filename>/etc/hosts</filename> containing:
+If a network card is to be configured, a new file
+<filename>/etc/hosts</filename> is created containing:
 </para>
 
 <literallayout>
@@ -74,9 +74,10 @@ If you do configure a network card, create a new file
 </literallayout>
 
 <para>
-Of course, change the 192.168.1.1 and www.mydomain.org to your own
-liking (or requirements if you are assigned an IP-address by a network/system
-administrator and you plan on connecting this machine to that network).
+Of course, the 192.168.1.1 and www.mydomain.org have to be changed to the 
+users 
+liking (or requirements if assigned an IP-address by a network/system
+administrator and this machine is planned to be connected to that network).
 </para>
 
 </sect1>

chapter07/introduction.xml

@@ -2,7 +2,7 @@
 <title>Introduction</title>
 
 <para>
-This chapter will setup basic networking. Although you might not be
+This chapter will setup basic networking. Although the system might not be
 connected to a network, Linux software uses network functions anyway.
 We'll be installing at least the local loopback device and a network
 card as well if applicable. Also the proper bootscripts will be created

chapter07/localnet-symperm.xml

@@ -2,7 +2,7 @@
 <title>Setting up permissions and symlink</title>
 
 <para>
-Set the proper file permissions and create the necessary symlink by
+The proper file permissions and the necessary symlink are set or created by
 running the following commands:
 </para>
 

chapter07/localnet.xml

@@ -2,7 +2,7 @@
 <title>Creating the /etc/init.d/localnet bootscript</title>
 
 <para>
-Create a new file <filename>/etc/init.d/localnet</filename> containing
+A new file <filename>/etc/init.d/localnet</filename> is created containing
 the following:
 </para>
 

chapter07/network.xml

@@ -2,8 +2,8 @@
 <title>Creating the /etc/sysconfig/network file</title>
 
 <para>
-Create a new file <filename>/etc/sysconfig/network</filename> and put the 
-hostname in it by running:
+A new file <filename>/etc/sysconfig/network</filename> is created and the 
+hostname is put in it by running:
 </para>
 
 <blockquote><literallayout>
@@ -13,8 +13,9 @@ hostname in it by running:
 </literallayout></blockquote>
 
 <para>
-Replace <quote>lfs</quote> by the name you wish to call your computer.
-Please not that you should not enter the FQDN (Fully Qualified Domain
+<quote>lfs</quote> needs to be replaced by the name the computer is to be 
+called.
+A user should not enter the FQDN (Fully Qualified Domain
 Name) here. That information will be put in the
 <filename>/etc/hosts</filename> file later.
 </para>