diff --git a/doc/apidocs.xml b/doc/apidocs.xml
index c3153cfcabbf03132371b783b21ede2cfdd54719..50f0425014efda4bd650b425ad79d10eb8b8252b 100644
--- a/doc/apidocs.xml
+++ b/doc/apidocs.xml
@@ -19,7 +19,7 @@
 		You are encouraged to read this document for a better
 		understanding of the SAX API in &XercesCName;.</p>
 
-	    <p><em><jump href="apiDocs/index.html">Click here for the &XercesCName; API documentation.</jump></em></p>
+	    <p>See the <em><jump href="apiDocs/index.html">&XercesCName; API documentation.</jump></em> for more details.</p>
 
 	    <note>The API documentation is automatically generated using
 		<jump href="http://www.stack.nl/~dimitri/doxygen/">doxygen</jump> and
diff --git a/doc/buildc.xml b/doc/buildc.xml
index a4e596e176fa6adf31ef9f5fc4546bb20dc39992..9befb7073b4f5e545827009757ec1f8e18f93568 100644
--- a/doc/buildc.xml
+++ b/doc/buildc.xml
@@ -13,7 +13,7 @@
     <li><link anchor="BuildMac">Building &XercesCName; on Macintosh.</link></li>
     <li><link anchor="BuildICU">Building ICU.</link></li>
     <li><link anchor="BuildCOM">Building COM module on Windows 98/NT/2000.</link></li>
-    <li><link anchor="BuildDocs">How to build the User Documentation?.</link></li>
+    <li><link anchor="BuildDocs">How to build the User Documentation?</link></li>
     <li><link anchor="PortingGuide">I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?</link></li>
     <li><link anchor="WCharT">What should I define XMLCh to be?</link></li>
     <li><link anchor="BuildUsingLibWWW">How can I generate Xerces-C binaries which includes the
@@ -582,8 +582,8 @@ files prior to your build.</p>
 
 <p><em>Troubleshooting:</em></p>
 <p>If you are using the parser and are failing to get any  message text
-for error codes, it may be because of the <code>*LIBL</code> resolution
-of the message file.</p>
+for error codes, it may be because of the <code>*LIBL</code> resolution of
+the message file.</p>
 </s3>
 
 <s3 title="Building Samples on AS/400">
diff --git a/doc/caveats.xml b/doc/caveats.xml
index f90d1f8fc0e511120a93005535311cdb009cd7cb..09dabd06fba65be3159920132b54c3ba34e9b175 100644
--- a/doc/caveats.xml
+++ b/doc/caveats.xml
@@ -8,6 +8,7 @@
 				line (this means that it cannot process its own
 				output). This is because the SAX API doesn't provide
 				a callback handler for the prologue.</li>
+			<li>&#913;&#955;&#966;&#945;&#946;&#951;&#964;&#953;&#954;&#972;&#962;</li>
 	    </ul>
 	</s2>
 </s1>
diff --git a/doc/faq-other.xml b/doc/faq-other.xml
index a7d7c96a2b6faac2fbbba97d153cdbd71e337da0..502150c6b2ce4832ef62c6e6575c91874c8e0e3b 100644
--- a/doc/faq-other.xml
+++ b/doc/faq-other.xml
@@ -15,8 +15,8 @@
     </faq>
 
 
-    <faq title="I found a defect - whom do I report it to?">
-        <q>I found a defect - whom do I report it to?</q>
+    <faq title="I found a defect - how do I report it?">
+        <q>I found a defect - how do I report it?</q>
         <a>
 
             <p>Send the defect reports to &lt;<jump
diff --git a/doc/memparse.xml b/doc/memparse.xml
index 65d2dcff6a5afcab185d8fb079e5302335e29d41..281e2198896e4e7bb5165c4e382d5632241b15de 100644
--- a/doc/memparse.xml
+++ b/doc/memparse.xml
@@ -20,7 +20,7 @@ cd MemParse
 gmake</source>
         <p>
         This will create the object files in the current directory and the executable named
