From 8dd0a1de07d86af84b1fd03c46ec437a6ca662ed Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 30 May 2005 19:32:44 +0000 Subject: [PATCH] Wording improvement (may -> can) --- doc/src/sgml/datatype.sgml | 2 +- doc/src/sgml/libpq.sgml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index d422003ed1..f308f2eae5 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1118,7 +1118,7 @@ SELECT b, char_length(b) FROM test2; When entering bytea values, octets of certain values must be escaped (but all octet values - may be escaped) when used as part of a string + can be escaped) when used as part of a string literal in an SQL statement. In general, to escape an octet, it is converted into the three-digit octal number equivalent of its decimal octet value, and preceded by two diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 97a58cdbcf..0f7f58ec7a 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -2229,7 +2229,7 @@ unsigned char *PQescapeBytea(const unsigned char *from, Certain byte values must be escaped (but all - byte values may be escaped) when used as part + byte values can be escaped) when used as part of a bytea literal in an SQL statement. In general, to escape a byte, it is converted into the three digit octal number equal to the octet value, and preceded by -- 2.39.5