[Pcre-svn] [1756] code/trunk/doc: Fix minor documentation ty…

Top Page
Delete this message
Author: Subversion repository
Date:  
To: pcre-svn
Subject: [Pcre-svn] [1756] code/trunk/doc: Fix minor documentation typos.
Revision: 1756
          http://vcs.pcre.org/viewvc?view=rev&revision=1756
Author:   ph10
Date:     2019-07-22 12:12:47 +0100 (Mon, 22 Jul 2019)
Log Message:
-----------
Fix minor documentation typos.


Modified Paths:
--------------
    code/trunk/doc/pcre.3
    code/trunk/doc/pcreapi.3


Modified: code/trunk/doc/pcre.3
===================================================================
--- code/trunk/doc/pcre.3    2019-07-18 06:13:14 UTC (rev 1755)
+++ code/trunk/doc/pcre.3    2019-07-22 11:12:47 UTC (rev 1756)
@@ -146,7 +146,7 @@
 One way of guarding against this possibility is to use the
 \fBpcre_fullinfo()\fP function to check the compiled pattern's options for UTF.
 Alternatively, from release 8.33, you can set the PCRE_NEVER_UTF option at
-compile time. This causes an compile time error if a pattern contains a
+compile time. This causes a compile time error if a pattern contains a
 UTF-setting sequence.
 .P
 If your application is one that supports UTF, be aware that validity checking


Modified: code/trunk/doc/pcreapi.3
===================================================================
--- code/trunk/doc/pcreapi.3    2019-07-18 06:13:14 UTC (rev 1755)
+++ code/trunk/doc/pcreapi.3    2019-07-22 11:12:47 UTC (rev 1756)
@@ -1227,7 +1227,7 @@
   PCRE_ERROR_BADOPTION      the value of \fIwhat\fP was invalid
   PCRE_ERROR_UNSET          the requested field is not set
 .sp
-The "magic number" is placed at the start of each compiled pattern as an simple
+The "magic number" is placed at the start of each compiled pattern as a simple
 check against passing an arbitrary memory pointer. The endianness error can
 occur if a compiled pattern is saved and reloaded on a different host. Here is
 a typical call of \fBpcre_fullinfo()\fP, to obtain the length of the compiled
@@ -1294,7 +1294,7 @@
 .sp
 Return the value of the first data unit (non-UTF character) of any matched
 string in the situation where PCRE_INFO_FIRSTCHARACTERFLAGS returns 1;
-otherwise return 0. The fourth argument should point to an \fBuint_t\fP
+otherwise return 0. The fourth argument should point to a \fBuint_t\fP
 variable.
 .P
 In the 8-bit library, the value is always less than 256. In the 16-bit library
@@ -1560,7 +1560,7 @@
 .sp
 Return the value of the rightmost literal data unit that must exist in any
 matched string, other than at its start, if such a value has been recorded. The
-fourth argument should point to an \fBuint32_t\fP variable. If there is no such
+fourth argument should point to a \fBuint32_t\fP variable. If there is no such
 value, 0 is returned.
 .
 .