From b51f86e49a7f119004c0ce5d0be89cdf98309141 Mon Sep 17 00:00:00 2001
From: David Rowley <drowley@postgresql.org>
Date: Mon, 14 Apr 2025 11:55:18 +1200
Subject: [PATCH] Doc: use "an SQL" consistently rather than "a SQL"

Per the precedent set by 04539e73f, adjust article prefixes for "SQL" to
use "an" consistently rather than "a", i.e., "an es-que-ell" rather than
"a sequel".

Both of these are new to v18. Also see b1b13d2b5, d866f0374 and
7bdd489d3.
---
 doc/src/sgml/ref/copy.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index d6859276bed..8433344e5b6 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -677,7 +677,7 @@ COPY <replaceable class="parameter">count</replaceable>
     backward compatibility.  However, <application>psql</application>
     uses <literal>\.</literal> to terminate a <literal>COPY FROM
     STDIN</literal> operation (that is, reading
-    in-line <command>COPY</command> data in a SQL script).  In that
+    in-line <command>COPY</command> data in an SQL script).  In that
     context the rule is needed to be able to end the operation before the
     end of the script.
    </para>
@@ -844,7 +844,7 @@ COPY <replaceable class="parameter">count</replaceable>
     is not normally treated as special when reading <literal>CSV</literal>
     data.  An exception is that <application>psql</application> will terminate
     a <literal>COPY FROM STDIN</literal> operation (that is, reading
-    in-line <command>COPY</command> data in a SQL script) at a line containing
+    in-line <command>COPY</command> data in an SQL script) at a line containing
     only <literal>\.</literal>, whether it is text or <literal>CSV</literal>
     mode.
    </para>