Re: "an SQL" vs. "a SQL"

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2024-04-09T04:18:00Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Doc: use "an SQL" consistently rather than "a SQL"
- a78cf591a3f5 19 (unreleased) landed
- d866f0374ca6 16.0 landed
- 7bdd489d3d32 15.0 landed
Doc: use "an SQL" instead of "a SQL"
- b1b13d2b524e 17.0 landed
Use the correct article for abbreviations
- 04539e73faaa 14.0 landed

Attachments

use_an_SQL_not_a_SQL.patch (text/plain) patch

On Tue, 11 Apr 2023 at 17:43, David Rowley <dgrowleyml@gmail.com> wrote:
>
> On Fri, 11 Jun 2021 at 13:44, David Rowley <dgrowleyml@gmail.com> wrote:
> > Anyway, I'll set an alarm for this time next year so I can check on
> > how many inconsistencies have crept back in over the development
> > cycle.
>
> That alarm went off today.
>
> There seem to be only 3 "a SQL"s in the docs to change to "an SQL".
>
> This is a pretty old thread, so here's a link [1] to the discussion.
>
> [1] https://postgr.es/m/CAApHDvpML27UqFXnrYO1MJddsKVMQoiZisPvsAGhKE_tsKXquw@mail.gmail.com

Link to the old thread above.

There's just 1 instance of "a SQL" that crept into PG16 after
d866f0374.  This probably means I'd be better off doing this in June a
few weeks before branching...

Patch attached.

David