Code tidies for 10.30-RC1 release candidate.

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

1 files changed, 13 insertions, 8 deletions

diff --git a/doc/pcre2build.3 b/doc/pcre2build.3
index 8b081d9..7586d22 100644
--- a/doc/pcre2build.3
+++ b/doc/pcre2build.3
@@ -1,4 +1,4 @@
-.TH PCRE2BUILD 3 "17 June 2017" "PCRE2 10.30"
+.TH PCRE2BUILD 3 "18 July 2017" "PCRE2 10.30"
 .SH NAME
 PCRE2 - Perl-compatible regular expressions (revised API)
 .
@@ -66,10 +66,10 @@ Options that specify values have names that start with --with.
 .rs
 .sp
 By default, a library called \fBlibpcre2-8\fP is built, containing functions
-that take string arguments contained in vectors of bytes, interpreted either as
+that take string arguments contained in arrays of bytes, interpreted either as
 single-byte characters, or UTF-8 strings. You can also build two other
 libraries, called \fBlibpcre2-16\fP and \fBlibpcre2-32\fP, which process
-strings that are contained in vectors of 16-bit and 32-bit code units,
+strings that are contained in arrays of 16-bit and 32-bit code units,
 respectively. These can be interpreted either as single-unit characters or
 UTF-16/UTF-32 strings. To build these additional libraries, add one or both of
 the following to the \fBconfigure\fP command:
@@ -197,18 +197,22 @@ to the \fBconfigure\fP command. There is a fourth option, specified by
   --enable-newline-is-anycrlf
 .sp
 which causes PCRE2 to recognize any of the three sequences CR, LF, or CRLF as
-indicating a line ending. Finally, a fifth option, specified by
+indicating a line ending. A fifth option, specified by
 .sp
   --enable-newline-is-any
 .sp
 causes PCRE2 to recognize any Unicode newline sequence. The Unicode newline
 sequences are the three just mentioned, plus the single characters VT (vertical
 tab, U+000B), FF (form feed, U+000C), NEL (next line, U+0085), LS (line
-separator, U+2028), and PS (paragraph separator, U+2029).
+separator, U+2028), and PS (paragraph separator, U+2029). The final option is
+.sp
+  --enable-newline-is-nul
+.sp
+which causes NUL (binary zero) is set as the default line-ending character.
 .P
 Whatever default line ending convention is selected when PCRE2 is built can be
 overridden by applications that use the library. At build time it is
-conventional to use the standard for your operating system.
+recommended to use the standard for your operating system.
 .
 .
 .SH "WHAT \eR MATCHES"
@@ -297,7 +301,8 @@ because the size of each backtracking "frame" depends on the number of
 capturing parentheses in a pattern, the amount of heap that is used before the
 limit is reached varies from pattern to pattern. This limit was more useful in
 versions before 10.30, where function recursion was used for backtracking.
-However, as well as applying to \fBpcre2_match()\fP, this limit also controls
+.P
+As well as applying to \fBpcre2_match()\fP, the depth limit also controls
 the depth of recursive function calls in \fBpcre2_dfa_match()\fP. These are
 used for lookaround assertions, atomic groups, and recursion within patterns.
 The limit does not apply to JIT matching.
@@ -577,6 +582,6 @@ Cambridge, England.
 .rs
 .sp
 .nf
-Last updated: 17 June 2017
+Last updated: 18 July 2017
 Copyright (c) 1997-2017 University of Cambridge.
 .fi