summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-11-02 15:15:32 +0900
committerMichael Paquier <michael@paquier.xyz>2020-11-02 15:15:32 +0900
commitb99cbbf5ce5174dd644d6b90fb0e4fbe253fa0c8 (patch)
tree87508bc0f45ce689a1319dad7d9a9275896cf8af
parentdd7ae03f8c2a5dbadd4e7e1f288afcecfedbfb32 (diff)
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
-rw-r--r--doc/src/sgml/ddl.sgml2
-rw-r--r--doc/src/sgml/ref/pg_rewind.sgml2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 70f90784298..7ea379bba6e 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3296,7 +3296,7 @@ CREATE INDEX ON measurement_y2008m01 (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 05fb1918499..94517d607d8 100644
--- 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</> directory, or
fetched on startup by configuring <filename>recovery.conf</>. The use of
<application>pg_rewind</> 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>