--- chap2.xml	2004-10-25 10:53:03.000000000 -0600
+++ chap2.xml.new	2004-10-26 07:51:57.000000000 -0600
@@ -84,7 +84,7 @@
     team..</para>
 
     <para>The last benefit of JRobin is that is helps us to reach our goal of
-    a 100% Pure Java version of OpenNMS that can work write 'of the box' for
+    a 100% Pure Java version of OpenNMS that can work right 'of the box' for
     new users.</para>
 
     <para>Thanks go to the JRobin team for providing this excellent RRD
@@ -110,7 +110,7 @@
     node/interface/service deleted when a node gets deleted rather than
     actually deleting it. (The node completely removed from the database by
     Vacuumd discussed below.) This allows any web pages that are currently
-    viewing the node to react properly. In addition to this the code was
+    viewing the node to react properly. In addition to this, the code was
     changed so that any deletion that occurs as a result of a single operation
     (for example, deleting an node, deleted its interfaces, which deletes its
     services) happens within a single transaction. This means that if a
@@ -135,9 +135,9 @@
     needed to ensure that the data actually got removed eventually. To do this
     Vacuumd was introduced to provide a mechanism to periodically run database
     maintenance operations. Vacuumd's configuration consists of a set of
-    database statements to be run daily (or which every period is preferable).
+    database statements to be run daily (or whichever period is preferable).
     There are four maintenance operations provided by OpenNMS by default.
-    These are as follows: delete nodes have been marked as deleted, delete
+    These are as follows: delete nodes that have been marked as deleted, delete
     interfaces that have been marked as deleted, delete services that have
     been marked as deleted, and delete any event that is not related to a
     current outage and is older than 6 weeks.</para>
@@ -186,13 +186,13 @@
     <para>Installing a fresh copy of OpenNMS will now use the Java Mail API by
     default. Upgrade installs will create two new files that the user will
     have to merge into their existing configurations:
-    d<filename>estinationPaths.xml.rpmnew</filename> and
+    <filename>destinationPaths.xml.rpmnew</filename> and
     <filename>notficationCommands.xml.rpmnew</filename>.</para>
 
     <para>The <filename>javamail-configuration.properties</filename> file
     should be modified to specify the sender's address and the SMTP server
-    address. This file also provides support SMTP servers requiring user and
-    password authentication.</para>
+    address. This file also provides support for SMTP servers requiring user
+    and password authentication.</para>
 
     <para>There are also major changes to the
     <filename>notificationCommands.xml</filename> file. The schema definition