-        MemParse in ' &XercesCInstallDir;-linux/bin' directory.</p>
+        <code>MemParse</code> in '&XercesCInstallDir;-linux/bin' directory.</p>
 
         <p>To delete all the generated object files and executables, type</p>
 <source>gmake clean</source>
diff --git a/doc/migration.xml b/doc/migration.xml
index ca54fc8e7775ef2a1e5cd2069acff087e21f27d1..9c89d72db57b531f13b729b8da943197e7ad2da2 100644
--- a/doc/migration.xml
+++ b/doc/migration.xml
@@ -179,7 +179,7 @@
 
         <p>The new samples are:</p>
         <ol>
-           <li>PParse - Demonstrates 'progressive parse', (see below)</li>
+           <li>PParse - Demonstrates 'progressive parse' (see below)</li>
            <li>StdInParse - Demonstrates use of the standard in input source</li>
            <li>EnumVal - Shows how to enumerate the markup decls in a DTD Validator</li>
         </ol>
@@ -341,8 +341,7 @@ while (gotMore &amp;&amp; !handler.getDone())
         this:</p>
 
 <source>SAXParser myParser;
-
-// Tell it whether to do namespacse
+// Tell it whether to do namespace
 myParser.setDoNamespaces(true);</source>
     </s2>
 
diff --git a/doc/pparse.xml b/doc/pparse.xml
index 9fd1c09864b3765872c6a427d9e3a9b354adc15b..275ce2b898cd71fa1a8394eabe7b438e527eed50 100644
--- a/doc/pparse.xml
+++ b/doc/pparse.xml
@@ -32,7 +32,7 @@ gmake</source>
 			and the executable named PParse in ' &XercesCInstallDir;-linux/bin'
 			directory.</p>
 
-	        <p>To delete all the generated object files and executables, type</p>
+	        <p>To delete all the generated object files and executables, type:</p>
 <source>gmake clean</source>
         </s3>
 
diff --git a/doc/program.xml b/doc/program.xml
index ee92baa9ec56b81448ef37d2a577674ca8b50ef2..57c7c53293b35c901c08e2a061d14433b837196a 100644
--- a/doc/program.xml
+++ b/doc/program.xml
@@ -305,7 +305,7 @@ docRootNode.AppendChild(aNode);</source>
         specific needs of the DOM API.</p>
 
       <p>The design derives from two primary sources: from the DOM's
-        CharacterData interface and from class java.lang.string</p>
+        CharacterData interface and from class <code>java.lang.string</code>.</p>
 
       <p>Main features are:</p>
 
diff --git a/doc/stdinparse.xml b/doc/stdinparse.xml
index 1f3972211d2282ea58c341baa5ba656196f991ee..c7bf87ef23213add0cdf73d0a7fdb82a7c081cb9 100644
--- a/doc/stdinparse.xml
+++ b/doc/stdinparse.xml
@@ -21,7 +21,7 @@ gmake</source>
 			and the executable named
 	        StdInParse in ' &XercesCInstallDir;-linux/bin' directory.</p>
 
-	        <p>To delete all the generated object files and executables, type</p>
+	        <p>To delete all the generated object files and executables, type:</p>
  <source>gmake clean</source>
         </s3>
 
@@ -30,7 +30,7 @@ gmake</source>
 		  count of the number of
           elements in the file. To run StdInParse, enter the following: </p>
 <source>StdInParse &lt; &lt;XML file&gt;</source>
-          <p>Here is a sample output from StdInParse</p>
+          <p>Here is a sample output from StdInParse:</p>
 <source>cd &XercesCInstallDir;-linux/samples/data
 StdInParse &lt; personal.xml
 personal.xml: 60 ms (37 elems, 12 attrs, 0 spaces, 268 chars)</source>
@@ -39,6 +39,4 @@ personal.xml: 60 ms (37 elems, 12 attrs, 0 spaces, 268 chars)</source>
           machine processor.</note>
         </s3>
     </s2>
-
-
 </s1>