doc: Fix some grammar

This is an extraction of the user-visible changes done in 410aa24,
including all the relevant documentation parts.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20220124030001[email protected]
Backpatch-through: 10

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index c09760ef574a36ebcd8b50d8c2297ab6f6cb4100..d046614d76526b7cfb9a45c09819e3077d4b8cf1 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -8208,8 +8208,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
         This parameter specifies the default table access method to use when
         creating tables or materialized views if the CREATE
         command does not explicitly specify an access method, or when
-        SELECT ... INTO is used, which does not allow to
-        specify a table access method. The default is heap.
+        SELECT ... INTO is used, which does not allow
+        specifying a table access method. The default is heap.
        
       
      

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index e0ffb020bf99b0c8bc5b21697c9a3a78b2e09160..a58ff277eb55704ff8a558dc8a5bec429208aea9 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3986,7 +3986,7 @@ ALTER TABLE measurement ATTACH PARTITION measurement_y2008m02
      holding an ACCESS EXCLUSIVE lock on that partition.
      It is recommended to drop the now-redundant CHECK
      constraint after the ATTACH PARTITION is complete.  If
-     the table being attached is itself a partitioned table then each of its
+     the table being attached is itself a partitioned table, then each of its
      sub-partitions will be recursively locked and scanned until either a
      suitable CHECK constraint is encountered or the leaf
      partitions are reached.
@@ -4001,7 +4001,7 @@ ALTER TABLE measurement ATTACH PARTITION measurement_y2008m02
      the partition being attached.  This operation will be performed whilst
      holding an ACCESS EXCLUSIVE lock on the 
      DEFAULT partition.  If the DEFAULT partition
-     is itself a partitioned table then each of its partitions will be
+     is itself a partitioned table, then each of its partitions will be
      recursively checked in the same way as the table being attached, as
      mentioned above.
     

diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml
index 89ff58338e5db0362687f0d5489e7fa43e630cac..9cf8ebea8088ce1347591dd4d2fa71d42947b654 100644 (file)
--- a/doc/src/sgml/perform.sgml
+++ b/doc/src/sgml/perform.sgml
@@ -1337,7 +1337,7 @@ nd | {"1, 2": 33178, "1, 5": 33178, "2, 5": 27435, "1, 2, 5": 33178}
     Multivariate MCV Lists
 
     
-     Another type of statistics stored for each column are most-common value
+     Another type of statistic stored for each column are most-common value
      lists.  This allows very accurate estimates for individual columns, but
      may result in significant misestimates for queries with conditions on
      multiple columns.

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 1f425a08decd0a08740b4467adbd25ca04b713ef..d2111d817fb97b99ac5a1242af70ea12e81c0d9f 100644 (file)
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -2078,7 +2078,7 @@ The commands accepted in replication mode are:
       streaming starts on timeline tli;
       otherwise, the server's current timeline is selected. The server can
       reply with an error, for example if the requested section of WAL has already
-      been recycled. On success, server responds with a CopyBothResponse
+      been recycled. On success, the server responds with a CopyBothResponse
       message, and then starts to stream WAL to the frontend.
      
 

diff --git a/doc/src/sgml/ref/pg_receivewal.sgml b/doc/src/sgml/ref/pg_receivewal.sgml
index 6da8b2be8c09182b9586b9365b8e221bfb5236d6..96cc40957af9099db0cc136c491d3d42d122d64c 100644 (file)
--- a/doc/src/sgml/ref/pg_receivewal.sgml
+++ b/doc/src/sgml/ref/pg_receivewal.sgml
@@ -82,9 +82,8 @@ PostgreSQL documentation
     
      
       First, scan the directory where the WAL segment files are written and
-      find the newest completed segment file, using as starting point the
-      beginning of the next WAL segment file. This is calculated independently
-      on the compression method used to compress each segment.
+      find the newest completed segment file, using as the starting point the
+      beginning of the next WAL segment file.
      
     
 
@@ -92,7 +91,7 @@ PostgreSQL documentation
      
       If a starting point cannot be calculated with the previous method,
       the latest WAL flush location is used as reported by the server from
-      a IDENTIFY_SYSTEM command.
+      an IDENTIFY_SYSTEM command.
      
     
    

diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml
index acc6401485b77599f577980be81e306261f250b4..82a77784b99763e20eefe1903692324b9de1f761 100644 (file)
--- a/doc/src/sgml/ref/select_into.sgml
+++ b/doc/src/sgml/ref/select_into.sgml
@@ -107,7 +107,7 @@ SELECT [ ALL | DISTINCT [ ON ( expression
 
   
    In contrast to CREATE TABLE AS, SELECT
-   INTO does not allow to specify properties like a table's access
+   INTO does not allow specifying properties like a table's access
    method with  or the table's
    tablespace with . Use
    CREATE TABLE AS if necessary.  Therefore, the default table