Documentation spell checking and markup improvements

Author: petere

doc/src/sgml/bloom.sgml

@@ -212,8 +212,8 @@ CREATE INDEX
 
   <para>
    An operator class for bloom indexes requires only a hash function for the
-   indexed datatype and an equality operator for searching. This example
-   shows the opclass definition for the <type>text</> data type:
+   indexed data type and an equality operator for searching. This example
+   shows the operator class definition for the <type>text</> data type:
   </para>
 
 <programlisting>

doc/src/sgml/brin.sgml

@@ -625,7 +625,7 @@ typedef struct BrinOpcInfo
  </table>
 
  <para>
-  To write an operator class for a complex datatype which has values
+  To write an operator class for a complex data type which has values
   included within another type, it's possible to use the inclusion support
   procedures alongside the corresponding operators, as shown
   in <xref linkend="brin-extensibility-inclusion-table">.  It requires
@@ -774,16 +774,16 @@ typedef struct BrinOpcInfo
     Support procedure numbers 1-10 are reserved for the BRIN internal
     functions, so the SQL level functions start with number 11.  Support
     function number 11 is the main function required to build the index.
-    It should accept two arguments with the same datatype as the opclass,
-    and return the union of them.  The inclusion opclass can store union
-    values with different datatypes if it is defined with the
+    It should accept two arguments with the same data type as the operator class,
+    and return the union of them.  The inclusion operator class can store union
+    values with different data types if it is defined with the
     <literal>STORAGE</> parameter.  The return value of the union
-    function should match the <literal>STORAGE</> datatype.
+    function should match the <literal>STORAGE</> data type.
  </para>
 
  <para>
     Support procedure numbers 12 and 14 are provided to support
-    irregularities of built-in datatypes.  Procedure number 12
+    irregularities of built-in data types.  Procedure number 12
     is used to support network addresses from different families which
     are not mergeable.  Procedure number 14 is used to support
     empty ranges.  Procedure number 13 is an optional but
@@ -794,17 +794,17 @@ typedef struct BrinOpcInfo
  </para>
 
  <para>
-    Both minmax and inclusion opclasses support cross-datatype
+    Both minmax and inclusion operator classes support cross-data-type
     operators, though with these the dependencies become more complicated.
-    The minmax opclass requires a full set of operators to be
-    defined with both arguments having the same datatype.  It allows
-    additional datatypes to be supported by defining extra sets
-    of operators.  Inclusion opclass operator strategies are dependent
+    The minmax operator class requires a full set of operators to be
+    defined with both arguments having the same data type.  It allows
+    additional data types to be supported by defining extra sets
+    of operators.  Inclusion operator class operator strategies are dependent
     on another operator strategy as shown in
     <xref linkend="brin-extensibility-inclusion-table">, or the same
     operator strategy as themselves.  They require the dependency
-    operator to be defined with the <literal>STORAGE</> datatype as the
-    left-hand-side argument and the other supported datatype to be the
+    operator to be defined with the <literal>STORAGE</> data type as the
+    left-hand-side argument and the other supported data type to be the
     right-hand-side argument of the supported operator.  See
     <literal>float4_minmax_ops</> as an example of minmax, and
     <literal>box_inclusion_ops</> as an example of inclusion.

doc/src/sgml/config.sgml

@@ -2006,7 +2006,7 @@ include_dir 'conf.d'
          <literal>Gather</literal> node.  Parallel workers are taken from the
          pool of processes established by
          <xref linkend="guc-max-worker-processes">.  Note that the requested
-         number of workers may not actually be available at runtime.  If this
+         number of workers may not actually be available at run time.  If this
          occurs, the plan will run with fewer workers than expected, which may
          be inefficient.  The default value is 2.  Setting this value to 0
          disables parallel query execution.

doc/src/sgml/ecpg.sgml

@@ -3782,7 +3782,7 @@ EXEC SQL GET DESCRIPTOR <replaceable>name</replaceable> VALUE <replaceable>num</
     keywords are different. A Descriptor Area can also be manually built to
     provide the input parameters for a query or a cursor and
     <literal>USING SQL DESCRIPTOR <replaceable>name</replaceable></literal>
