doc: adjust libpq wording to be neither/nor
authorBruce Momjian <[email protected]>
Thu, 11 Apr 2019 17:25:33 +0000 (13:25 -0400)
committerBruce Momjian <[email protected]>
Thu, 11 Apr 2019 17:25:33 +0000 (13:25 -0400)
Reported-by: [email protected]
Discussion: https://postgr.es/m/155419437926.737.10876947446993402227@wrigleys.postgresql.org

Backpatch-through: 9.4

doc/src/sgml/libpq.sgml

index bf108b727d1eb9959dc6d11db590c23bbdae21cb..223ade8aa2e91b3542ade1f098bbcdbf78b38e67 100644 (file)
@@ -3578,7 +3578,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>