8000 doc: Properly punctuate "etc." · postgrespro/postgres@648aa67 · GitHub
[go: up one dir, main page]
Skip to content

Commit 648aa67

Browse files
peterepetere
committed
doc: Properly punctuate "etc."
1 parent c4a4e76 commit 648aa67

19 files changed

+32
-32
lines changed

‎doc/src/sgml/arch-dev.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,7 +261,7 @@
261261
system catalog lookups can only be done within a transaction, and we
262262
do not wish to start a transaction immediately upon receiving a query
263263
string. The raw parsing stage is sufficient to identify the transaction
264-
control commands (<command>BEGIN</command>, <command>ROLLBACK</command>, etc), and
264+
control commands (<command>BEGIN</command>, <command>ROLLBACK</command>, etc.), and
265265
these can then be correctly executed without any further analysis.
266266
Once we know that we are dealing with an actual query (such as
267267
<command>SELECT</command> or <command>UPDATE</command>), it is okay to

‎doc/src/sgml/bki.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -836,11 +836,11 @@ $ perl rewrite_dat_with_prokind.pl pg_proc.dat
836836
When <literal>bootstrap</literal> is specified,
837837
the table will only be created on disk; nothing is entered into
838838
<structname>pg_class</structname>,
839-
<structname>pg_attribute</structname>, etc, for it. Thus the
839+
<structname>pg_attribute</structname>, etc., for it. Thus the
840840
table will not be accessible by ordinary SQL operations until
841841
such entries are made the hard way (with <literal>insert</literal>
842842
commands). This option is used for creating
843-
<structname>pg_class</structname> etc themselves.
843+
<structname>pg_class</structname> etc. themselves.
844844
</para>
845845

846846
<para>

‎doc/src/sgml/config.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6374,7 +6374,7 @@ local0.* /var/log/postgresql
63746374
<para>
63756375
Example: To keep 7 days of logs, one log file per day named
63766376
<literal>server_log.Mon</literal>, <literal>server_log.Tue</literal>,
6377-
etc, and automatically overwrite last week's log with this week's log,
6377+
etc., and automatically overwrite last week's log with this week's log,
63786378
set <varname>log_filename</varname> to <literal>server_log.%a</literal>,
63796379
<varname>log_truncate_on_rotation</varname> to <literal>on</literal>, and
63806380
<varname>log_rotation_age</varname> to <literal>1440</literal>.
@@ -8552,7 +8552,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
85528552
alias <literal>pg_temp</literal><indexterm><primary>pg_temp</primary></indexterm>. If it is not listed in the path then
85538553
it is searched first (even before <literal>pg_catalog</literal>). However,
85548554
the temporary schema is only searched for relation (table, view,
8555-
sequence, etc) and data type names. It is never searched for
8555+
sequence, etc.) and data type names. It is never searched for
85568556
function or operator names.
85578557
</para>
85588558

‎doc/src/sgml/datetime.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -515,7 +515,7 @@
515515

516516
<para>
517517
For reference purposes, a standard installation also contains files
518-
<filename>Africa.txt</filename>, <filename>America.txt</filename>, etc, containing
518+
<filename>Africa.txt</filename>, <filename>America.txt</filename>, etc., containing
519519
information about every time zone abbreviation known to be in use
520520
according to the IANA timezone database. The zone name
521521
definitions found in these files can be copied and pasted into a custom

‎doc/src/sgml/ddl.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1694,7 +1694,7 @@ ALTER TABLE products RENAME TO items;
16941694
<literal>EXECUTE</literal>, <literal>USAGE</literal>, <literal>SET</literal>
16951695
and <literal>ALTER SYSTEM</literal>.
16961696
The privileges applicable to a particular
1697-
object vary depending on the object's type (table, function, etc).
1697+
object vary depending on the object's type (table, function, etc.).
16981698
More detail about the meanings of these privileges appears below.
16991699
The following sections and chapters will also show you how
17001700
these privileges are used.

‎doc/src/sgml/extend.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -825,7 +825,7 @@ RETURNS anycompatible AS ...
825825
<para>
826826
An extension's <acronym>SQL</acronym> script files can contain any SQL commands,
827827
except for transaction control commands (<command>BEGIN</command>,
828-
<command>COMMIT</command>, etc) and commands that cannot be executed inside a
828+
<command>COMMIT</command>, etc.) and commands that cannot be executed inside a
829829
transaction block (such as <command>VACUUM</command>). This is because the
830830
script files are implicitly executed within a transaction block.
831831
</para>

