doc: Fix some grammar and inconsistencies

Some comments are fixed while on it.

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

diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index 7e1a3b454fe2022d4b22c190501db51d3511d278..42c004f151212e73461a56657e25416b84290c96 100644 (file)
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -223,7 +223,7 @@ $ pg_recvlogical -d postgres --slot test --drop-slot
      A logical slot will emit each change just once in normal operation.
      The current position of each slot is persisted only at checkpoint, so in
      the case of a crash the slot may return to an earlier LSN, which will
-     then cause recent changes to be resent when the server restarts.
+     then cause recent changes to be sent again when the server restarts.
      Logical decoding clients are responsible for avoiding ill effects from
      handling the same message more than once.  Clients may wish to record
      the last LSN they saw when decoding and skip over any repeated data or

diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 946176213c0c00d0a8d69a1a4abe68a7182cc150..7d652541d2c2ad37cb7a793069f84672f94461df 100644 (file)
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -786,7 +786,7 @@ ALTER TABLE [ IF EXISTS ] name
       UNIQUE, PRIMARY KEY, and
       FOREIGN KEY constraints are not considered.
       If any of the CHECK constraints of the table being
-      attached is marked NO INHERIT, the command will fail;
+      attached are marked NO INHERIT, the command will fail;
       such constraints must be recreated without the
       NO INHERIT clause.
      

diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml
index 30e1925804269562e56b7481e460fa0b10cc6d9f..1af245c02f2bbd7abfa1911359c3c8161bf7ee9f 100644 (file)
--- a/doc/src/sgml/ref/create_subscription.sgml
+++ b/doc/src/sgml/ref/create_subscription.sgml
@@ -159,7 +159,7 @@ CREATE SUBSCRIPTION subscription_name
          
           It is safe to use off for logical replication:
           If the subscriber loses transactions because of missing
-          synchronization, the data will be resent from the publisher.
+          synchronization, the data will be sent again from the publisher.
          
 
          

diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml
index a78eb789263e8117c98f8b3e39aff934e601cb17..a1a14a43a0703d0e1c86c7b5cc011f7ba0ea7d38 100644 (file)
--- a/doc/src/sgml/sources.sgml
+++ b/doc/src/sgml/sources.sgml
@@ -359,7 +359,7 @@ ereport(ERROR,
      specify suppression of the CONTEXT: portion of a message in
      the postmaster log.  This should only be used for verbose debugging
      messages where the repeated inclusion of context would bloat the log
-     volume too much.
+     too much.
     
    
   

diff --git a/src/backend/storage/lmgr/proc.c b/src/backend/storage/lmgr/proc.c
index 1f93576a99f7a185a1ef142228bc80a4ceac25af..1da6d7f7c66521b0530e6eb99c4168a92ad2a9d4 100644 (file)
--- a/src/backend/storage/lmgr/proc.c
+++ b/src/backend/storage/lmgr/proc.c
@@ -1341,7 +1341,7 @@ ProcSleep(LOCALLOCK *locallock, LockMethod lockMethodTable)
            else
                LWLockRelease(ProcArrayLock);
 
-           /* prevent signal from being resent more than once */
+           /* prevent signal from being sent again more than once */
            allow_autovacuum_cancel = false;
        }