doc: Spell checking

Author: petere

doc/src/sgml/backup.sgml

@@ -40,7 +40,7 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
    As you see, <application>pg_dump</> writes its result to the
    standard output. We will see below how this can be useful.
    While the above command creates a text file, <application>pg_dump</>
-   can create files in other formats that allow for parallism and more
+   can create files in other formats that allow for parallelism and more
    fine-grained control of object restoration.
   </para>
 
@@ -221,7 +221,7 @@ psql -f <replaceable class="parameter">infile</replaceable> postgres
     roles, tablespaces, and empty databases, then invoking
     <application>pg_dump</> for each database.  This means that while
     each database will be internally consistent, the snapshots of
-    different databases are not sychronized.
+    different databases are not synchronized.
    </para>
 
    <para>

doc/src/sgml/brin.sgml

@@ -532,7 +532,7 @@ typedef struct BrinOpcInfo
   The core distribution includes support for two types of operator classes:
   minmax and inclusion.  Operator class definitions using them are shipped for
   in-core data types as appropriate.  Additional operator classes can be
-  defined by the user for other datatypes using equivalent definitions,
+  defined by the user for other data types using equivalent definitions,
   without having to write any source code; appropriate catalog entries being
   declared is enough.  Note that assumptions about the semantics of operator
   strategies are embedded in the support procedures's source code.
@@ -547,8 +547,8 @@ typedef struct BrinOpcInfo
  </para>
 
  <para>
-  To write an operator class for a datatype that implements a totally
-  ordered set, it is possible to use the Minmax support procedures
+  To write an operator class for a data type that implements a totally
+  ordered set, it is possible to use the minmax support procedures
   alongside the corresponding operators, as shown in
   <xref linkend="brin-extensibility-minmax-table">.
   All operator class members (procedures and operators) are mandatory.

doc/src/sgml/catalogs.sgml

@@ -7946,7 +7946,7 @@
     <row>
      <entry><structfield>sourcefile</structfield></entry>
      <entry><structfield>text</structfield></entry>
-     <entry>Full pathname of the configuration file</entry>
+     <entry>Full path name of the configuration file</entry>
     </row>
     <row>
      <entry><structfield>sourceline</structfield></entry>

doc/src/sgml/client-auth.sgml

@@ -958,11 +958,11 @@ omicron         bryanh                  guest1
     <productname>PostgreSQL</> also supports a parameter to strip the realm from
     the principal.  This method is supported for backwards compatibility and is
     strongly discouraged as it is then impossible to distinguish different users
-    with the same username but coming from different realms.  To enable this,
+    with the same user name but coming from different realms.  To enable this,
     set <literal>include_realm</> to 0.  For simple single-realm
     installations, <literal>include_realm</> combined with the
     <literal>krb_realm</> parameter (which checks that the realm provided
-    matches exactly what is in the krb_realm parameter) would be a secure but
+    matches exactly what is in the <literal>krb_realm</literal> parameter) would be a secure but
     less capable option compared to specifying an explicit mapping in
     <filename>pg_ident.conf</>.
    </para>
@@ -1009,8 +1009,8 @@ omicron         bryanh                  guest1
         If set to 0, the realm name from the authenticated user principal is
         stripped off before being passed through the user name mapping
         (<xref linkend="auth-username-maps">). This is discouraged and is
-        primairly available for backwards compatibility as it is not secure
-        in multi-realm environments unless krb_realm is also used.  Users
+        primarily available for backwards compatibility as it is not secure
+        in multi-realm environments unless <literal>krb_realm</literal> is also used.  Users
         are recommended to leave include_realm set to the default (1) and to
         provide an explicit mapping in <filename>pg_ident.conf</>.
        </para>
@@ -1030,7 +1030,7 @@ omicron         bryanh                  guest1
         <literal>username/hostbased@EXAMPLE.COM</literal>, respectively),
         unless <literal>include_realm</literal> has been set to 0, in which case
         <literal>username</literal> (or <literal>username/hostbased</literal>)
-        is what is seen as the system username when mapping.
+        is what is seen as the system user name when mapping.
        </para>
       </listitem>
      </varlistentry>
@@ -1088,8 +1088,8 @@ omicron         bryanh                  guest1
         If set to 0, the realm name from the authenticated user principal is
         stripped off before being passed through the user name mapping
         (<xref linkend="auth-username-maps">). This is discouraged and is
-        primairly available for backwards compatibility as it is not secure
-        in multi-realm environments unless krb_realm is also used.  Users
+        primarily available for backwards compatibility as it is not secure
+        in multi-realm environments unless <literal>krb_realm</literal> is also used.  Users
         are recommended to leave include_realm set to the default (1) and to
         provide an explicit mapping in <filename>pg_ident.conf</>.
        </para>
@@ -1109,7 +1109,7 @@ omicron         bryanh                  guest1
         <literal>username/hostbased@EXAMPLE.COM</literal>, respectively),
         unless <literal>include_realm</literal> has been set to 0, in which case
         <literal>username</literal> (or <literal>username/hostbased</literal>)
-        is what is seen as the system username when mapping.
+        is what is seen as the system user name when mapping.
        </para>
       </listitem>
      </varlistentry>
@@ -1292,7 +1292,7 @@ omicron         bryanh                  guest1
     this search, the server disconnects and re-binds to the directory as
     this user, using the password specified by the client, to verify that the
     login is correct. This mode is the same as that used by LDAP authentication
-    schemes in other software, such as Apache mod_authnz_ldap and pam_ldap.
+    schemes in other software, such as Apache <literal>mod_authnz_ldap</literal> and <literal>pam_ldap</literal>.
     This method allows for significantly more flexibility
     in where the user objects are located in the directory, but will cause
     two separate connections to the LDAP server to be made.

doc/src/sgml/config.sgml

@@ -1902,7 +1902,7 @@ include_dir 'conf.d'
 
         <para>
          The default is 1 on supported systems, otherwise 0.  This value can
-         be overriden for tables in a particular tablespace by setting the
+         be overridden for tables in a particular tablespace by setting the
          tablespace parameter of the same name (see
          <xref linkend="sql-altertablespace">).
         </para>
@@ -1993,7 +1993,7 @@ include_dir 'conf.d'
        <para>
         In <literal>logical</> level, the same information is logged as
         with <literal>hot_standby</>, plus information needed to allow
-        extracting logical changesets from the WAL. Using a level of
+        extracting logical change sets from the WAL. Using a level of
         <literal>logical</> will increase the WAL volume, particularly if many
         tables are configured for <literal>REPLICA IDENTITY FULL</literal> and
         many <command>UPDATE</> and <command>DELETE</> statements are
@@ -3909,7 +3909,7 @@ local0.*    /var/log/postgresql
         listed in the Open Group's <ulink
         url="http://pubs.opengroup.org/onlinepubs/009695399/functions/strftime.html">strftime
         </ulink> specification.
-        Note that the system's <systemitem>strftime</systemitem> is not used
+        Note that the system's <function>strftime</function> is not used
         directly, so platform-specific (nonstandard) extensions do not work.
         The default is <literal>postgresql-%Y-%m-%d_%H%M%S.log</literal>.
        </para>

doc/src/sgml/custom-scan.sgml

@@ -70,7 +70,7 @@ typedef struct CustomPath
   <para>
     <structfield>path</> must be initialized as for any other path, including
     the row-count estimate, start and total cost, and sort ordering provided
-    by this path.  <structfield>flags</> is a bitmask, which should include
+    by this path.  <structfield>flags</> is a bit mask, which should include
     <literal>CUSTOMPATH_SUPPORT_BACKWARD_SCAN</> if the custom path can support
     a backward scan and <literal>CUSTOMPATH_SUPPORT_MARK_RESTORE</> if it
     can support mark and restore.  Both capabilities are optional.
@@ -163,7 +163,7 @@ typedef struct CustomScan
   <para>
     <structfield>scan</> must be initialized as for any other scan, including
     estimated costs, target lists, qualifications, and so on.
