Tidies of documenation and code while preparing for release.

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

1 files changed, 10 insertions, 10 deletions

diff --git a/doc/pcretest.1 b/doc/pcretest.1
index 6c37d3d..c5d4fd6 100644
--- a/doc/pcretest.1
+++ b/doc/pcretest.1
@@ -179,7 +179,7 @@ options that do not correspond to anything in Perl:
   \fB/U\fP              PCRE_UNGREEDY
   \fB/W\fP              PCRE_UCP
   \fB/X\fP              PCRE_EXTRA
-  \fB/Y\fP              PCRE_NO_START_OPTIMIZE 
+  \fB/Y\fP              PCRE_NO_START_OPTIMIZE
   \fB/<JS>\fP           PCRE_JAVASCRIPT_COMPAT
   \fB/<cr>\fP           PCRE_NEWLINE_CR
   \fB/<lf>\fP           PCRE_NEWLINE_LF
@@ -222,9 +222,9 @@ empty string, the next call is done with the PCRE_NOTEMPTY_ATSTART and
 PCRE_ANCHORED flags set in order to search for another, non-empty, match at the
 same point. If this second match fails, the start offset is advanced, and the
 normal match is retried. This imitates the way Perl handles such cases when
-using the \fB/g\fP modifier or the \fBsplit()\fP function. Normally, the start 
-offset is advanced by one character, but if the newline convention recognizes 
-CRLF as a newline, and the current character is CR followed by LF, an advance 
+using the \fB/g\fP modifier or the \fBsplit()\fP function. Normally, the start
+offset is advanced by one character, but if the newline convention recognizes
+CRLF as a newline, and the current character is CR followed by LF, an advance
 of two is used.
 .
 .
@@ -345,7 +345,7 @@ recognized:
   \et         tab (\ex09)
   \ev         vertical tab (\ex0b)
   \ennn       octal character (up to 3 octal digits)
-               always a byte unless > 255 in UTF-8 mode 
+               always a byte unless > 255 in UTF-8 mode
   \exhh       hexadecimal byte (up to 2 hex digits)
 .\" JOIN
   \ex{hh...}  hexadecimal character, any number of digits
@@ -418,7 +418,7 @@ recognized:
                \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
 .\" JOIN
   \e>dd       start the match at offset dd (optional "-"; then
-               any number of digits); this sets the \fIstartoffset\fP 
+               any number of digits); this sets the \fIstartoffset\fP
                argument for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP
 .\" JOIN
   \e<cr>      pass the PCRE_NEWLINE_CR option to \fBpcre_exec()\fP
@@ -436,11 +436,11 @@ recognized:
   \e<any>     pass the PCRE_NEWLINE_ANY option to \fBpcre_exec()\fP
                or \fBpcre_dfa_exec()\fP
 .sp
-Note that \exhh always specifies one byte, even in UTF-8 mode; this makes it 
-possible to construct invalid UTF-8 sequences for testing purposes. On the 
+Note that \exhh always specifies one byte, even in UTF-8 mode; this makes it
+possible to construct invalid UTF-8 sequences for testing purposes. On the
 other hand, \ex{hh} is interpreted as a UTF-8 character in UTF-8 mode,
-generating more than one byte if the value is greater than 127. When not in 
-UTF-8 mode, it generates one byte for values less than 256, and causes an error 
+generating more than one byte if the value is greater than 127. When not in
+UTF-8 mode, it generates one byte for values less than 256, and causes an error
 for greater values.
 .P
 The escapes that specify line ending sequences are literal strings, exactly as