doc: Properly punctuate "etc."

Author: petere

doc/src/sgml/arch-dev.sgml

@@ -261,7 +261,7 @@
  system catalog lookups can only be done within a transaction, and we
  do not wish to start a transaction immediately upon receiving a query
  string. The raw parsing stage is sufficient to identify the transaction
- control commands (<command>BEGIN</command>, <command>ROLLBACK</command>, etc), and
+ control commands (<command>BEGIN</command>, <command>ROLLBACK</command>, etc.), and
  these can then be correctly executed without any further analysis.
  Once we know that we are dealing with an actual query (such as
  <command>SELECT</command> or <command>UPDATE</command>), it is okay to

doc/src/sgml/bki.sgml

@@ -836,11 +836,11 @@ $ perl rewrite_dat_with_prokind.pl pg_proc.dat
  When <literal>bootstrap</literal> is specified,
  the table will only be created on disk; nothing is entered into
  <structname>pg_class</structname>,
- <structname>pg_attribute</structname>, etc, for it. Thus the
+ <structname>pg_attribute</structname>, etc., for it. Thus the
  table will not be accessible by ordinary SQL operations until
  such entries are made the hard way (with <literal>insert</literal>
  commands). This option is used for creating
- <structname>pg_class</structname> etc themselves.
+ <structname>pg_class</structname> etc. themselves.
  </para>
 
  <para>

doc/src/sgml/config.sgml

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

doc/src/sgml/datetime.sgml

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

doc/src/sgml/ddl.sgml

@@ -1694,7 +1694,7 @@ ALTER TABLE products RENAME TO items;
  <literal>EXECUTE</literal>, <literal>USAGE</literal>, <literal>SET</literal>
  and <literal>ALTER SYSTEM</literal>.
  The privileges applicable to a particular
- object vary depending on the object's type (table, function, etc).
+ object vary depending on the object's type (table, function, etc.).
  More detail about the meanings of these privileges appears below.
  The following sections and chapters will also show you how
  these privileges are used.

doc/src/sgml/extend.sgml

@@ -825,7 +825,7 @@ RETURNS anycompatible AS ...
  <para>
  An extension's <acronym>SQL</acronym> script files can contain any SQL commands,
  except for transaction control commands (<command>BEGIN</command>,
- <command>COMMIT</command>, etc) and commands that cannot be executed inside a
+ <command>COMMIT</command>, etc.) and commands that cannot be executed inside a
  transaction block (such as <command>VACUUM</command>). This is because the
  script files are implicitly executed within a transaction block.
  </para>

doc/src/sgml/func.sgml

@@ -6156,7 +6156,7 @@ regexp_substr('ABCDEFGHI', '(c..)(...)', 1, 1, 'i', 2)
  <para>
  A branch is zero or more <firstterm>quantified atoms</firstterm> or
  <firstterm>constraints</firstterm>, concatenated.
- It matches a match for the first, followed by a match for the second, etc;
+ It matches a match for the first, followed by a match for the second, etc.;
  an empty branch matches the empty string.
  </para>
 

doc/src/sgml/glossary.sgml

@@ -1389,7 +1389,7 @@
  <para>
  More generically, the term <firstterm>schema</firstterm> is used to mean
  all data descriptions (<glossterm linkend="glossary-table">table</glossterm> definitions,
- <glossterm linkend="glossary-constraint">constraints</glossterm>, comments, etc)
+ <glossterm linkend="glossary-constraint">constraints</glossterm>, comments, etc.)
  for a given <glossterm linkend="glossary-database">database</glossterm> or
  subset thereof.
  </para>

doc/src/sgml/libpq.sgml

@@ -3049,7 +3049,7 @@ PGresult *PQdescribePrepared(PGconn *conn, const char *stmtName);
  <structname>PGresult</structname> to obtain information about the parameters
  of the prepared statement, and the functions
  <xref linkend="libpq-PQnfields"/>, <xref linkend="libpq-PQfname"/>,
- <xref linkend="libpq-PQftype"/>, etc provide information about the
+ <xref linkend="libpq-PQftype"/>, etc. provide information about the
  result columns (if any) of the statement.
  </para>
  </listitem>
@@ -3081,7 +3081,7 @@ PGresult *PQdescribePortal(PGconn *conn, const char *portalName);
  portal. On success, a <structname>PGresult</structname> with status
  <literal>PGRES_COMMAND_OK</literal> is returned. The functions
  <xref linkend="libpq-PQnfields"/>, <xref linkend="libpq-PQfname"/>,
- <xref linkend="libpq-PQftype"/>, etc can be applied to the
+ <xref linkend="libpq-PQftype"/>, etc. can be applied to the
  <structname>PGresult</structname> to obtain information about the result
  columns (if any) of the portal.
  </para>
@@ -5544,7 +5544,7 @@ UPDATE mytable SET x = x + 1 WHERE id = 42;
  more rows will arrive. (But note that it is still necessary to continue
  calling <xref linkend="libpq-PQgetResult"/> until it returns null.) All of
  these <structname>PGresult</structname> objects will contain the same row
- description data (column names, types, etc) that an ordinary
+ description data (column names, types, etc.) that an ordinary
  <structname>PGresult</structname> object for the query would have.
  Each object should be freed with <xref linkend="libpq-PQclear"/> as usual.
  </para>
@@ -6010,7 +6010,7 @@ typedef struct pgNotify
  <listitem>
  <para>
  0 indicates the overall copy format is textual (rows separated by
- newlines, columns separated by separator characters, etc). 1
+ newlines, columns separated by separator characters, etc.). 1
  indicates the overall copy format is binary. See <xref
  linkend="sql-copy"/> for more information.
  </para>

doc/src/sgml/manage-ag.sgml

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