doc: Spell checking

Author: petere

doc/src/sgml/bgworker.sgml

@@ -69,7 +69,7 @@ typedef struct BackgroundWorker
   </para>
 
   <para>
-   <structfield>bgw_flags</> is a bitwise-or'd bitmask indicating the
+   <structfield>bgw_flags</> is a bitwise-or'd bit mask indicating the
    capabilities that the module wants.  Possible values are
    <literal>BGWORKER_SHMEM_ACCESS</literal> (requesting shared memory access)
    and <literal>BGWORKER_BACKEND_DATABASE_CONNECTION</literal> (requesting the
@@ -114,14 +114,14 @@ typedef struct BackgroundWorker
    passed at registration time. <structfield>bgw_main</structfield> may be
    NULL; in that case, <structfield>bgw_library_name</structfield> and
    <structfield>bgw_function_name</structfield> will be used to determine
-   the entrypoint.  This is useful for background workers launched after
+   the entry point.  This is useful for background workers launched after
    postmaster startup, where the postmaster does not have the requisite
    library loaded.
   </para>
 
   <para>
    <structfield>bgw_library_name</structfield> is the name of a library in
-   which the initial entrypoint for the background worker should be sought.
+   which the initial entry point for the background worker should be sought.
    It is ignored unless <structfield>bgw_main</structfield> is NULL.
    But if <structfield>bgw_main</structfield> is NULL, then the named library
    will be dynamically loaded by the worker process and
@@ -131,7 +131,7 @@ typedef struct BackgroundWorker
 
   <para>
    <structfield>bgw_function_name</structfield> is the name of a function in
-   a dynamically loaded library which should be used as the initial entrypoint
+   a dynamically loaded library which should be used as the initial entry point
    for a new background worker.  It is ignored unless
    <structfield>bgw_main</structfield> is NULL.
   </para>

doc/src/sgml/catalogs.sgml

@@ -408,13 +408,13 @@
       <entry><structfield>aggfinalextra</structfield></entry>
       <entry><type>bool</type></entry>
       <entry></entry>
-      <entry>True to pass extra dummy arguments to aggfinalfn</entry>
+      <entry>True to pass extra dummy arguments to <structfield>aggfinalfn</structfield></entry>
      </row>
      <row>
       <entry><structfield>aggmfinalextra</structfield></entry>
       <entry><type>bool</type></entry>
       <entry></entry>
-      <entry>True to pass extra dummy arguments to aggmfinalfn</entry>
+      <entry>True to pass extra dummy arguments to <structfield>aggmfinalfn</structfield></entry>
      </row>
      <row>
       <entry><structfield>aggsortop</structfield></entry>
@@ -838,7 +838,7 @@
       <entry><structfield>amopsortfamily</structfield></entry>
       <entry><type>oid</type></entry>
       <entry><literal><link linkend="catalog-pg-opfamily"><structname>pg_opfamily</structname></link>.oid</literal></entry>
-      <entry>The btree operator family this entry sorts according to, if an
+      <entry>The B-tree operator family this entry sorts according to, if an
        ordering operator; zero if a search operator</entry>
      </row>
 
@@ -853,7 +853,7 @@
    <replaceable>indexed_column</>
    <replaceable>operator</>
    <replaceable>constant</>.
-   Obviously, such an operator must return boolean, and its left-hand input
+   Obviously, such an operator must return <type>boolean</type>, and its left-hand input
    type must match the index's column data type.
   </para>
 
@@ -868,13 +868,13 @@
    its left-hand input type must match the index's column data type.
    The exact semantics of the <literal>ORDER BY</> are specified by the
    <structfield>amopsortfamily</structfield> column, which must reference
-   a btree operator family for the operator's result type.
+   a B-tree operator family for the operator's result type.
   </para>
 
   <note>
    <para>
     At present, it's assumed that the sort order for an ordering operator
-    is the default for the referenced opfamily, i.e., <literal>ASC NULLS
+    is the default for the referenced operator family, i.e., <literal>ASC NULLS
     LAST</>.  This might someday be relaxed by adding additional columns
     to specify sort options explicitly.
    </para>
@@ -974,7 +974,7 @@
    these match the input data type(s) of the support procedure itself, for
    others not.  There is a notion of <quote>default</> support procedures for
    an index, which are those with <structfield>amproclefttype</> and
-   <structfield>amprocrighttype</> both equal to the index opclass's
+   <structfield>amprocrighttype</> both equal to the index operator class's
    <structfield>opcintype</>.
   </para>
 
@@ -1959,7 +1959,7 @@
        <literal>d</> = default (primary key, if any),
        <literal>n</> = nothing,
        <literal>f</> = all columns
-       <literal>i</> = index with indisreplident set, or default
+       <literal>i</> = index with <structfield>indisreplident</structfield> set, or default
       </entry>
      </row>
 
@@ -5261,7 +5261,7 @@
       <entry><structfield>plugin</structfield></entry>
       <entry><type>name</type></entry>
       <entry></entry>
-      <entry>The basename of the shared object containing the output plugin this logical slot is using, or null for physical slots.</entry>
+      <entry>The base name of the shared object containing the output plugin this logical slot is using, or null for physical slots.</entry>
      </row>
 
      <row>
@@ -5275,7 +5275,7 @@
       <entry><structfield>datoid</structfield></entry>
       <entry><type>oid</type></entry>
       <entry><literal><link linkend="catalog-pg-database"><structname>pg_database</structname></link>.oid</literal></entry>
-      <entry>The oid of the database this slot is associated with, or
+      <entry>The OID of the database this slot is associated with, or
       null. Only logical slots have an associated database.</entry>
      </row>
 

doc/src/sgml/config.sgml

@@ -2603,7 +2603,7 @@ include_dir 'conf.d'
        <para>
         The name of a standby server for this purpose is the
         <varname>application_name</> setting of the standby, as set in the
-        <varname>primary_conninfo</> of the standby's walreceiver.  There is
+        <varname>primary_conninfo</> of the standby's WAL receiver.  There is
         no mechanism to enforce uniqueness. In case of duplicates one of the
         matching standbys will be chosen to be the synchronous standby, though
         exactly which one is indeterminate.

doc/src/sgml/datatype.sgml

@@ -4487,7 +4487,7 @@ SELECT * FROM pg_attribute
    <para>
     The <type>pg_lsn</type> data type can be used to store LSN (Log Sequence
     Number) data which is a pointer to a location in the XLOG. This type is a
-    representation of XLogRecPtr and an internal system type of
+    representation of <type>XLogRecPtr</type> and an internal system type of
     <productname>PostgreSQL</productname>.
    </para>
 

doc/src/sgml/fdwhandler.sgml

@@ -353,7 +353,7 @@ PlanForeignModify (PlannerInfo *root,
      <literal>plan</> is the <structname>ModifyTable</> plan node, which is
      complete except for the <structfield>fdwPrivLists</> field.
      <literal>resultRelation</> identifies the target foreign table by its
-     rangetable index.  <literal>subplan_index</> identifies which target of
+     range table index.  <literal>subplan_index</> identifies which target of
      the <structname>ModifyTable</> plan node this is, counting from zero;
      use this if you want to index into <literal>plan-&gt;plans</> or other
      substructure of the <literal>plan</> node.
@@ -430,7 +430,7 @@ ExecForeignInsert (EState *estate,
      <literal>rinfo</> is the <structname>ResultRelInfo</> struct describing
      the target foreign table.
      <literal>slot</> contains the tuple to be inserted; it will match the
-     rowtype definition of the foreign table.
+     row-type definition of the foreign table.
      <literal>planSlot</> contains the tuple that was generated by the
      <structname>ModifyTable</> plan node's subplan; it differs from
      <literal>slot</> in possibly containing additional <quote>junk</>
@@ -476,7 +476,7 @@ ExecForeignUpdate (EState *estate,
      <literal>rinfo</> is the <structname>ResultRelInfo</> struct describing
      the target foreign table.
      <literal>slot</> contains the new data for the tuple; it will match the
-     rowtype definition of the foreign table.
+     row-type definition of the foreign table.
      <literal>planSlot</> contains the tuple that was generated by the
      <structname>ModifyTable</> plan node's subplan; it differs from
      <literal>slot</> in possibly containing additional <quote>junk</>
@@ -576,7 +576,7 @@ IsForeignRelUpdatable (Relation rel);
 </programlisting>
 
      Report which update operations the specified foreign table supports.
-     The return value should be a bitmask of rule event numbers indicating
+     The return value should be a bit mask of rule event numbers indicating
      which operations are supported by the foreign table, using the
      <literal>CmdType</> enumeration; that is,
      <literal>(1 << CMD_UPDATE) = 4</> for <command>UPDATE</>,

doc/src/sgml/func.sgml

@@ -10086,7 +10086,7 @@ table2-mapping
 
    <para>
    <xref linkend="functions-json-op-table"> shows the operators that
-   are available for use with the two JSON datatypes (see <xref
+   are available for use with the two JSON data types (see <xref
    linkend="datatype-json">).
   </para>
 
@@ -10162,7 +10162,7 @@ table2-mapping
    The standard comparison operators shown in  <xref
    linkend="functions-comparison-table"> are available for
    <type>jsonb</type>, but not for <type>json</type>. They follow the
-   ordering rules for btree operations outlined at <xref
+   ordering rules for B-tree operations outlined at <xref
    linkend="json-indexing">.
   </para>
   <para>
@@ -10269,7 +10269,7 @@ table2-mapping
          (recursively) to arrays and objects; otherwise, if there is a cast
          from the type to <type>json</type>, the cast function will be used to
          perform the conversion; otherwise, a JSON scalar value is produced.
-         For any scalar type other than a number, a boolean, or a null value,
+         For any scalar type other than a number, a Boolean, or a null value,
          the text representation will be used, properly quoted and escaped
          so that it is a valid JSON string.
        </entry>
@@ -14007,7 +14007,7 @@ AND
    These operators compare the internal binary representation of the two
    rows.  Two rows might have a different binary representation even
    though comparisons of the two rows with the equality operator is true.
-   The ordering of rows under these comparision operators is deterministic
+   The ordering of rows under these comparison operators is deterministic
    but not otherwise meaningful.  These operators are used internally for
    materialized views and might be useful for other specialized purposes
    such as replication but are not intended to be generally useful for
@@ -15461,32 +15461,32 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
       <row>
        <entry><literal><function>to_regclass(<parameter>rel_name</parameter>)</function></literal></entry>
        <entry><type>regclass</type></entry>
-       <entry>get the oid of the named relation</entry>
+       <entry>get the OID of the named relation</entry>
       </row>
       <row>
        <entry><literal><function>to_regproc(<parameter>func_name</parameter>)</function></literal></entry>
        <entry><type>regproc</type></entry>
-       <entry>get the oid of the named function</entry>
+       <entry>get the OID of the named function</entry>
       </row>
       <row>
        <entry><literal><function>to_regprocedure(<parameter>func_name</parameter>)</function></literal></entry>
        <entry><type>regprocedure</type></entry>
-       <entry>get the oid of the named function</entry>
+       <entry>get the OID of the named function</entry>
       </row>
       <row>
        <entry><literal><function>to_regoper(<parameter>operator_name</parameter>)</function></literal></entry>
        <entry><type>regoper</type></entry>
-       <entry>get the oid of the named operator</entry>
+       <entry>get the OID of the named operator</entry>
       </row>
       <row>
        <entry><literal><function>to_regoperator(<parameter>operator_name</parameter>)</function></literal></entry>
        <entry><type>regoperator</type></entry>
-       <entry>get the oid of the named operator</entry>
+       <entry>get the OID of the named operator</entry>
       </row>
       <row>
        <entry><literal><function>to_regtype(<parameter>type_name</parameter>)</function></literal></entry>
        <entry><type>regtype</type></entry>
-       <entry>get the oid of the named type</entry>
+       <entry>get the OID of the named type</entry>
       </row>
      </tbody>
     </tgroup>
@@ -16619,8 +16619,8 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
        <entry>
         Creates a new physical replication slot named
         <parameter>slot_name</parameter>. Streaming changes from a physical slot
-        is only possible with the walsender protocol - see <xref
-        linkend="protocol-replication">. Corresponds to the walsender protocol
+        is only possible with the streaming-replication protocol - see <xref
+        linkend="protocol-replication">. Corresponds to the replication protocol
         command <literal>CREATE_REPLICATION_SLOT ... PHYSICAL</literal>.
        </entry>
       </row>
@@ -16636,7 +16636,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
        </entry>
        <entry>
         Drops the physical or logical replication slot
-        named <parameter>slot_name</parameter>. Same as walsender protocol
+        named <parameter>slot_name</parameter>. Same as replication protocol
         command <literal>DROP_REPLICATION_SLOT</>.
        </entry>
       </row>

doc/src/sgml/high-availability.sgml

@@ -1894,7 +1894,7 @@ if (!triggered)
     might want to make adjustments to handle the period when
     <varname>hot_standby_feedback</> feedback is not being provided.
     For example, consider increasing <varname>max_standby_archive_delay</>
-    so that queries are not rapidly cancelled by conflicts in WAL archive
+    so that queries are not rapidly canceled by conflicts in WAL archive
     files during disconnected periods.  You should also consider increasing
     <varname>max_standby_streaming_delay</> to avoid rapid cancellations
     by newly-arrived streaming WAL entries after reconnection.

doc/src/sgml/indexam.sgml

@@ -168,7 +168,7 @@ ambuild (Relation heapRelation,
 void
 ambuildempty (Relation indexRelation);
 </programlisting>
-   Build an empty index, and write it to the initialization fork (INIT_FORKNUM)
+   Build an empty index, and write it to the initialization fork (<symbol>INIT_FORKNUM</symbol>)
    of the given relation.  This method is called only for unlogged tables; the
    empty index written to the initialization fork will be copied over the main
    relation fork on each server restart.
@@ -278,7 +278,7 @@ amcanreturn (Relation indexRelation);
 </programlisting>
    Check whether the index can support <firstterm>index-only scans</> by
    returning the indexed column values for an index entry in the form of an
-   IndexTuple.  Return TRUE if so, else FALSE.  If the index AM can never
+   <structname>IndexTuple</structname>.  Return TRUE if so, else FALSE.  If the index AM can never
    support index-only scans (an example is hash, which stores only
    the hash values not the original data), it is sufficient to set its
    <structfield>amcanreturn</> field to zero in <structname>pg_am</>.

doc/src/sgml/json.sgml

@@ -354,7 +354,7 @@ SELECT '"foo"'::jsonb ? 'foo';
     keys or key/value pairs occurring within a large number of
     <type>jsonb</> documents (datums).
     Two GIN <quote>operator classes</> are provided, offering different
-    performance and flexibility tradeoffs.
+    performance and flexibility trade-offs.
   </para>
   <para>
     The default GIN operator class for <type>jsonb</> supports queries with

doc/src/sgml/libpq.sgml

@@ -136,7 +136,7 @@ PGconn *PQconnectdbParams(const char * const *keywords,
       </para>
 
       <para>
-       If  any  parameter is NULL or an emptry string, the corresponding
+       If  any  parameter is <symbol>NULL</symbol> or an emptry string, the corresponding
        environment variable (see <xref linkend="libpq-envars">) is checked.
        If the  environment  variable is not set either, then the indicated
        built-in defaults are used.