Doc file tidies for 10.38-RC1

Author: PhilipHazel

README

@@ -12,7 +12,7 @@ repository:
 https://github.com/PhilipHazel/pcre2/releases
 
 There is a mailing list for discussion about the development of PCRE2 at
-[email protected]. You can subscribe by sending an email to 
+[email protected]. You can subscribe by sending an email to
 [email protected].
 
 You can access the archives and also subscribe or manage your subscription

doc/html/README.txt

@@ -12,7 +12,7 @@ repository:
 https://github.com/PhilipHazel/pcre2/releases
 
 There is a mailing list for discussion about the development of PCRE2 at
-[email protected]. You can subscribe by sending an email to 
+[email protected]. You can subscribe by sending an email to
 [email protected].
 
 You can access the archives and also subscribe or manage your subscription

doc/html/pcre2.html

@@ -28,7 +28,7 @@ <h1>pcre2 man page</h1>
 increasingly difficult. The new API is more extensible, and it was simplified
 by abolishing the separate "study" optimizing function; in PCRE2, patterns are
 automatically optimized where possible. Since forking from PCRE1, the code has
-been extensively refactored and new features introduced. The old library is now 
+been extensively refactored and new features introduced. The old library is now
 obsolete and is no longer maintained.
 </P>
 <P>

doc/html/pcre2_dfa_match.html

@@ -45,10 +45,10 @@ <h1>pcre2_dfa_match man page</h1>
   <i>workspace</i>    Points to a vector of ints used as working space
   <i>wscount</i>      Number of elements in the vector
 </pre>
-The size of output vector needed to contain all the results depends on the  
-number of simultaneous matches, not on the number of parentheses in the        
-pattern. Using <b>pcre2_match_data_create_from_pattern()</b> to create the match 
-data block is therefore not advisable when using this function.   
+The size of output vector needed to contain all the results depends on the
+number of simultaneous matches, not on the number of parentheses in the
+pattern. Using <b>pcre2_match_data_create_from_pattern()</b> to create the match
+data block is therefore not advisable when using this function.
 </P>
 <P>
 A match context is needed only if you want to set up a callout function or

doc/html/pcre2api.html

@@ -1917,10 +1917,10 @@ <h1>pcre2api man page</h1>
 <pre>
   PCRE2_EXTRA_ALLOW_LOOKAROUND_BSK
 </pre>
-Since release 10.38 PCRE2 has forbidden the use of \K within lookaround 
-assertions, following Perl's lead. This option is provided to re-enable the 
-previous behaviour (act in positive lookarounds, ignore in negative ones) in 
-case anybody is relying on it.   
+Since release 10.38 PCRE2 has forbidden the use of \K within lookaround
+assertions, following Perl's lead. This option is provided to re-enable the
+previous behaviour (act in positive lookarounds, ignore in negative ones) in
+case anybody is relying on it.
 <pre>
   PCRE2_EXTRA_ALLOW_SURROGATE_ESCAPES
 </pre>
@@ -2526,7 +2526,7 @@ <h1>pcre2api man page</h1>
 Before calling <b>pcre2_match()</b>, <b>pcre2_dfa_match()</b>, or
 <b>pcre2_jit_match()</b> you must create a match data block by calling one of
 the creation functions above. For <b>pcre2_match_data_create()</b>, the first
-argument is the number of pairs of offsets in the <i>ovector</i>. 
+argument is the number of pairs of offsets in the <i>ovector</i>.
 </P>
 <P>
 When using <b>pcre2_match()</b>, one pair of offsets is required to identify the
@@ -2535,14 +2535,14 @@ <h1>pcre2api man page</h1>
 the matched portion of the subject plus three captured substrings.
 </P>
 <P>
-When using <b>pcre2_dfa_match()</b> there may be multiple matched substrings of 
+When using <b>pcre2_dfa_match()</b> there may be multiple matched substrings of
 different lengths at the same point in the subject. The ovector should be made
 large enough to hold as many as are expected.
 </P>
 <P>
 A minimum of at least 1 pair is imposed by <b>pcre2_match_data_create()</b>, so
-it is always possible to return the overall matched string in the case of 
-<b>pcre2_match()</b> or the longest match in the case of 
+it is always possible to return the overall matched string in the case of
+<b>pcre2_match()</b> or the longest match in the case of
 <b>pcre2_dfa_match()</b>.
 </P>
 <P>

