Fix two typos in pcre2api, plus some other minor issues (#703)

Author: NWilson

doc/html/pcre2.html

@@ -34,15 +34,15 @@ <h1>pcre2 man page</h1>
 <p>
 As well as Perl-style regular expression patterns, some features that appeared
 in Python and the original PCRE before they appeared in Perl are available
-using the Python syntax. There is also some support for one or two .NET and
-Oniguruma syntax items, and there are options for requesting some minor changes
-that give better ECMAScript (aka JavaScript) compatibility.
+using the Python syntax. There is also some support for some .NET and Oniguruma
+syntax items, and there are options for requesting some minor changes that give
+better ECMAScript (JavaScript) compatibility.
 </p>
 <p>
 The source code for PCRE2 can be compiled to support strings of 8-bit, 16-bit,
 or 32-bit code units, which means that up to three separate libraries may be
-installed, one for each code unit size. The size of code unit is not related to
-the bit size of the underlying hardware. In a 64-bit environment that also
+installed, one for each code unit size. The size of a code unit is not related
+to the bit size of the underlying hardware. In a 64-bit environment that also
 supports 32-bit applications, versions of PCRE2 that are compiled in both
 64-bit and 32-bit modes may be needed.
 </p>

doc/html/pcre2api.html

@@ -279,7 +279,7 @@ <h1>pcre2api man page</h1>
 <b>int pcre2_substitute(const pcre2_code *<i>code</i>, PCRE2_SPTR <i>subject</i>,</b>
 <b>  PCRE2_SIZE <i>length</i>, PCRE2_SIZE <i>startoffset</i>,</b>
 <b>  uint32_t <i>options</i>, pcre2_match_data *<i>match_data</i>,</b>
-<b>  pcre2_match_context *<i>mcontext</i>, PCRE2_SPTR <i>replacementz</i>,</b>
+<b>  pcre2_match_context *<i>mcontext</i>, PCRE2_SPTR <i>replacement</i>,</b>
 <b>  PCRE2_SIZE <i>rlength</i>, PCRE2_UCHAR *<i>outputbuffer</i>,</b>
 <b>  PCRE2_SIZE *<i>outlengthptr</i>);</b>
 </p>
@@ -3017,7 +3017,7 @@ <h1>pcre2api man page</h1>
 </pre>
 The PCRE2_ANCHORED option limits <b>pcre2_match()</b> to matching at the first
 matching position. If a pattern was compiled with PCRE2_ANCHORED, or turned out
-to be anchored by virtue of its contents, it cannot be made unachored at
+to be anchored by virtue of its contents, it cannot be made unanchored at
 matching time. Note that setting the option at match time disables JIT
 matching.
 <pre>

doc/html/pcre2build.html

@@ -44,9 +44,9 @@ <h1>pcre2build man page</h1>
 <br><a name="SEC1" href="#TOC1">BUILDING PCRE2</a><br>
 <p>
 PCRE2 is distributed with a <b>configure</b> script that can be used to build
-the library in Unix-like environments using the applications known as
-Autotools. Also in the distribution are files to support building using
-<b>CMake</b> instead of <b>configure</b>. The text file
+the library in Unix-like environments using the Autotools applications. Also in
+the distribution are files to support building using <b>CMake</b> instead of
+<b>configure</b>. The text file
 <a href="README.txt"><b>README</b></a>
 contains general information about building with Autotools (some of which is
 repeated below), and also has some comments about building on various operating

doc/pcre2.3

@@ -16,14 +16,14 @@ obsolete and is no longer maintained.
 .P
 As well as Perl-style regular expression patterns, some features that appeared
 in Python and the original PCRE before they appeared in Perl are available
-using the Python syntax. There is also some support for one or two .NET and
-Oniguruma syntax items, and there are options for requesting some minor changes
-that give better ECMAScript (aka JavaScript) compatibility.
+using the Python syntax. There is also some support for some .NET and Oniguruma
+syntax items, and there are options for requesting some minor changes that give
+better ECMAScript (JavaScript) compatibility.
 .P
 The source code for PCRE2 can be compiled to support strings of 8-bit, 16-bit,
 or 32-bit code units, which means that up to three separate libraries may be
-installed, one for each code unit size. The size of code unit is not related to
-the bit size of the underlying hardware. In a 64-bit environment that also
+installed, one for each code unit size. The size of a code unit is not related
+to the bit size of the underlying hardware. In a 64-bit environment that also
 supports 32-bit applications, versions of PCRE2 that are compiled in both
 64-bit and 32-bit modes may be needed.
 .P