Applied Billy's grammatical patch.

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

chapter01/acknowledgements.xml

@@ -12,7 +12,7 @@ contributions toward the Linux From Scratch project:</para>
 server.</para></listitem>
  
 <listitem><para><ulink url="http://www.valinux.com">VA Linux
-Systems</ulink> for providing rackspace and bandwidth for the 
+Systems</ulink> for providing rack space and bandwidth for the 
 linuxfromscratch.org server.</para></listitem>
 
 <listitem><para><ulink url="http://fredan.org">Fredrik Danerklint</ulink>
@@ -114,7 +114,7 @@ banner.</para></listitem>
 Benson</ulink> &lt;dean@vipersoft.co.uk&gt; for helping out financially
 with setting up the LFS non-profit organization.</para></listitem>
 
-<listitem><para>Countless other people on the various LFS mailinglists who are
+<listitem><para>Countless other people on the various LFS mailing lists who are
 making this book happen by giving their suggestions, testing the book
 and submitting bug reports.</para></listitem>
 

chapter01/blfsbook.xml

@@ -2,10 +2,10 @@
 <title>blfs-book</title>
 
 <para>The blfs-book list is used for coordinating
-the BLFS Book's maintenance.
+the BLFS book's maintenance.
 Traffic on it is mostly Bugzilla and CVS commit messages.
 It is important that all development discussion
-of interest to the Book's users take place on blfs-dev, not here.</para>
+of interest to the book's users take place on blfs-dev, not here.</para>
 
 </sect2>
 

chapter01/blfsdev.xml

@@ -1,7 +1,7 @@
 <sect2>
 <title>blfs-dev</title>
 
-<para>The blfs-dev list is for discussion of BLFS Book development.</para>
+<para>The blfs-dev list is for discussion of BLFS book development.</para>
 
 </sect2>
 

chapter01/blfssupport.xml

@@ -11,7 +11,7 @@ that might be installed on an LFS system.
 
 It does not include topics such as
 the price of beer, what hardware to buy,
-or GNU versus BSD or Microsoft versus Linux flamewars.
+or GNU versus BSD or Microsoft versus Linux flame wars.
 These belong on lfs-chat,
 and since blfs-support is high traffic,
 please follow this rule strictly.

chapter01/how.xml

@@ -50,7 +50,7 @@ computer normally.</para>
 
 <para>When all the software from Chapter 6 is installed, Chapters 7, 8 and 9
 will help us finalize our installation. We will set up our boot
-scripts in Chapter 7. In Chapter 8 we will build our final linux kernel and
+scripts in Chapter 7. In Chapter 8 we will build our final Linux kernel and
 set up the Linux boot loader. Chapter 9 has some pointers to help you after
 you finish the book. Then finally, you reboot your system and boot into your
 new LFS system, and start to really use it.</para>

chapter01/lfsbook.xml

@@ -1,10 +1,10 @@
 <sect2>
 <title>lfs-book</title>
 
-<para>The lfs-book list is used for coordinating the LFS Book's maintenance.
+<para>The lfs-book list is used for coordinating the LFS book's maintenance.
 Traffic on it is mostly Bugzilla and CVS commit messages.
 It is important that all development discussion
-of interest to the Book's users take place on lfs-dev, not here.</para>
+of interest to the book's users take place on lfs-dev, not here.</para>
 
 </sect2>
 

chapter01/lfschat.xml

@@ -4,7 +4,7 @@
 <para>The lfs-chat list is the place for community chatter.
 It's a place where anything goes, nothing is off-topic.
 You can discuss the price of beer or what hardware to buy.
-Even GNU versus BSD and Microsoft versus Linux flamewars
+Even GNU versus BSD and Microsoft versus Linux flame wars
 are okay in lfs-chat.</para>
 
 </sect2>

chapter01/lfsdev.xml

@@ -1,7 +1,7 @@
 <sect2>
 <title>lfs-dev</title>
 
-<para>The lfs-dev list is for discussion of LFS Book development.</para>
+<para>The lfs-dev list is for discussion of LFS book development.</para>
 
 </sect2>
 

chapter01/subscribe.xml

@@ -1,7 +1,7 @@
 <sect2>
 <title>How to subscribe?</title>
 
-<para>Any of the above-mentioned mailinglists can be subscribed to by sending
+<para>Any of the above-mentioned mailing lists can be subscribed to by sending
 an email to <ulink url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink> 
 and writing <emphasis>subscribe listname</emphasis> as the subject 
 header of the message.</para>

