Fix typos and grammar in documentation and code comments

Comment fixes are applied on HEAD, and documentation improvements are
applied on back-branches where needed.

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

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index ce8f722948fd1162fe0304d97887bc254c53496b..eaf1d75b85a31cd9e55151fcafe9894e6bbdd792 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -185,7 +185,7 @@
     never issue VACUUM FULL.  In this approach, the idea
     is not to keep tables at their minimum size, but to maintain steady-state
     usage of disk space: each table occupies space equivalent to its
-    minimum size plus however much space gets used up between vacuumings.
+    minimum size plus however much space gets used up between vacuum runs.
     Although VACUUM FULL can be used to shrink a table back
     to its minimum size and return the disk space to the operating system,
     there is not much point in this if the table will just grow again in the

diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index e56c4af9b1747d2ec24214628e260391fbeaf1be..3be4c888b0014e69147ec0bd89c06491d7d8be57 100644 (file)
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -1488,7 +1488,7 @@ WITH ( MODULUS numeric_literal, REM
     
    
 
-   
+   cuum-scale-factor" xreflabel="autovacuum_vacuum_scale_factor">
     autovacuum_vacuum_scale_factor, toast.autovacuum_vacuum_scale_factor (floating point)
     
      autovacuum_vacuum_scale_factor 
@@ -1578,7 +1578,7 @@ WITH ( MODULUS numeric_literal, REM
     
    
 
-   
+   cuum-cost-limit" xreflabel="autovacuum_vacuum_cost_limit">
     autovacuum_vacuum_cost_limit, toast.autovacuum_vacuum_cost_limit (integer)
     
      autovacuum_vacuum_cost_limit

diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml
index 9d24df8b7a8879e5e3de695f943eced5dd1ebbe4..f43b4a4adaa3074b71f32107e584cbf8aef37e0d 100644 (file)
--- a/doc/src/sgml/ref/createuser.sgml
+++ b/doc/src/sgml/ref/createuser.sgml
@@ -44,7 +44,7 @@ PostgreSQL documentation
    If you wish to create a new superuser, you must connect as a
    superuser, not merely with CREATEROLE privilege.
    Being a superuser implies the ability to bypass all access permission
-   checks within the database, so superuserdom should not be granted lightly.
+   checks within the database, so superuser access should not be granted lightly.