Wording improvement (may -> can)

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 06183ec9e76802696bbc98bc156ad19ddc01799a..cea45aa7e518f88a6d278faf3a13d4735c5be8e5 100644 (file)
--- 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 968cb1974946bf71e264e10b44e23104f15d2064..a81dc9defcb55500c8f7ac29a2719378619b3d0c 100644 (file)
--- 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