From: David Rowley Date: Tue, 9 Apr 2024 22:43:31 +0000 (+1200) Subject: Doc: use "an SQL" instead of "a SQL" X-Git-Tag: REL_17_BETA1~296 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b1b13d2b524e64e3bf3538441366bdc8f6d3beda;p=thirdparty%2Fpostgresql.git Doc: use "an SQL" instead of "a SQL" Although which is correct depends entirely on whether you pronounce SQL as "ess-que-ell" or "sequel", we have standardized on the former in our user-facing documentation, so use the correct article according to that pronunciation. Discussion: https://postgr.es/m/CAApHDvp3osQwQam+wNTp9BdhP+QfWO6aY6ZTixQQMfM-UArKCw@mail.gmail.com --- diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index cd8304ef752..00f44f56faf 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -5479,7 +5479,7 @@ CREATE FUNCTION get_color_note (rainbow) RETURNS text AS - On the other hand, for a SQL-language function or procedure whose body + On the other hand, for an SQL-language function or procedure whose body is written in SQL-standard style, the body is parsed at function definition time and all dependencies recognized by the parser are stored. Thus, if we write the function above as