Doc: use "an SQL" consistently rather than "a SQL"
authorDavid Rowley <[email protected]>
Wed, 20 Apr 2022 03:17:56 +0000 (15:17 +1200)
committerDavid Rowley <[email protected]>
Wed, 20 Apr 2022 03:17:56 +0000 (15:17 +1200)
commit7bdd489d3d32d6ab5af1d2b22eaf8cc7dc148027
treef3ec9d0bced1ce13d0afc9c01d4f68d01e174b31
parent344a225cb9d42f20df063e4d0e0d4559c5de7910
Doc: use "an SQL" consistently rather than "a SQL"

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

Two inconsistencies have crept in during the v15 cycle.  The others
existed before but were missed in 04539e73f due to none of the searches
accounting for "SQL" being wrapped in tags.

As with 04539e73f, we don't touch code comments here in order to not
create unnecessary back-patching pain.

Discussion: https://postgr.es/m/CAApHDvpML27UqFXnrYO1MJddsKVMQoiZisPvsAGhKE_tsKXquw%40mail.gmail.com
doc/src/sgml/func.sgml
doc/src/sgml/ref/select.sgml
doc/src/sgml/xfunc.sgml