Index: chapter01/changelog.xml
===================================================================
--- chapter01/changelog.xml	(revision e750af101fb820df3d9c1ab896da023fb541d2a8)
+++ chapter01/changelog.xml	(revision afbe6d98bab669abaec096139e952be3f9192c39)
@@ -13,6 +13,6 @@
 mirrors via <ulink url="&lfs-root;"/>.</para>
 
-<para>Below is a list of changes made since the previous release of the book,
-first a summary, then a detailed log.</para>
+<para>Below is a list of changes made since the previous release of the book.
+First a summary, then a detailed log.</para>
 
 <itemizedlist>
@@ -84,4 +84,10 @@
 </listitem>
 
+<listitem><para>May 12th, 2005 [matt]: More wording and tagging improvements
+(thanks to Peter Ennis and Tony Morgan)</para></listitem>
+
+<listitem><para>May 12th, 2005 [matt]: Minor wording improvements (thanks to
+Peter Ennis)</para></listitem>
+
 <listitem><para>April 27th, 2005 [archaic]: Added a patch to fix 2 glibc
 testsuite failures when the running kernel is 2.6.11.x.</para></listitem>
@@ -133,5 +139,5 @@
 </listitem>
 
-<listitem><para>April 4, 2005 [matt]: Fix E2fsprogs compile problem (Ken Moffat
+<listitem><para>April 4, 2005 [matt]: Fix e2fsprogs compile problem (Ken Moffat
 &amp; Greg Schafer)</para></listitem>
 
@@ -193,5 +199,5 @@
 </listitem>
 
-<listitem><para>March 14, 2005 [jim]: Added /var/log/hotplug for capturing
+<listitem><para>March 14, 2005 [jim]: Added <filename class="directory">/var/log/hotplug</filename> for capturing
 of hotplug events. Added /lib/firmware for firmware loading with hotplug</para></listitem>
 
@@ -239,6 +245,6 @@
 </para></listitem>
 
-<listitem><para>February 28, 2005 [matt]: Move /usr/bin/logger to /bin
-as the bootscripts need it there.  Fixes bug 1035.</para>
+<listitem><para>February 28, 2005 [matt]: Move <filename>/usr/bin/logger</filename>
+to <filename class="directory">/bin</filename> as the bootscripts need it there.  Fixes bug 1035.</para>
 </listitem>
 
@@ -275,5 +281,5 @@
 
 <listitem><para>February 19, 2005 [jeremy]: Added correction to chapter 5
-glibc build to correct the disabling of selinux functionality.  Thanks to
+glibc build to fix the disabling of selinux functionality.  Thanks to
 Bobson on IRC (bobson@bobson.net) for pointing this out.  Closes bugzilla
 1034.</para></listitem>
@@ -360,5 +366,5 @@
 from version 5.1.</para></listitem>
 
-<listitem><para>December 20, 2004 [manuel]: Made Grub's configuration location 
+<listitem><para>December 20, 2004 [manuel]: Made grub's configuration location 
 FHS compliant.</para></listitem>
 
Index: chapter02/creatingfilesystem.xml
===================================================================
--- chapter02/creatingfilesystem.xml	(revision e750af101fb820df3d9c1ab896da023fb541d2a8)
+++ chapter02/creatingfilesystem.xml	(revision afbe6d98bab669abaec096139e952be3f9192c39)
@@ -10,7 +10,7 @@
 <para>Now that a blank partition has been set up, the file system can
 be created. The most widely-used system in the Linux world is the
-second extended file system (ext2), but with the newer high-capacity
-hard disks, the journaling file systems are becoming increasingly
-popular.  Here we will create an ext2 file system, but build
+second extended file system (ext2), but with newer high-capacity
+hard disks, journaling file systems are becoming increasingly
+popular.  We will create an ext2 file system, however build
 instructions for other file systems can be found at <ulink
 url="&blfs-root;view/svn/postlfs/filesystems.html"><phrase 
@@ -52,6 +52,5 @@
 
 <para>If a swap partition was created, it will need to be initialized
-as a swap partition too (also known as formatting, as described above
-with <command>mke2fs</command>) by running the following. If you are using an existing
+as a swap partition by using the command below. If you are using an existing
 swap partition, there is no need to format it.</para>
 
Index: chapter02/creatingpartition.xml
===================================================================
--- chapter02/creatingpartition.xml	(revision e750af101fb820df3d9c1ab896da023fb541d2a8)
+++ chapter02/creatingpartition.xml	(revision afbe6d98bab669abaec096139e952be3f9192c39)
@@ -8,9 +8,8 @@
 <?dbhtml filename="creatingpartition.html"?>
 
-<!--Edit Me-->
 <para>Like most other operating systems, LFS is usually installed on
-a dedicated partition.  If you have an empty partition or enough
-unpartitioned space on one of your hard disks to make one, using this
-for your LFS installation is recommended.  However, an LFS system (in
+a dedicated partition.  The recommended approach to building an LFS
+system is to use an available empty partition or, if you have enough
+unpartitioned space, to create one. However, an LFS system (in
 fact even multiple LFS systems) may also be installed on a partition
 already occupied by another operating system and the different systems
@@ -20,5 +19,4 @@
 explains how to implement this, whereas this book discusses the method of
 using a fresh partition for the installation.</para>
-<!--End Edit Me-->
 
 <para>A minimal system requires a partition of around 1.3 gigabytes
@@ -27,6 +25,6 @@
 Linux system, additional software will probably be installed which
 will require additional space (2 or 3 GB). The LFS system itself will
-not take up this much space. A large portion of this required amount
-of space is to provide sufficient free temporary space. Compiling
+not take up this much room. A large portion of this requirement
+is to provide sufficient free temporary storage. Compiling
 packages can require a lot of disk space which will be reclaimed after
 the package is installed.</para>
@@ -34,9 +32,9 @@
 <para>Because there is not always enough Random Access Memory (RAM)
 available for compilation processes, it is a good idea to use a small
-disk partition as swap space.  This space is used by the kernel to
-store seldom-used data to make room in memory for active processes.
+disk partition as swap space.  This is used by the kernel to
+store seldom-used data and leave more memory available for active processes.
 The swap partition for an LFS system can be the same as the one used
-by the host system, so another swap partition will not need to be
-created if your host system already has one setup.</para>
+by the host system, in which case it is not necessary to create another
+one.</para>
 
 <para>Start a disk partitioning program such as
Index: chapter05/glibc.xml
===================================================================
--- chapter05/glibc.xml	(revision e750af101fb820df3d9c1ab896da023fb541d2a8)
+++ chapter05/glibc.xml	(revision afbe6d98bab669abaec096139e952be3f9192c39)
@@ -145,5 +145,5 @@
 importance, please see <xref linkend="ch-system-glibc" role="."/></para>
 
-<para>In this chapter, some tests can be adversely effected by
+<para>In this chapter, some tests can be adversely affected by
 existing tools or environmental issues on the host system. Glibc test
 suite failures in this chapter are typically not worrisome. The Glibc
Index: chapter05/toolchaintechnotes.xml
===================================================================
--- chapter05/toolchaintechnotes.xml	(revision e750af101fb820df3d9c1ab896da023fb541d2a8)
+++ chapter05/toolchaintechnotes.xml	(revision afbe6d98bab669abaec096139e952be3f9192c39)
@@ -67,5 +67,5 @@
 
 <listitem><para>Careful manipulation of <command>gcc</command>'s
-<filename>specs</filename> file tell the compiler which target dynamic
+<filename>specs</filename> file tells the compiler which target dynamic
 linker will be used</para></listitem>
 </itemizedlist>
@@ -78,5 +78,5 @@
 result in a subtly broken toolchain, where the impact of such breakage
 might not show up until near the end of the build of an entire
-distribution. A test suite failure will usually alert this error
+distribution. A test suite failure will usually highlight this error
 before too much additional work is performed.</para>
 
Index: general.ent
===================================================================
--- general.ent	(revision e750af101fb820df3d9c1ab896da023fb541d2a8)
+++ general.ent	(revision afbe6d98bab669abaec096139e952be3f9192c39)
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "TESTING-20050428">
-<!ENTITY releasedate "April 28, 2005">
+<!ENTITY version "TESTING-20050512">
+<!ENTITY releasedate "May 12, 2005">
 <!ENTITY milestone "6.1">
 
