fixed setup to 'set up'

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

appendixa/bootscripts-desc.xml

@@ -39,7 +39,7 @@ device.</para></sect4>
 or aren't network based.</para></sect4>
 
 <sect4><title>network</title>
-<para>The network script setup network interfaces (such as network cards)
+<para>The network script sets up network interfaces (such as network cards)
 and sets up the default gateway where applicable.</para></sect4>
 
 <sect4><title>rc</title>

chapter01/changelog.xml

@@ -243,7 +243,7 @@ binutils-2.12</para></listitem>
 here hinted towards the fact that you could skip configuring this step
 which isn't true unless the entire script would be removed. So the text was
 changed a bit to just have them create the file no matter how the hardware
-clock is setup.</para></listitem>
+clock is set up.</para></listitem>
 
 <listitem><para>March 11th, 2002 [gerard]: Chapter 07 - Loadkeys: Removed
 the need to configure a <filename>/etc/sysconfig/keyboard</filename> file.
@@ -497,7 +497,7 @@ files (dependencies, download location, descriptions)</para></listitem>
 installation.</para></listitem>
 
 <listitem><para>January 15th, 2002 [gerard]: Chapter 7: Removed most of the
-scripts, only left the part of a few where we setup up config files in
+scripts, only left the part of a few where we set up config files in
 /etc/sysconfig.</para></listitem>
 
 <listitem><para>January 15th, 2002 [gerard]: Chapter 6 - Configuring

chapter01/how.xml

@@ -29,8 +29,8 @@ still use your host system. While software is being installed you can
 simply switch to a different VC (Virtual Console) or X desktop and
 continue using your computer as you normally would.</para>
 
-<para>When all the software is installed, chapter 7 will setup the boot
-scripts. Chapter 8 will setup the Linux boot loader and in chapter 9
+<para>When all the software is installed, chapter 7 will set up the boot
+scripts. Chapter 8 will set up the Linux boot loader and in chapter 9
 there are some pointers what you can do after you finish the book. Then
 you can finally reboot your system into your new LFS system, and start
 to really use it.</para>

chapter02/download.xml

@@ -11,7 +11,7 @@ makes sense because you would still have access to those files when you boot
 into the LFS system. $LFS/usr/src is just a logical place to store source
 code, but by no means a requirement. You may even want to create a
 subdirectory under $LFS/usr/src for tarball storage. That way you can
-seperate tarballs from temporary build directories, but again that's up
+separate tarballs from temporary build directories, but again that's up
 to you.</para>
 
 <para>The next chapter contains a list of all the packages that need to be

chapter05/installasuser.xml

@@ -25,7 +25,7 @@ as root to change the ownership of the LFS partition to user "lfs":</para>
 <para>Now you can login as user "lfs". You can do this two ways: either
 the normal way through the console or the display manager, or with
 <userinput>su - lfs</userinput>. When you're working as user "lfs", type
-the following commands to setup a good environment to work in:</para>
+the following commands to set up a good environment to work in:</para>
 
 <para><screen><userinput>cat &gt; ~/.bash_profile &lt;&lt; "EOF"
 umask 022

chapter05/introduction.xml

@@ -31,7 +31,7 @@ about improper use of the C or C++ syntax, but not illegal use. It's just
 that, often, C standards changed and packages still use the old standard 
 which is not a problem).</para>
 
-<para>Before we start, make sure the LFS environment variable is setup
+<para>Before we start, make sure the LFS environment variable is set up
 properly if you decided to make use of it. Run the following:</para>
 
 <para><screen><userinput>echo $LFS</userinput></screen></para>

chapter06/config-keyboard.xml

@@ -15,7 +15,7 @@ example, if you have a Dutch keyboard, you would run:</para>
 
 <para><screen><userinput>ln -s i386/qwerty/nl.map.gz /usr/share/kbd/keymaps/defkeymap.map.gz</userinput></screen></para>
 
-<para>An second option to configure your keyboard's layout is to compile
+<para>A second option to configure your keyboard's layout is to compile
 the keymap directly into the kernel. This will make sure that your
 keyboard always works as expected, even when you have booted into
 maintenance mode (by passing `init=/bin/sh' to the kernel) in which case

chapter07/introduction.xml

@@ -2,9 +2,9 @@
 <title>Introduction</title>
 <?dbhtml filename="introduction.html" dir="chapter07"?>
 
-<para>This chapter will setup the bootscripts that you installed in chapter
+<para>This chapter will set up the bootscripts that you installed in chapter
 6. Most of these scripts will work without needing to modify them, but a
-few do require additional configuration files setup as they deal with
+few do require additional configuration files set up as they deal with
 hardware dependent information.</para>
 
 </sect1>

chapter07/loadkeys.xml

@@ -4,7 +4,7 @@
 
 <para>If you decided to compile your keymap file directly into the kernel
 back at the end of chapter 6, then you strictly speaking don't need to run
-this loadkeys script, since the kernel has already setup the keymap for
+this loadkeys script, since the kernel has already set up the keymap for
 you. You can still run it if you want, it isn't going to hurt you. It could
 even be beneficial to keep it in case you run a lot of different kernels
 and don't remember or want to compile the keymap into every kernel you lay

chapter07/network.xml

@@ -14,7 +14,7 @@ runlevel directories
 <sect2>
 <title>Configuring default gateway</title>
 
-<para>If you're on a network you may need to setup the default gateway for
+<para>If you're on a network you may need to set up the default gateway for
 this machine. This is done by adding the proper values to the
 /etc/sysconfig/network file by running the following:</para>