From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 11 Apr 2019 17:25:34 +0000 (-0400)
Subject: doc:  adjust libpq wording to be neither/nor
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=d4888a3f766a7c02a9330c658c76c60e1ab8cc3e;p=users%2Fbernd%2Fpostgres.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 fe833aa626..7f01fcc148 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -4153,7 +4153,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</function> or
       its sibling routines.
      </para>