1
0
mirror of https://github.com/postgres/postgres.git synced 2025-10-22 14:32:25 +03:00

doc: add commas after 'i.e.' and 'e.g.'

This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.

Discussion: https://postgr.es/m/20200825183619.GA22369@momjian.us

Backpatch-through: 9.5
This commit is contained in:
Bruce Momjian
2020-08-31 18:33:37 -04:00
parent 50ed605b3e
commit 953c64e0f6
46 changed files with 103 additions and 103 deletions

View File

@@ -219,7 +219,7 @@ protocol to make nodes agree on a serializable transactional order.
this is unacceptable, either the middleware or the application
must query such values from a single server and then use those
values in write queries. Another option is to use this replication
option with a traditional primary-standby setup, i.e. data modification
option with a traditional primary-standby setup, i.e., data modification
queries are sent only to the primary and are propagated to the
standby servers via primary-standby replication, not by the replication
middleware. Care must also be taken that all
@@ -662,7 +662,7 @@ protocol to make nodes agree on a serializable transactional order.
Set up continuous archiving on the primary to an archive directory
accessible from the standby, as described
in <xref linkend="continuous-archiving"/>. The archive location should be
accessible from the standby even when the primary is down, i.e. it should
accessible from the standby even when the primary is down, i.e., it should
reside on the standby server itself or another trusted server, not on
the primary server.
</para>
@@ -2232,7 +2232,7 @@ LOG: database system is ready to accept read only connections
<itemizedlist>
<listitem>
<para>
Data Definition Language (DDL): e.g. <command>CREATE INDEX</command>
Data Definition Language (DDL): e.g., <command>CREATE INDEX</command>
</para>
</listitem>
<listitem>
@@ -2298,7 +2298,7 @@ LOG: database system is ready to accept read only connections
<para>
WAL file control commands will not work during recovery,
e.g. <function>pg_start_backup</function>, <function>pg_switch_wal</function> etc.
e.g., <function>pg_start_backup</function>, <function>pg_switch_wal</function> etc.
</para>
<para>