From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 11 Apr 2019 17:25:33 +0000 (-0400)
Subject: doc:  adjust libpq wording to be neither/nor
X-Git-Tag: REL9_4_22~21
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f4daf89582196596b947b9be96394a1f63a986dc;p=thirdparty%2Fpostgresql.git

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 bf108b727d1..223ade8aa2e 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -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>