pgsql: Doc: use "an SQL" consistently rather than "a SQL"

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: use "an SQL" consistently rather than "a SQL"
Date: 2023-04-11 06:53:20
Message-ID: E1pm7sV-002Uob-Ag@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: use "an SQL" consistently rather than "a SQL"

Similarly to what was done in 04539e73f and 7bdd489d3, we standardized on
SQL being pronounced "es-que-ell" rather than "sequel" in our
documentation.

This fixes the instances of "a SQL" that have crept in during the v16
cycle.

Discussion: https://postgr.es/m/CAApHDvpML27UqFXnrYO1MJddsKVMQoiZisPvsAGhKE_tsKXquw%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d866f0374ca688937b905fbebfcc2c5f8dc88b54

Modified Files
--------------
doc/src/sgml/ecpg.sgml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2023-04-11 07:37:11 pgsql: Improve ereports for VACUUM's BUFFER_USAGE_LIMIT option
Previous Message Kyotaro Horiguchi 2023-04-11 06:29:35 Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option