doc/html/pcre2demo.html

@@ -234,11 +234,11 @@ <h1>pcre2demo man page</h1>
 if (rc == 0)
   printf("ovector was not big enough for all the captured substrings\n");
 
-/* Since release 10.38 PCRE2 has locked out the use of \K in lookaround 
-assertions. However, there is an option to re-enable the old behaviour. If that 
+/* Since release 10.38 PCRE2 has locked out the use of \K in lookaround
+assertions. However, there is an option to re-enable the old behaviour. If that
 is set, it is possible to run patterns such as /(?=.\K)/ that use \K in an
 assertion to set the start of a match later than its end. In this demonstration
-program, we show how to detect this case, but it shouldn't arise because the 
+program, we show how to detect this case, but it shouldn't arise because the
 option is never set. */
 
 if (ovector[0] &gt; ovector[1])

doc/html/pcre2pattern.html

@@ -1175,10 +1175,10 @@ <h1>pcre2pattern man page</h1>
 matches "foobar", the first substring is still set to "foo".
 </P>
 <P>
-From version 5.32.0 Perl forbids the use of \K in lookaround assertions. From 
-release 10.38 PCRE2 also forbids this by default. However, the 
-PCRE2_EXTRA_ALLOW_LOOKAROUND_BSK option can be used when calling 
-<b>pcre2_compile()</b> to re-enable the previous behaviour. When this option is 
+From version 5.32.0 Perl forbids the use of \K in lookaround assertions. From
+release 10.38 PCRE2 also forbids this by default. However, the
+PCRE2_EXTRA_ALLOW_LOOKAROUND_BSK option can be used when calling
+<b>pcre2_compile()</b> to re-enable the previous behaviour. When this option is
 set, \K is acted upon when it occurs inside positive assertions, but is
 ignored in negative assertions. Note that when a pattern such as (?=ab\K)
 matches, the reported start of the match can be greater than the end of the

doc/html/pcre2syntax.html

@@ -429,7 +429,7 @@ <h1>pcre2syntax man page</h1>
 <pre>
   \K          set reported start of match
 </pre>
-From release 10.38 \K is not permitted by default in lookaround assertions, 
+From release 10.38 \K is not permitted by default in lookaround assertions,
 for compatibility with Perl. However, if the PCRE2_EXTRA_ALLOW_LOOKAROUND_BSK
 option is set, the previous behaviour is re-enabled. When this option is set,
 \K is honoured in positive assertions, but ignored in negative ones.

doc/html/pcre2test.html

@@ -84,7 +84,7 @@ <h1>pcre2test man page</h1>
 <br><a name="SEC3" href="#TOC1">INPUT ENCODING</a><br>
 <P>
 Input to <b>pcre2test</b> is processed line by line, either by calling the C
-library's <b>fgets()</b> function, or via the <b>libreadline</b> or <b>libedit</b> 
+library's <b>fgets()</b> function, or via the <b>libreadline</b> or <b>libedit</b>
 library. In some Windows environments character 26 (hex 1A) causes an immediate
 end of file, and no further data is read, so this character should be avoided
 unless you really want that action.
@@ -610,7 +610,7 @@ <h1>pcre2test man page</h1>
 for a description of the effects of these options.
 <pre>
       allow_empty_class         set PCRE2_ALLOW_EMPTY_CLASS
-      allow_lookaround_bsk      set PCRE2_EXTRA_ALLOW_LOOKAROUND_BSK 
+      allow_lookaround_bsk      set PCRE2_EXTRA_ALLOW_LOOKAROUND_BSK
       allow_surrogate_escapes   set PCRE2_EXTRA_ALLOW_SURROGATE_ESCAPES
       alt_bsux                  set PCRE2_ALT_BSUX
       alt_circumflex            set PCRE2_ALT_CIRCUMFLEX

doc/pcre2.3

@@ -11,7 +11,7 @@ nearly two decades, the limitations of the original API were making development
 increasingly difficult. The new API is more extensible, and it was simplified
 by abolishing the separate "study" optimizing function; in PCRE2, patterns are
 automatically optimized where possible. Since forking from PCRE1, the code has
-been extensively refactored and new features introduced. The old library is now 
+been extensively refactored and new features introduced. The old library is now
 obsolete and is no longer maintained.
 .P
 As well as Perl-style regular expression patterns, some features that appeared