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

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Dave Page <dpage@pgadmin.org>

Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, David Rowley <dgrowleyml@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-10T08:58:41Z

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 10 Jun 2021, at 10:54, Dave Page <dpage@pgadmin.org> wrote:

> .. I would perhaps suggest extending to any user-visible messages in the code.

I agree, consistent language between docs and user-facing messages is
important.

--
Daniel Gustafsson		https://vmware.com/