Applied a spelling patch from Geert Kloosterman to xml.html, and regenerated
the web site, Daniel
diff --git a/doc/FAQ.html b/doc/FAQ.html
index d31c725..d8bb868 100644
--- a/doc/FAQ.html
+++ b/doc/FAQ.html
@@ -88,24 +88,24 @@
<td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd">
<p>Table of Content:</p>
<ul>
-<li><a href="FAQ.html#Licence">Licence(s)</a></li>
+<li><a href="FAQ.html#License">License(s)</a></li>
<li><a href="FAQ.html#Installati">Installation</a></li>
<li><a href="FAQ.html#Compilatio">Compilation</a></li>
<li><a href="FAQ.html#Developer">Developer corner</a></li>
</ul>
<h3>
-<a name="Licence">Licence</a>(s)</h3>
+<a name="License">License</a>(s)</h3>
<ol>
<li>
<em>Licensing Terms for libxml</em>
<p>libxml is released under the <a href="http://www.opensource.org/licenses/mit-license.html">MIT
- Licence</a>, see the file Copyright in the distribution for the precise
+ License</a>, see the file Copyright in the distribution for the precise
wording</p>
</li>
<li>
<em>Can I embed libxml in a proprietary application ?</em>
- <p>Yes. The MIT Licence allows you to also keep proprietary the changes
- you made to libxml, but it would be graceful to provide back bugfixes and
+ <p>Yes. The MIT License allows you to also keep proprietary the changes
+ you made to libxml, but it would be graceful to provide back bug fixes and
improvements as patches for possible incorporation in the main
development tree</p>
</li>
@@ -119,7 +119,7 @@
<em>Where can I get libxml</em> ?
<p>The original distribution comes from <a href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or <a href="ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/">gnome.org</a>
</p>
-<p>Most linux and Bsd distribution includes libxml, this is probably the
+<p>Most Linux and BSD distributions include libxml, this is probably the
safer way for end-users</p>
<p>David Doolin provides precompiled Windows versions at <a href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/%20%20%20%20%20%20%20%20%20">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a>
</p>
@@ -150,8 +150,8 @@
</li>
<li>
<em>I can't install the libxml(2) RPM package due to failed
- dependancies</em>
- <p>The most generic solution is to refetch the latest src.rpm , and
+ dependencies</em>
+ <p>The most generic solution is to re-fetch the latest src.rpm , and
rebuild it locally with</p>
<p><code>rpm --rebuild libxml(2)-xxx.src.rpm</code></p>
<p>if everything goes well it will generate two binary rpm (one providing
@@ -188,7 +188,7 @@
highly portable and available widely compression library</li>
<li>iconv: a powerful character encoding conversion library. It's
included by default on recent glibc libraries, so it doesn't need to
- be installed specifically on linux. It seems it's now <a href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
+ be installed specifically on Linux. It seems it's now <a href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
of the official UNIX</a> specification. Here is one <a href="http://clisp.cons.org/~haible/packages-libiconv.html">implementation
of the library</a> which source can be found <a href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
</ul>
@@ -248,7 +248,7 @@
<p><em>I want to the get the content of the first node (node with the
CommFlag="0")</em></p>
<p><em>so I did it as following;</em></p>
-<pre>xmlNodePtr pode;
+<pre>xmlNodePtr pnode;
pnode=pxmlDoc->children->children;</pre>
<p><em>but it does not work. If I change it to</em></p>
<pre>pnode=pxmlDoc->children->children->next;</pre>
@@ -257,7 +257,7 @@
<p>In XML all characters in the content of the document are significant
<strong>including blanks and formatting line breaks</strong>.</p>
<p>The extra nodes you are wondering about are just that, text nodes with
- the formatting spaces wich are part of the document but that people tend
+ the formatting spaces which are part of the document but that people tend
to forget. There is a function <a href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
()</a> to remove those at parse time, but that's an heuristic, and its
use should be limited to case where you are sure there is no
@@ -300,7 +300,7 @@
generated doc</a>
</li>
<li>looks for examples of use for libxml function using the Gnome code
- for example the following will query the full Gnome CVs base for the
+ for example the following will query the full Gnome CVS base for the
use of the <strong>xmlAddChild()</strong> function:
<p><a href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
<p>This may be slow, a large hardware donation to the gnome project
@@ -318,7 +318,7 @@
<p>libxml is written in pure C in order to allow easy reuse on a number
of platforms, including embedded systems. I don't intend to convert to
C++.</p>
-<p>There is however a few C++ wrappers which may fullfill your needs:</p>
+<p>There is however a few C++ wrappers which may fulfill your needs:</p>
<ul>
<li>by Ari Johnson <ari@btigate.com>:
<p>Website: <a href="http://lusis.org/~ari/xml%2B%2B/">http://lusis.org/~ari/xml++/</a>
@@ -336,7 +336,7 @@
<p>It is possible to validate documents which had not been validated at
initial parsing time or documents who have been built from scratch using
the API. Use the <a href="http://xmlsoft.org/html/libxml-valid.html#XMLVALIDATEDTD">xmlValidateDtd()</a>
- function. It is also possible to simply add a Dtd to an existing
+ function. It is also possible to simply add a DTD to an existing
document:</p>
<pre>xmlDocPtr doc; /* your existing document */
xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */