Fix some typos, grammar and style in docs and comments

The portions fixing the documentation are backpatched where needed.

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

diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 70b45f494ef7ff783bc11b9aca02c5cf542c4495..2666b33e7ac7c3011badc5338fb8804aa4c65b92 100644 (file)
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -617,7 +617,7 @@ SELECT * FROM test1 ORDER BY a || b COLLATE "fr_FR";
     name such as de_DE can be considered unique
     within a given database even though it would not be unique globally.
     Use of the stripped collation names is recommended, since it will
-    make one less thing you need to change if you decide to change to
+    make one fewer thing you need to change if you decide to change to
     another database encoding.  Note however that the default,
     C, and POSIX collations can be used regardless of
     the database encoding.

diff --git a/doc/src/sgml/pageinspect.sgml b/doc/src/sgml/pageinspect.sgml
index 7a767b25ea958d39483bfdab165cecedc3d8aa0d..0d515781fc7cd4f56198d1962470573f0a732df3 100644 (file)
--- a/doc/src/sgml/pageinspect.sgml
+++ b/doc/src/sgml/pageinspect.sgml
@@ -206,7 +206,7 @@ test=# SELECT tuple_data_split('pg_class'::regclass, t_data, t_infomask, t_infom
      
      
       If do_detoast is true,
-      attribute that will be detoasted as needed. Default value is
+      attributes will be detoasted as needed. Default value is
       false.
      
     

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index df3520f8bcf6e59691304e8aac4550193831049b..ec8565298d63bfb29a5000255be97338ff578fdf 100644 (file)
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -6882,8 +6882,8 @@ Delete
 
 
 
-                Identifies the following TupleData message as a old tuple.
-                This field is present if the table in which the delete has
+                Identifies the following TupleData message as an old tuple.
+                This field is present if the table in which the delete
                 happened has REPLICA IDENTITY set to FULL.
 
 

diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml
index 175315f3d7e456332a2b9c667773727e2d3e5f46..4d927b0bfae61e9eedbe603ec17b2145d1b0f4d6 100644 (file)
--- a/doc/src/sgml/ref/create_type.sgml
+++ b/doc/src/sgml/ref/create_type.sgml
@@ -790,7 +790,7 @@ CREATE TYPE name
    Before PostgreSQL version 8.3, the name of
    a generated array type was always exactly the element type's name with one
    underscore character (_) prepended.  (Type names were
-   therefore restricted in length to one less character than other names.)
+   therefore restricted in length to one fewer character than other names.)
    While this is still usually the case, the array type name may vary from
    this in case of maximum-length names or collisions with user type names
    that begin with underscore.  Writing code that depends on this convention

diff --git a/doc/src/sgml/ref/drop_index.sgml b/doc/src/sgml/ref/drop_index.sgml
index 85cf23bca20aa06219e548aa675b9aab99aa1dc6..b6d2c2014f28e82d6f69aa41e4eb9fb0b931a4c4 100644 (file)
--- a/doc/src/sgml/ref/drop_index.sgml
+++ b/doc/src/sgml/ref/drop_index.sgml
@@ -45,7 +45,7 @@ DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ] name
      
       Drop the index without locking out concurrent selects, inserts, updates,
       and deletes on the index's table.  A normal DROP INDEX
-      acquires exclusive lock on the table, blocking other accesses until the
+      acquires an exclusive lock on the table, blocking other accesses until the
       index drop can be completed.  With this option, the command instead
       waits until conflicting transactions have completed.
      

diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
index 3d9d8b400d97e41ccf22bfb9ec3754a1d4c2293a..7f7548d98122b73fae25459848007ca3eef53761 100644 (file)
--- a/doc/src/sgml/rules.sgml
+++ b/doc/src/sgml/rules.sgml
@@ -1265,7 +1265,7 @@ CREATE [ OR REPLACE ] RULE name AS
 
     The query trees generated from rule actions are thrown into the
     rewrite system again, and maybe more rules get applied resulting
-    in more or less query trees.
+    in additional or fewer query trees.
     So a rule's actions must have either a different
     command type or a different result relation than the rule itself is
     on, otherwise this recursive process will end up in an infinite loop.