Final source file tidies for 8.33 release.

git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1335 2f5784b3-3f2a-0410-8824-cb99058d5e15

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/html/pcrepartial.html b/doc/html/pcrepartial.html
index 1ae06bb..98d34f0 100644
--- a/doc/html/pcrepartial.html
+++ b/doc/html/pcrepartial.html
@@ -95,8 +95,8 @@ of the subject.
 If there are at least two slots in the offsets vector when a partial match is
 returned, the first slot is set to the offset of the earliest character that
 was inspected. For convenience, the second offset points to the end of the
-subject so that a substring can easily be identified. If there are at least 
-three slots in the offsets vector, the third slot is set to the offset of the 
+subject so that a substring can easily be identified. If there are at least
+three slots in the offsets vector, the third slot is set to the offset of the
 character where matching started.
 </P>
 <P>
@@ -110,7 +110,7 @@ inspected while carrying out the match. For example, consider this pattern:
 This pattern matches "123", but only if it is preceded by "abc". If the subject
 string is "xyzabc12", the first two offsets after a partial match are for the
 substring "abc12", because all these characters were inspected. However, the
-third offset is set to 6, because that is the offset where matching began. 
+third offset is set to 6, because that is the offset where matching began.
 </P>
 <P>
 What happens when a partial match is identified depends on which of the two
@@ -337,8 +337,8 @@ processing time is needed.
 <P>
 <b>Note:</b> If the pattern contains lookbehind assertions, or \K, or starts
 with \b or \B, the string that is returned for a partial match includes
-characters that precede the start of what would be returned for a complete 
-match, because it contains all the characters that were inspected during the 
+characters that precede the start of what would be returned for a complete
+match, because it contains all the characters that were inspected during the
 partial match.
 </P>
 <br><a name="SEC9" href="#TOC1">ISSUES WITH MULTI-SEGMENT MATCHING</a><br>
@@ -369,8 +369,8 @@ characters should be retained.)
 From release 8.33, there is a more accurate way of deciding which characters to
 retain. Instead of subtracting the length of the longest lookbehind from the
 earliest inspected character (<i>offsets[0]</i>), the match start position
-(<i>offsets[2]</i>) should be used, and the next match attempt started at the 
-<i>offsets[2]</i> character by setting the <i>startoffset</i> argument of 
+(<i>offsets[2]</i>) should be used, and the next match attempt started at the
+<i>offsets[2]</i> character by setting the <i>startoffset</i> argument of
 <b>pcre_exec()</b> or <b>pcre_dfa_exec()</b>.
 </P>
 <P>
@@ -380,7 +380,7 @@ and 5. This indicates that the matching process that gave a partial match
 started at offset 5, but the characters "123a" were all inspected. The maximum
 lookbehind for that pattern is 3, so taking that away from 5 shows that we need
 only keep "123a", and the next match attempt can be started at offset 3 (that
-is, at "a") when further characters have been added. When the match start is 
+is, at "a") when further characters have been added. When the match start is
 not the earliest inspected character, <b>pcretest</b> shows it explicitly:
 <pre>
     re&#62; "(?&#60;=123)abc"