File tidies for 10.35-RC1 release candidate.

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

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/html/pcre2pattern.html b/doc/html/pcre2pattern.html
index 4160295..ec2e8c9 100644
--- a/doc/html/pcre2pattern.html
+++ b/doc/html/pcre2pattern.html
@@ -114,7 +114,7 @@ Another special sequence that may appear at the start of a pattern is (*UCP).
 This has the same effect as setting the PCRE2_UCP option: it causes sequences
 such as \d and \w to use Unicode properties to determine character types,
 instead of recognizing only characters with codes less than 256 via a lookup
-table. If also causes upper/lower casing operations to use Unicode properties 
+table. If also causes upper/lower casing operations to use Unicode properties
 for characters with code points greater than 127, even when UTF is not set.
 </P>
 <P>
@@ -2664,8 +2664,8 @@ as before because nothing has changed, so using a non-atomic assertion just
 wastes resources.
 </P>
 <P>
-There is one exception to backtracking into a non-atomic assertion. If an 
-(*ACCEPT) control verb is triggered, the assertion succeeds atomically. That 
+There is one exception to backtracking into a non-atomic assertion. If an
+(*ACCEPT) control verb is triggered, the assertion succeeds atomically. That
 is, a subsequent match failure cannot backtrack into the assertion.
 </P>
 <P>