-    is the way to pass the input parameters into a parametrized query. The statement
+    is the way to pass the input parameters into a parameterized query. The statement
     to build a named SQL Descriptor Area is below:
 <programlisting>
 EXEC SQL SET DESCRIPTOR <replaceable>name</replaceable> VALUE <replaceable>num</replaceable> <replaceable>field</replaceable> = :<replaceable>hostvar</replaceable>;
@@ -3917,7 +3917,7 @@ typedef struct sqlda_struct sqlda_t;
       <term><literal>sqln</></term>
       <listitem>
        <para>
-        It contains the number of input parameters for a parametrized query in
+        It contains the number of input parameters for a parameterized query in
         case it's passed into <command>OPEN</command>, <command>DECLARE</command> or
         <command>EXECUTE</command> statements using the <literal>USING</literal>
         keyword. In case it's used as output of <command>SELECT</command>,
@@ -8121,7 +8121,7 @@ if (*(int2 *)sqldata->sqlvar[i].sqlind != 0)
       <listitem>
        <para>
         Type of the NULL indicator data. It's always SQLSMINT when returning data from the server.
-        When the <literal>SQLDA</literal> is used for a parametrized query, the data is treated
+        When the <literal>SQLDA</literal> is used for a parameterized query, the data is treated
         according to the set type.
        </para>
       </listitem>

doc/src/sgml/func.sgml

@@ -17100,7 +17100,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
        </entry>
        <entry><type>record</type></entry>
        <entry>
-        Returns information about current controldata file state.
+        Returns information about current control file state.
        </entry>
       </row>
 
@@ -17148,97 +17148,97 @@ SELECT collation for ('foo' COLLATE "de_DE");
      <tbody>
 
       <row>
-       <entry>checkpoint_location</entry>
+       <entry><literal>checkpoint_location</literal></entry>
        <entry><type>pg_lsn</type></entry>
       </row>
 
       <row>
-       <entry>prior_location</entry>
+       <entry><literal>prior_location</literal></entry>
        <entry><type>pg_lsn</type></entry>
       </row>
 
       <row>
-       <entry>redo_location</entry>
+       <entry><literal>redo_location</literal></entry>
        <entry><type>pg_lsn</type></entry>
       </row>
 
       <row>
-       <entry>redo_wal_file</entry>
+       <entry><literal>redo_wal_file</literal></entry>
        <entry><type>text</type></entry>
       </row>
 
       <row>
-       <entry>timeline_id</entry>
+       <entry><literal>timeline_id</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>prev_timeline_id</entry>
+       <entry><literal>prev_timeline_id</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>full_page_writes</entry>
+       <entry><literal>full_page_writes</literal></entry>
        <entry><type>boolean</type></entry>
       </row>
 
       <row>
-       <entry>next_xid</entry>
+       <entry><literal>next_xid</literal></entry>
        <entry><type>text</type></entry>
       </row>
 
       <row>
-       <entry>next_oid</entry>
+       <entry><literal>next_oid</literal></entry>
        <entry><type>oid</type></entry>
       </row>
 
       <row>
-       <entry>next_multixact_id</entry>
+       <entry><literal>next_multixact_id</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>next_multi_offset</entry>
+       <entry><literal>next_multi_offset</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>oldest_xid</entry>
+       <entry><literal>oldest_xid</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>oldest_xid_dbid</entry>
+       <entry><literal>oldest_xid_dbid</literal></entry>
        <entry><type>oid</type></entry>
       </row>
 
       <row>
-       <entry>oldest_active_xid</entry>
+       <entry><literal>oldest_active_xid</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>oldest_multi_xid</entry>
+       <entry><literal>oldest_multi_xid</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>oldest_multi_dbid</entry>
+       <entry><literal>oldest_multi_dbid</literal></entry>
        <entry><type>oid</type></entry>
       </row>
 
       <row>
-       <entry>oldest_commit_ts_xid</entry>
+       <entry><literal>oldest_commit_ts_xid</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>newest_commit_ts_xid</entry>
+       <entry><literal>newest_commit_ts_xid</literal></entry>
        <entry><type>xid</type></entry>
       </row>
 
       <row>
-       <entry>checkpoint_time</entry>
+       <entry><literal>checkpoint_time</literal></entry>
        <entry><type>timestamp with time zone</type></entry>
       </row>
 
@@ -17264,22 +17264,22 @@ SELECT collation for ('foo' COLLATE "de_DE");
      <tbody>
 
       <row>