‎doc/src/sgml/func.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6156,7 +6156,7 @@ regexp_substr('ABCDEFGHI', '(c..)(...)', 1, 1, 'i', 2)
61566156
<para>
61576157
A branch is zero or more <firstterm>quantified atoms</firstterm> or
61586158
<firstterm>constraints</firstterm>, concatenated.
6159-
It matches a match for the first, followed by a match for the second, etc;
6159+
It matches a match for the first, followed by a match for the second, etc.;
61606160
an empty branch matches the empty string.
61616161
</para>
61626162

‎doc/src/sgml/glossary.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1389,7 +1389,7 @@
13891389
<para>
13901390
More generically, the term <firstterm>schema</firstterm> is used to mean
13911391
all data descriptions (<glossterm linkend="glossary-table">table</glossterm> definitions,
1392-
<glossterm linkend="glossary-constraint">constraints</glossterm>, comments, etc)
1392+
<glossterm linkend="glossary-constraint">constraints</glossterm>, comments, etc.)
13931393
for a given <glossterm linkend="glossary-database">database</glossterm> or
13941394
subset thereof.
13951395
</para>

‎doc/src/sgml/libpq.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3049,7 +3049,7 @@ PGresult *PQdescribePrepared(PGconn *conn, const char *stmtName);
30493049
<structname>PGresult</structname> to obtain information about the parameters
30503050
of the prepared statement, and the functions
30513051
<xref linkend="libpq-PQnfields"/>, <xref linkend="libpq-PQfname"/>,
3052-
<xref linkend="libpq-PQftype"/>, etc provide information about the
3052+
<xref linkend="libpq-PQftype"/>, etc. provide information about the
30533053
result columns (if any) of the statement.
30543054
</para>
30553055
</listitem>
@@ -3081,7 +3081,7 @@ PGresult *PQdescribePortal(PGconn *conn, const char *portalName);
30813081
portal. On success, a <structname>PGresult</structname> with status
30823082
<literal>PGRES_COMMAND_OK</literal> is returned. The functions
30833083
<xref linkend="libpq-PQnfields"/>, <xref linkend="libpq-PQfname"/>,
3084-
<xref linkend="libpq-PQftype"/>, etc can be applied to the
3084+
<xref linkend="libpq-PQftype"/>, etc. can be applied to the
30853085
<structname>PGresult</structname> to obtain information about the result
30863086
columns (if any) of the portal.
30873087
</para>
@@ -5544,7 +5544,7 @@ UPDATE mytable SET x = x + 1 WHERE id = 42;
55445544
more rows will arrive. (But note that it is still necessary to continue
55455545
calling <xref linkend="libpq-PQgetResult"/> until it returns null.) All of
55465546
these <structname>PGresult</structname> objects will contain the same row
5547-
description data (column names, types, etc) that an ordinary
5547+
description data (column names, types, etc.) that an ordinary
55485548
<structname>PGresult</structname> object for the query would have.
55495549
Each object should be freed with <xref linkend="libpq-PQclear"/> as usual.
55505550
</para>
@@ -6010,7 +6010,7 @@ typedef struct pgNotify
60106010
<listitem>
60116011
<para>
60126012
0 indicates the overall copy format is textual (rows separated by
6013-
newlines, columns separated by separator characters, etc). 1
6013+
newlines, columns separated by separator characters, etc.). 1
60146014
indicates the overall copy format is binary. See <xref
60156015
linkend="sql-copy"/> for more information.
60166016
</para>

‎doc/src/sgml/manage-ag.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -412,7 +412,7 @@ dropdb <replaceable class="parameter">dbname</replaceable>
412412
of data files. They are dependent on metadata contained in the main
413413
data directory, and therefore cannot be attached to a different
414414
database cluster or backed up individually. Similarly, if you lose
415-
a tablespace (file deletion, disk failure, etc), the database cluster
415+
a tablespace (file deletion, disk failure, etc.), the database cluster
416416
might become unreadable or unable to start. Placing a tablespace
417417
on a temporary file system like a RAM disk risks the reliability of
418418
the entire cluster.

0 commit comments

Comments
 (0)
0