Index: introduction/important/bootscripts.xml
===================================================================
--- introduction/important/bootscripts.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/important/bootscripts.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -17,5 +17,5 @@
 <para>The blfs-bootscripts package will be used throughout the <acronym>BLFS</acronym>
 book for startup scripts.  Unlike <acronym>LFS</acronym>, each init script
-has a seperate install target in the blfs-bootscripts package. 
+has a separate install target in the blfs-bootscripts package. 
 It is recomended you keep the package
 source directory around until completion of your
Index: introduction/important/patches.xml
===================================================================
--- introduction/important/patches.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/important/patches.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -14,7 +14,7 @@
 </itemizedlist>
 
-<para>In short, the book only includes patches that are either Required or
-Recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
-which hosts various patches (including the patches included in the books)
+<para>In short, the book only includes patches that are either required or
+recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
+which hosts various patches (including the patches referenced in the books)
 to enable you to configure your <acronym>LFS</acronym> the way you like it.</para>
 
Index: introduction/important/pkgmgt.xml
===================================================================
--- introduction/important/pkgmgt.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/important/pkgmgt.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -99,5 +99,5 @@
 mentioned in <xref linkend="intro-important-beyond"/> need to be expanded to
 include <filename>/usr/pkg/foo</filename>. For more than a few packages,
-this scheme becomes unmanagable.</para>
+this scheme becomes unmanageable.</para>
 
 </sect3>
@@ -111,9 +111,9 @@
 to expand the environment variables. Though the symlinks can be created by the user,
 to automate the creation, many package managers have been written on this approach.
-Few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
+A few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
 
 <para>The installation needs to be faked, so that the package thinks that it is
-installed in <filename>/usr</filename> though in reality it is installed in
-<filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
+installed in <filename class="directory">/usr</filename> though in reality it is installed in
+<filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
 task. For example, consider that you are installing a package libfoo-1.1. The following
 instructions may not install the package properly:</para>
Index: introduction/important/unpacking.xml
===================================================================
--- introduction/important/unpacking.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/important/unpacking.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -75,5 +75,5 @@
 staring at the screen hoping to catch a particular error or warning. Log files
 are also useful for debugging and keeping records. The following command
-allows you to create a installation log. Replace &lt;command&gt; with the
+allows you to create an installation log. Replace &lt;command&gt; with the
 command you intend to execute.</para>
 
@@ -81,5 +81,5 @@
 
 <para><parameter>2&gt;&amp;1</parameter> redirects error messages
-to the same location as normal output. The <command>tee</command> command
+to the same location as standard output. The <command>tee</command> command
 allows viewing of the output while logging the results to a file. The parentheses
 around the command run the entire command in a subshell and finally the
Index: introduction/welcome/askhelp.xml
===================================================================
--- introduction/welcome/askhelp.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/welcome/askhelp.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -20,6 +20,6 @@
 <itemizedlist>
 <listitem><para>Is the hardware support compiled into the kernel or
-available as a module to the kernel.  If it is a module, is it configured
-properly in <filename>modules.conf</filename> and has it been loaded.  You
+available as a module to the kernel?  If it is a module, is it configured
+properly in <filename>modules.conf</filename> and has it been loaded?  You
 should use <command>lsmod</command> as root to see if it's loaded. Check the
 <filename>sys.log</filename> or run <command>modprobe &lt;driver&gt;
@@ -28,11 +28,10 @@
 
 <listitem><para>Are your permissions properly set, especially for
-devices. <acronym>LFS</acronym> uses groups to make these settings easier, but 
+devices? <acronym>LFS</acronym> uses groups to make these settings easier, but 
 it also adds the step of adding users to groups to allow access. A simple
 <command>moduser -G audio &lt;user&gt;</command> may be all that's necessary 
 for that user to have access to the sound system.  Any question that starts 
-out with "It works as root, but not as ..." should review permissions
-thoroughly
-prior to asking.</para></listitem>
+out with "It works as root, but not as ..." requires a thorough review
+of permissions prior to asking.</para></listitem>
 
 <listitem><para><acronym>BLFS</acronym> liberally uses <filename>
@@ -40,6 +39,6 @@
 need to expand your environment variables for each package placed there (e.g.
 PATH=$PATH:/opt/kde/bin).  In some cases, the package will walk you
-through the changes, but some will not.  <xref linkend="intro-important-beyond"/> 
-is available to help you check.</para></listitem>
+through the changes, but some will not.  The section called "<ulink
+url="beyond.html">Going Beyond BLFS</ulink>" is available to help you check.</para></listitem>
 </itemizedlist></sect2>
 
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/welcome/changelog.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -11,4 +11,8 @@
 
 <itemizedlist>
+
+<listitem><para>May 29th, 2004 [igor]: Applied fixes for various
+grammar and spelling errors, suggested by Randy
+McMurchy.</para></listitem>
 
 <listitem><para>May 29th, 2004 [igor]: Moved the samba maintainer
Index: introduction/welcome/conventions.xml
===================================================================
--- introduction/welcome/conventions.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/welcome/conventions.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -44,4 +44,8 @@
 Therefore, this whole section is generally typed as seen.</para></blockquote>
 
+<para><replaceable>[REPLACED TEXT]</replaceable></para>
+
+<blockquote><para>This form of text is used to encapsulate text that is
+not to be typed as seen or copy and pasted.</para></blockquote>
+
 </sect1>
-
Index: introduction/welcome/version.xml
===================================================================
--- introduction/welcome/version.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ introduction/welcome/version.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -4,5 +4,5 @@
 
 <para>This is <acronym>BLFS</acronym>-BOOK version &version; dated &releasedate;. 
-If this version is older than a month a newer version is probably already 
+If this version is older than a month, a newer version is probably already 
 available for download. Check one of the mirror sites below for updated
 versions.</para>
Index: preface/foreword.xml
===================================================================
--- preface/foreword.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ preface/foreword.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -22,5 +22,5 @@
 
 <para>Thanks as ever go to everyone in the <acronym>LFS</acronym>/<acronym>BLFS</acronym> 
-community especially those who have contributed instructions, written text, 
+community; especially those who have contributed instructions, written text, 
 answered questions and generally shouted when things were wrong!</para>
 
Index: preface/organization.xml
===================================================================
--- preface/organization.xml	(revision bb0d842be5dce03fe0e5f28758d9b54604c194b6)
+++ preface/organization.xml	(revision aa15d3ead6d17ac24d525a078e040b2ceeb297f3)
@@ -36,10 +36,9 @@
 
 <sect2><title>Part VII - Content Serving</title>
-<para>In this part we deal with databases and web server software
-<!--(including php)-->.</para></sect2>
+<para>In this part we deal with databases and web server software.</para></sect2>
 
 <sect2><title>Part VIII - X + Window Managers</title>
 <para>This part explains how to set up a basic
-<application>XFree86</application> installation along
+X Window System installation along
 with some generic <application>X</application> libraries and Window managers.</para></sect2>
 
