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

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Gavin Flower <GavinFlower@archidevsys.co.nz>, Isaac Morland <isaac.morland@gmail.com>, David Rowley <dgrowleyml@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Dave Page <dpage@pgadmin.org>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-11T16:34:38Z

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

On Thu, Jun 10, 2021 at 05:39:00PM -0400, Andrew Dunstan wrote:
> I suspect "an historic" is bordering on archaic even in the UK these days.

Don't trigger me on the difference between "historic" and "historical"!  ;-)

(Hey, not every day I get to trim quoted text to one line --- see recent
pgsql-general discussion of the topic.)

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.