Skip to content

Wording fix for the manual page #377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 31, 2024
Merged

Wording fix for the manual page #377

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/pcre2api.3
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -344,10 +344,10 @@ There are also three different sets of data types:
\fBPCRE2_UCHAR8, PCRE2_UCHAR16, PCRE2_UCHAR32\fP
\fBPCRE2_SPTR8, PCRE2_SPTR16, PCRE2_SPTR32\fP
.sp
The UCHAR types define unsigned code units of the appropriate widths. For
example, PCRE2_UCHAR16 is usually defined as `uint16_t'. The SPTR types are
constant pointers to the equivalent UCHAR types, that is, they are pointers to
vectors of unsigned code units.
The UCHAR types define unsigned code units of the appropriate widths.
For example, PCRE2_UCHAR16 is usually defined as `uint16_t'.
The SPTR types are pointers to constants of the equivalent UCHAR types,
that is, they are pointers to vectors of unsigned code units.
.P
Character strings are passed to a PCRE2 library as sequences of unsigned
integers in code units of the appropriate width. The length of a string may
Expand Down