-       <entry>pg_control_version</entry>
+       <entry><literal>pg_control_version</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>catalog_version_no</entry>
+       <entry><literal>catalog_version_no</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>system_identifier</entry>
+       <entry><literal>system_identifier</literal></entry>
        <entry><type>bigint</type></entry>
       </row>
 
       <row>
-       <entry>pg_control_last_modified</entry>
+       <entry><literal>pg_control_last_modified</literal></entry>
        <entry><type>timestamp with time zone</type></entry>
       </row>
 
@@ -17305,67 +17305,67 @@ SELECT collation for ('foo' COLLATE "de_DE");
      <tbody>
 
       <row>
-       <entry>max_data_alignment</entry>
+       <entry><literal>max_data_alignment</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>database_block_size</entry>
+       <entry><literal>database_block_size</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>blocks_per_segment</entry>
+       <entry><literal>blocks_per_segment</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>wal_block_size</entry>
+       <entry><literal>wal_block_size</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>bytes_per_wal_segment</entry>
+       <entry><literal>bytes_per_wal_segment</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>max_identifier_length</entry>
+       <entry><literal>max_identifier_length</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>max_index_columns</entry>
+       <entry><literal>max_index_columns</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>max_toast_chunk_size</entry>
+       <entry><literal>max_toast_chunk_size</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>large_object_chunk_size</entry>
+       <entry><literal>large_object_chunk_size</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>bigint_timestamps</entry>
+       <entry><literal>bigint_timestamps</literal></entry>
        <entry><type>boolean</type></entry>
       </row>
 
       <row>
-       <entry>float4_pass_by_value</entry>
+       <entry><literal>float4_pass_by_value</literal></entry>
        <entry><type>boolean</type></entry>
       </row>
 
       <row>
-       <entry>float8_pass_by_value</entry>
+       <entry><literal>float8_pass_by_value</literal></entry>
        <entry><type>boolean</type></entry>
       </row>
 
       <row>
-       <entry>data_page_checksum_version</entry>
+       <entry><literal>data_page_checksum_version</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
@@ -17391,27 +17391,27 @@ SELECT collation for ('foo' COLLATE "de_DE");
      <tbody>
 
       <row>
-       <entry>min_recovery_end_location</entry>
+       <entry><literal>min_recovery_end_location</literal></entry>
        <entry><type>pg_lsn</type></entry>
       </row>
 
       <row>
-       <entry>min_recovery_end_timeline</entry>
+       <entry><literal>min_recovery_end_timeline</literal></entry>
        <entry><type>integer</type></entry>
       </row>
 
       <row>
-       <entry>backup_start_location</entry>
+       <entry><literal>backup_start_location</literal></entry>
        <entry><type>pg_lsn</type></entry>
       </row>
 
       <row>
-       <entry>backup_end_location</entry>
+       <entry><literal>backup_end_location</literal></entry>
        <entry><type>pg_lsn</type></entry>
       </row>
 
       <row>
-       <entry>end_of_backup_record_required</entry>
+       <entry><literal>end_of_backup_record_required</literal></entry>
        <entry><type>boolean</type></entry>
       </row>
 

doc/src/sgml/high-availability.sgml

@@ -1046,7 +1046,7 @@ primary_slot_name = 'node_a_slot'
     servers.  Waiting for confirmation increases the user's confidence that the
     changes will not be lost in the event of server crashes but it also
     necessarily increases the response time for the requesting transaction.
-    The minimum wait time is the roundtrip time between primary to standby.
+    The minimum wait time is the round-trip time between primary to standby.
    </para>
 
    <para>

doc/src/sgml/indices.sgml

@@ -1315,7 +1315,7 @@ SELECT target FROM tests WHERE subject = 'some-subject' AND success;
    But there's a problem: the <literal>WHERE</> clause refers
    to <literal>success</> which is not available as a result column of the
    index.  Nonetheless, an index-only scan is possible because the plan does
-   not need to recheck that part of the <literal>WHERE</> clause at runtime:
+   not need to recheck that part of the <literal>WHERE</> clause at run time:
    all entries found in the index necessarily have <literal>success = true</>
    so this need not be explicitly checked in the
    plan.  <productname>PostgreSQL</> versions 9.6 and later will recognize