From f375cc9c98083618c9b865ece092aa1f028918d8 Mon Sep 17 00:00:00 2001
From: Karl Waclawek <kwaclaw@users.sourceforge.net>
Date: Thu, 28 Aug 2003 13:08:10 +0000
Subject: [PATCH] Fixed omission of second argument in XML_ParserReset.
 Reported by Tim Bray.

---
 expat/doc/reference.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/expat/doc/reference.html b/expat/doc/reference.html
index 4156ce1b..01b07e7a 100644
--- a/expat/doc/reference.html
+++ b/expat/doc/reference.html
@@ -692,7 +692,7 @@ freeing any memory associated with <a href="#userdata">user data</a>.
 
 <pre class="fcndec" id="XML_ParserReset">
 XML_Bool
-XML_ParserReset(XML_Parser p);
+XML_ParserReset(XML_Parser p, const XML_Char *encoding);
 </pre>
 <div class="fcndef">
 Clean up the memory structures maintained by the parser so that it may
@@ -708,9 +708,9 @@ dealing with any memory associated with <a href="#userdata">user data</a>.
 <h3><a name="parsing">Parsing</a></h3>
 
 <p>To state the obvious: the three parsing functions <code><a href=
-"#XML_Parse" >XML_Parse</a></code>, <code><a href= "#XML_ParseBuffer"
->XML_ParseBuffer</a></code> and <code><a href= "#XML_GetBuffer"
->>XML_GetBuffer</a></code> must not be
+"#XML_Parse" >XML_Parse</a></code>, <code><a href= "#XML_ParseBuffer">
+XML_ParseBuffer</a></code> and <code><a href= "#XML_GetBuffer">
+XML_GetBuffer</a></code> must not be
 called from within a handler unless they operate on a separate parser
 instance, that is, one that did not call the handler. For example, it
 is OK to call the parsing functions from within an
-- 
2.40.0