commit 95c09d9abdaeffa10f0c8327f994fdfe2b13d0a3
author Daniel Veillard <veillard@src.gnome.org> Mon Jul 07 12:11:06 2003 +0000
committer Daniel Veillard <veillard@src.gnome.org> Mon Jul 07 12:11:06 2003 +0000
tree 78dcf8d4735fbaed44815cb92deaf6d681e40948
parent 560c2a441bf27f5b9d55252a70f3d5952d9ae351

Update of docs, Daniel

doc/catalog.html

diff --git a/doc/catalog.html b/doc/catalog.html
index b3ed4a2..6dd5212 100644
--- a/doc/catalog.html
+++ b/doc/catalog.html
@@ -191,8 +191,8 @@
 automatically generated <a href="html/libxml-catalog.html">API page for
 catalog support</a>.</p><p>The header for the catalog interfaces should be included as:</p><pre>#include &lt;libxml/catalog.h&gt;</pre><p>The API is voluntarily kept very simple. First it is not obvious that
 applications really need access to it since it is the default behaviour of
-libxml2 (Note: it is possible to completely override libxml2 default catalog by
-using <a href="html/libxml-parser.html">xmlSetExternalEntityLoader</a> to
+libxml2 (Note: it is possible to completely override libxml2 default catalog
+by using <a href="html/libxml-parser.html">xmlSetExternalEntityLoader</a> to
 plug an application specific resolver).</p><p>Basically libxml2 support 2 catalog lists:</p><ul><li>the default one, global shared by all the application</li>
   <li>a per-document catalog, this one is built if the document uses the
     <code>oasis-xml-catalog</code> PIs to specify its own catalog list, it is