postgres.git / summary / log / commit / refs

commit    2c31332267ea3d924e201054b20b080278c08305
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Apr 11 17:25:34 2019 +0000
First released in: 12.0, 9.4.22, 9.5.17, 9.6.13, 10.8, 11.3

    doc:  adjust libpq wording to be neither/nor
    
    Reported-by: postgresql@cohi.at
    
    Discussion: https://postgr.es/m/155419437926.737.10876947446993402227@wrigleys.postgresql.org
    
    Backpatch-through: 9.4


 doc/src/sgml/libpq.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index ad2e3a4466d..badf3b98e9a 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -3983,7 +3983,7 @@ char *PQescapeLiteral(PGconn *conn, const char *str, size_t length);
      </tip>
 
      <para>
-      Note that it is not necessary nor correct to do escaping when a data
+      Note that it is neither necessary nor correct to do escaping when a data
       value is passed as a separate parameter in <function>PQexecParams</> or
       its sibling routines.
      </para>


[parent: 99bbff5c1579]