chapter05/fileutils-inst.xml

@@ -34,7 +34,7 @@ than likely result in all kinds of compile time problems.</para>
 
 <para><screen><userinput>make</userinput></screen></para>
 
-<para>And finsh off installing the package:</para>
+<para>And finish off installing the package:</para>
 
 <para><screen><userinput>make install</userinput></screen></para>
 

chapter06/config-shadowpwd.xml

@@ -7,9 +7,9 @@ file within the unpacked shadow password suite's source tree. There's one
 thing to keep in mind if you decide to use shadow support: that 
 programs that need to verify passwords (for example xdm, ftp daemons, 
 pop3 daemons) need to be 'shadow-compliant', that is they need to
-be able to work with shadow'ed passwords.</para>
+be able to work with shadowed passwords.</para>
 
-<para>To enable shadow'ed passwords, run the following command:</para>
+<para>To enable shadowed passwords, run the following command:</para>
 
 <para><screen><userinput>/usr/sbin/pwconv</userinput></screen></para>
 

chapter06/gcc-exp.xml

@@ -2,11 +2,11 @@
 <title>Command explanations</title>
 
 <para><userinput>--enable-threads=posix:</userinput> This enables C++
-exception handling for multithreaded code.</para>
+exception handling for multi-threaded code.</para>
 
 <para><userinput>--enable-__cxa_atexit:</userinput> This option will result
 in C++ shared libraries and C++ programs that are interoperable with other
-linux distributions.</para>
+Linux distributions.</para>
 
 <para><userinput>--enable-clocale=gnu:</userinput> There is a risk that
 some people will build ABI incompatible C++ libraries if they didn't install

chapter07/setclock.xml

@@ -26,7 +26,7 @@ UTC=1
 
 <para>Now, you may want to take a look at a very good hint explaining how we
 deal with time on LFS at <ulink url="&hints-root;time.txt"/>. 
-It explains issues such as timezones, UTC, and the TZ environment
+It explains issues such as time zones, UTC, and the TZ environment
 variable.</para>
 
 </sect1>

chapter09/whatnow.xml

@@ -24,7 +24,7 @@ submitted by volunteers in the LFS community. The Hints are available at
 
 <listitem><para>Mailing lists</para>
 
-<para>There are several LFS mailinglists you may subscribe to if you are
+<para>There are several LFS mailing lists you may subscribe to if you are
 in need of help. See <xref linkend="ch01-maillists"/> for more
 information.</para></listitem>
 

index.xml

@@ -4,8 +4,8 @@
 
 <!ENTITY book SYSTEM "book/book.xml">
 
-<!ENTITY version "20030111">
-<!ENTITY releasedate "January 11th, 2003">
+<!ENTITY version "20030113">
+<!ENTITY releasedate "January 13th, 2003">
 
 <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
 <!ENTITY http-root "http://ftp.linuxfromscratch.org">

preface/foreword.xml

@@ -8,7 +8,7 @@ the bootscripts. I didn't like the way certain programs were configured by
 default. Much more of that sort of thing bothered me. Finally I realized
 that if I wanted full satisfaction from my Linux system I would have to
 build my own system from scratch, using only the source code. I resolved
-not to use pre-compiled packages of any kind, nor CD-ROM or bootdisk that
+not to use pre-compiled packages of any kind, nor CD-ROM or boot disk that
 would install some basic utilities. I would use my current Linux system to
 develop my own.</para>
 

preface/whonotread.xml

@@ -4,7 +4,7 @@
 
 <para>If you do not wish to build your own Linux system from scratch, then
 you probably don't want to read this book. Our goal is to build a complete
-and useable foundation system. If you only want to know what happens while
+and usable foundation system. If you only want to know what happens while
 your computer boots, then we recommend the
 <quote>From Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare
 system which is similar to that of this book, but it focuses strictly on

preface/whoread.xml

@@ -36,7 +36,7 @@ other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
 This allows you to review it, to omit unwanted ingredients, and to
 add your own ingredients which enhance the flavor of your burger. When you
 are satisfied with the recipe, you go on to preparing it. You make it just
-the way you like it: broil it, bake it, deep-fry it, barbeque it, or eat it
+the way you like it: broil it, bake it, deep-fry it, barbecue it, or eat it
 tar-tar (raw).</para>
 
 <para>Another analogy that we can use is that of comparing LFS with a