From b12436340adf27aa3d334c92579e6662dd3090ce Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 10 Mar 2021 12:38:43 -0500 Subject: [PATCH] Doc: get rid of tags. MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit We italicized some, but not all, instances of "per se", "pro forma", and "ad hoc". These phrases are widespread in formal registers of English, so it"s debatable whether they even qualify as foreign. We could instead try to be more consistent in the use of , but that"s difficult to enforce, so let"s just remove the tags for those words. The one case that seems to deserve the tag is "voilà". Instead of keeping just one instance of the tag, change that to a more standard phrase. John Naylor Discussion: https://postgr.es/m/CAFBsxsHtWs_NsccAVgQ=tTUKkXHpHdkjZXtp_Cd9dGWyBDxfbQ@mail.gmail.com --- doc/src/sgml/ddl.sgml | 4 ++-- doc/src/sgml/ref/create_role.sgml | 2 +- doc/src/sgml/rules.sgml | 2 +- doc/src/sgml/typeconv.sgml | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 1e9a4625cc6..422c1180bab 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -2763,8 +2763,8 @@ CREATE SCHEMA myschema; database.schema.table - can be used too, but at present this is just for pro - forma compliance with the SQL standard. If you write a database name, + can be used too, but at present this is just for pro forma + compliance with the SQL standard. If you write a database name, it must be the same as the database you are connected to. diff --git a/doc/src/sgml/ref/create_role.sgml b/doc/src/sgml/ref/create_role.sgml index 73b30d7b23c..b6a4ea1f722 100644 --- a/doc/src/sgml/ref/create_role.sgml +++ b/doc/src/sgml/ref/create_role.sgml @@ -358,7 +358,7 @@ in sync when changing the above synopsis! The VALID UNTIL clause defines an expiration time for a - password only, not for the role per se. In + password only, not for the role per se. In particular, the expiration time is not enforced when logging in using a non-password-based authentication method. diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index b017d3122e3..2ae6925b418 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -1946,7 +1946,7 @@ DELETE FROM shoelace WHERE EXISTS WHERE sl_name = shoelace.sl_name); - Voilà: + The results are: SELECT * FROM shoelace; diff --git a/doc/src/sgml/typeconv.sgml b/doc/src/sgml/typeconv.sgml index 810b0cb5573..103e4c5d99d 100644 --- a/doc/src/sgml/typeconv.sgml +++ b/doc/src/sgml/typeconv.sgml @@ -40,7 +40,7 @@ has an associated data type which determines its behavior and allowed usage. PostgreSQL has an extensible type system that is more general and flexible than other SQL implementations. Hence, most type conversion behavior in PostgreSQL -is governed by general rules rather than by ad hoc +is governed by general rules rather than by ad hoc heuristics. This allows the use of mixed-type expressions even with user-defined types. -- 2.39.5