diff --git a/xdocs/guide.xml b/xdocs/guide.xml
index 89db29a..dc86f9b 100644
--- a/xdocs/guide.xml
+++ b/xdocs/guide.xml
@@ -147,7 +147,7 @@ commonly set by placing a file named commons-logging.properties in the classpath
 When such a file exists, every entry in the properties file becomes an "attribute"
 of the LogFactory. When there is more than one such file in the classpath, releases
 of commons-logging prior to 1.1 simply use the first one found. From release 1.1,
-each file may define a <code>priority</code> key in each file, and the file with
+each file may define a <code>priority</code> key, and the file with
 the highest priority is used (no priority definition implies priority of zero).
 When multiple files have the same priority, the first one found is used.
 </p>
diff --git a/xdocs/tech.xml b/xdocs/tech.xml
index 4296739..f64f755 100644
--- a/xdocs/tech.xml
+++ b/xdocs/tech.xml
@@ -646,7 +646,7 @@ href='http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com
 	This is the strategy adopted by JCL.
 			</p>
 			<p>
-	JCL uses the context classloader to use the <code>Log</code> implementation. 
+	JCL uses the context classloader to load the <code>Log</code> implementation. 
 			</p>
     	</subsection>
 	</section>
diff --git a/xdocs/troubleshooting.xml b/xdocs/troubleshooting.xml
index 869cbb0..399cfe1 100644
--- a/xdocs/troubleshooting.xml
+++ b/xdocs/troubleshooting.xml
@@ -88,7 +88,7 @@ up the understanding of the classloader environment required to diagnose JCL pro
     </subsection>
     <subsection name='Diagnostic Message Prefix'>
       <p>
-Each diagnostic message is prefixed with details of the class being logger in a standard format.
+Each diagnostic message is prefixed with details of the relevant class in a standard format.
 This takes the form:
     </p>
 <code><pre>