Typos in documentation and comments noted by Jason Hood.

git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@936 6239d852-aaf2-0410-a92c-79f79f948069

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/html/pcre2build.html b/doc/html/pcre2build.html
index c9d9324..3ce64f6 100644
--- a/doc/html/pcre2build.html
+++ b/doc/html/pcre2build.html
@@ -227,7 +227,7 @@ separator, U+2028), and PS (paragraph separator, U+2029). The final option is
 <pre>
   --enable-newline-is-nul
 </pre>
-which causes NUL (binary zero) is set as the default line-ending character.
+which causes NUL (binary zero) to be set as the default line-ending character.
 </P>
 <P>
 Whatever default line ending convention is selected when PCRE2 is built can be
@@ -286,15 +286,15 @@ The <b>pcre2_match()</b> function starts out using a 20K vector on the system
 stack to record backtracking points. The more nested backtracking points there
 are (that is, the deeper the search tree), the more memory is needed. If the
 initial vector is not large enough, heap memory is used, up to a certain limit,
-which is specified in kilobytes. The limit can be changed at run time, as
-described in the
+which is specified in kibibytes (units of 1024 bytes). The limit can be changed
+at run time, as described in the
 <a href="pcre2api.html"><b>pcre2api</b></a>
 documentation. The default limit (in effect unlimited) is 20 million. You can
 change this by a setting such as
 <pre>
   --with-heap-limit=500
 </pre>
-which limits the amount of heap to 500 kilobytes. This limit applies only to
+which limits the amount of heap to 500 KiB. This limit applies only to
 interpretive matching in <b>pcre2_match()</b> and <b>pcre2_dfa_match()</b>, which
 may also use the heap for internal workspace when processing complicated
 patterns. This limit does not apply when JIT (which has its own memory
@@ -542,7 +542,7 @@ generated from the string.
 Setting --enable-fuzz-support also causes a binary called <b>pcre2fuzzcheck</b>
 to be created. This is normally run under valgrind or used when PCRE2 is
 compiled with address sanitizing enabled. It calls the fuzzing function and
-outputs information about it is doing. The input strings are specified by
+outputs information about what it is doing. The input strings are specified by
 arguments: if an argument starts with "=" the rest of it is a literal input
 string. Otherwise, it is assumed to be a file name, and the contents of the
 file are the test string.