-    <structfield>flags</> is a bitmask with the same meaning as in
+    <structfield>flags</> is a bit mask with the same meaning as in
     <structname>CustomPath</>.
     <structfield>custom_plans</> can be used to store child
     <structname>Plan</> nodes.
@@ -174,12 +174,12 @@ typedef struct CustomScan
     that is only used by the custom scan provider itself.
     <structfield>custom_scan_tlist</> can be NIL when scanning a base
     relation, indicating that the custom scan returns scan tuples that match
-    the base relation's rowtype.  Otherwise it is a targetlist describing
+    the base relation's row type.  Otherwise it is a target list describing
     the actual scan tuples.  <structfield>custom_scan_tlist</> must be
     provided for joins, and could be provided for scans if the custom scan
     provider can compute some non-Var expressions.
     <structfield>custom_relids</> is set by the core code to the set of
-    relations (rangetable indexes) that this scan node handles; except when
+    relations (range table indexes) that this scan node handles; except when
     this scan is replacing a join, it will have only one member.
     <structfield>methods</> must point to a (usually statically allocated)
     object implementing the required custom scan methods, which are further
@@ -251,10 +251,10 @@ typedef struct CustomScanState
   </para>
 
   <para>
-   <structfield>ss</> is initialized as for any other scanstate,
+   <structfield>ss</> is initialized as for any other scan state,
    except that if the scan is for a join rather than a base relation,
    <literal>ss.ss_currentRelation</> is left NULL.
-   <structfield>flags</> is a bitmask with the same meaning as in
+   <structfield>flags</> is a bit mask with the same meaning as in
    <structname>CustomPath</> and <structname>CustomScan</>.
    <structfield>methods</> must point to a (usually statically allocated)
    object implementing the required custom scan state methods, which are

doc/src/sgml/ddl.sgml

