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

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index ad2e3a4466d5365a1391a15f57be705ac7661103..badf3b98e9ac08ed8ae4eec8990e9d97021f6e93 100644 (file)
--- 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>