From: Bruce Momjian Date: Mon, 30 May 2005 19:32:44 +0000 (+0000) Subject: Wording improvement (may -> can) X-Git-Tag: REL8_1_0BETA1~692 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a54c21a59c35b143f2b242a554138d8bb6ff5a11;p=postgresql Wording improvement (may -> can) --- diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 06183ec9e7..cea45aa7e5 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ @@ -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 968cb19749..a81dc9defc 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ @@ -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