Wording improvement (may -> can)

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index d422003ed106f9414620cc950f403d29d5330477..f308f2eae598a0f2ae8209b394467f5de76cc4ea 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -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

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 97a58cdbcfe557cebd9c7668d7b9669ad0da06b4..0f7f58ec7ac2eca1ceafd30687a2ef645cf0789d 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -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