Wording improvement (may -> can)

This commit is contained in:
Bruce Momjian 2005-05-30 19:32:44 +00:00
parent ac25dbd84b
commit a54c21a59c
2 changed files with 4 additions and 4 deletions

View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.157 2005/05/01 15:54:46 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.158 2005/05/30 19:32:44 momjian Exp $
-->
<chapter id="datatype">
@ -1118,7 +1118,7 @@ SELECT b, char_length(b) FROM test2;
<para>
When entering <type>bytea</type> values, octets of certain values
<emphasis>must</emphasis> be escaped (but all octet values
<emphasis>may</emphasis> be escaped) when used as part of a string
<emphasis>can</emphasis> be escaped) when used as part of a string
literal in an <acronym>SQL</acronym> 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

View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.180 2005/02/26 18:39:04 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.181 2005/05/30 19:32:44 momjian Exp $
-->
<chapter id="libpq">
@ -2229,7 +2229,7 @@ unsigned char *PQescapeBytea(const unsigned char *from,
<para>
Certain byte values <emphasis>must</emphasis> be escaped (but all
byte values <emphasis>may</emphasis> be escaped) when used as part
byte values <emphasis>can</emphasis> be escaped) when used as part
of a <type>bytea</type> literal in an <acronym>SQL</acronym>
statement. In general, to escape a byte, it is converted into the
three digit octal number equal to the octet value, and preceded by