Fix some grammar and typos in comments and docs

The documentation fixes are backpatched down to where they apply.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20201031020801.GD3080@telsasoft.com
Backpatch-through: 9.6

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 27922867a7aa203ca927a0429af7113b33f87e8b..8fafa5dd04f6e0546b3f672c935c25d9a781792b 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3324,7 +3324,7 @@ CREATE INDEX ON measurement (logdate);
 
     <para>
       Normally the set of partitions established when initially defining the
-      table are not intended to remain static.  It is common to want to
+      table is not intended to remain static.  It is common to want to
       remove old partitions of data and periodically add new partitions for
       new data. One of the most important advantages of partitioning is
       precisely that it allows this otherwise painful task to be executed

diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml
index 3cd6fc9464f7b37e8a9422d6a198d67f53a69329..eeb2a170d10b143e87d00951e06ba3ed3c6975f1 100644 (file)
--- a/doc/src/sgml/ref/pg_rewind.sgml
+++ b/doc/src/sgml/ref/pg_rewind.sgml
@@ -71,7 +71,7 @@ PostgreSQL documentation
    copied from the WAL archive to the <filename>pg_wal</filename> directory, or
    fetched on startup by configuring <filename>recovery.conf</filename>.  The use of
    <application>pg_rewind</application> is not limited to failover, e.g.,  a standby
-   server can be promoted, run some write transactions, and then rewinded
+   server can be promoted, run some write transactions, and then rewound
    to become a standby again.
   </para>