@@ -545,7 +545,7 @@ CREATE TABLE products (
    </para>
 
    <para>
-    Adding a unique constraint will automatically create a unique btree
+    Adding a unique constraint will automatically create a unique B-tree
     index on the column or group of columns used in the constraint.
     A uniqueness constraint on only some rows can be enforced by creating
     a <link linkend="indexes-partial">partial index</link>.
@@ -630,7 +630,7 @@ CREATE TABLE example (
    </para>
 
    <para>
-    Adding a primary key will automatically create a unique btree index
+    Adding a primary key will automatically create a unique B-tree index
     on the column or group of columns used in the primary key.
    </para>
 
@@ -1559,7 +1559,7 @@ REVOKE ALL ON accounts FROM PUBLIC;
   <para>
    To specify which rows are visible and what rows can be added to the
    table with row level security, an expression is required which returns
-   a boolean result.  This expression will be evaluated for each row prior
+   a Boolean result.  This expression will be evaluated for each row prior
    to other conditionals or functions which are part of the query.  The
    one exception to this rule are <literal>leakproof</literal> functions,
    which are guaranteed to not leak information.  Two expressions may be
@@ -1676,7 +1676,7 @@ CREATE POLICY user_policy ON users
 
   <para>
    Below is a larger example of how this feature can be used in
-   production environments, based on a unix password file.
+   production environments, based on a Unix password file.
   </para>
 
 <programlisting>

doc/src/sgml/fdwhandler.sgml

@@ -239,7 +239,7 @@ IterateForeignScan (ForeignScanState *node);
 
     <para>
      The rows returned must match the <structfield>fdw_scan_tlist</> target
-     list if one was supplied, otherwise they must match the rowtype of the
+     list if one was supplied, otherwise they must match the row type of the
      foreign table being scanned.  If you choose to optimize away fetching
      columns that are not needed, you should insert nulls in those column
      positions, or else generate a <structfield>fdw_scan_tlist</> list with
@@ -333,7 +333,7 @@ GetForeignJoinPaths (PlannerInfo *root,
      remote join cannot be found from the system catalogs, the FDW must
      fill <structfield>fdw_scan_tlist</> with an appropriate list
      of <structfield>TargetEntry</> nodes, representing the set of columns
-     it will supply at runtime in the tuples it returns.
+     it will supply at run time in the tuples it returns.
     </para>
 
     <para>
@@ -752,7 +752,7 @@ RefetchForeignRow (EState *estate,
      for the row to be re-fetched.  Although the <literal>rowid</> value is
      passed as a <type>Datum</>, it can currently only be a <type>tid</>.  The
      function API is chosen in hopes that it may be possible to allow other
-     datatypes for row IDs in future.
+     data types for row IDs in future.
     </para>
 
     <para>
@@ -1140,8 +1140,8 @@ GetForeignServerByName(const char *name, bool missing_ok);
      is <structfield>fdw_scan_tlist</>, which describes the tuples returned by
      the FDW for this plan node.  For simple foreign table scans this can be
      set to <literal>NIL</>, implying that the returned tuples have the
-     rowtype declared for the foreign table.  A non-NIL value must be a
-     targetlist (list of <structname>TargetEntry</>s) containing Vars and/or
+     row type declared for the foreign table.  A non-<symbol>NIL</symbol> value must be a
+     target list (list of <structname>TargetEntry</>s) containing Vars and/or
      expressions representing the returned columns.  This might be used, for
      example, to show that the FDW has omitted some columns that it noticed
      won't be needed for the query.  Also, if the FDW can compute expressions

doc/src/sgml/func.sgml

@@ -10327,7 +10327,7 @@ table2-mapping
        <row>
         <entry><literal>||</literal></entry>
         <entry><type>jsonb</type></entry>
-        <entry>Concatentate two jsonb values into a new jsonb value</entry>
+        <entry>Concatenate two <type>jsonb</type> values into a new <type>jsonb</type> value</entry>
         <entry><literal>'["a", "b"]'::jsonb || '["c", "d"]'::jsonb</literal></entry>
        </row>
        <row>
@@ -10986,7 +10986,7 @@ table2-mapping
       If the argument to <literal>json_strip_nulls</> contains duplicate
       field names in any object, the result could be semantically somewhat
       different, depending on the order in which they occur. This is not an
-      issue for <literal>jsonb_strip_nulls</> since jsonb values never have
+      issue for <literal>jsonb_strip_nulls</> since <type>jsonb</type> values never have
       duplicate object field names.
     </para>
   </note>
@@ -13433,7 +13433,7 @@ SELECT xmlagg(x) FROM (SELECT x FROM test ORDER BY y DESC) AS tab;
        <type>integer</type>
       </entry>
       <entry>
-       Integer bitmask indicating which arguments are not being included in the current
+       Integer bit mask indicating which arguments are not being included in the current
        grouping set
       </entry>
      </row>
@@ -16633,7 +16633,7 @@ SELECT set_config('log_statement_stats', 'off', false);
         </entry>
        <entry><type>boolean</type></entry>
        <entry>Cancel a backend's current query.  This is also allowed if the
-        calling role is a member of the role whose backend is being cancelled,
+        calling role is a member of the role whose backend is being canceled,
         however only superusers can cancel superuser backends.
         </entry>
       </row>
@@ -18600,7 +18600,7 @@ CREATE EVENT TRIGGER test_event_trigger_for_drops
         <literal><function>pg_event_trigger_table_rewrite_oid()</function></literal>
        </entry>
        <entry><type>Oid</type></entry>
-       <entry>The Oid of the table about to be rewritten.</entry>
+       <entry>The OID of the table about to be rewritten.</entry>
       </row>
 
       <row>

doc/src/sgml/indices.sgml

@@ -343,7 +343,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
    BRIN can support many different indexing strategies,
    and the particular operators with which a BRIN index can be used
    vary depending on the indexing strategy.
-   For datatypes that have a linear sort order, the indexed data
+   For data types that have a linear sort order, the indexed data
    corresponds to the minimum and maximum values of the
    values in the column for each block range,
    which support indexed queries using these operators: