Spell checking and markup refinement

doc/src/sgml/ref/alter_opfamily.sgml

@@ -159,7 +159,7 @@ ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="
     <term><replaceable class="parameter">sort_family_name</replaceable></term>
     <listitem>
      <para>
-      The name (optionally schema-qualified) of an existing btree operator
+      The name (optionally schema-qualified) of an existing <literal>btree</literal> operator
       family that describes the sort ordering associated with an ordering
       operator.
      </para>

doc/src/sgml/ref/cluster.sgml

@@ -128,7 +128,7 @@ CLUSTER [VERBOSE]
    </para>
 
    <para>
-    <command>CLUSTER</> can re-sort the table using either an indexscan
+    <command>CLUSTER</> can re-sort the table using either an index scan
     on the specified index, or (if the index is a b-tree) a sequential
     scan followed by sorting.  It will attempt to choose the method that
     will be faster, based on planner cost parameters and available statistical
@@ -136,7 +136,7 @@ CLUSTER [VERBOSE]
    </para>
 
    <para>
-    When an indexscan is used, a temporary copy of the table is created that
+    When an index scan is used, a temporary copy of the table is created that
     contains the table data in the index order.  Temporary copies of each
     index on the table are created as well.  Therefore, you need free space on
     disk at least equal to the sum of the table size and the index sizes.
@@ -146,7 +146,7 @@ CLUSTER [VERBOSE]
     When a sequential scan and sort is used, a temporary sort file is
     also created, so that the peak temporary space requirement is as much
     as double the table size, plus the index sizes.  This method is often
-    faster than the indexscan method, but if the disk space requirement is
+    faster than the index scan method, but if the disk space requirement is
     intolerable, you can disable this choice by temporarily setting <xref
     linkend="guc-enable-sort"> to <literal>off</>.
    </para>

doc/src/sgml/ref/create_opclass.sgml

@@ -184,7 +184,7 @@ CREATE OPERATOR CLASS <replaceable class="parameter">name</replaceable> [ DEFAUL
     <term><replaceable class="parameter">sort_family_name</replaceable></term>
     <listitem>
      <para>
-      The name (optionally schema-qualified) of an existing btree operator
+      The name (optionally schema-qualified) of an existing <literal>btree</literal> operator
       family that describes the sort ordering associated with an ordering
       operator.
      </para>

doc/src/sgml/ref/create_type.sgml

@@ -355,7 +355,7 @@ CREATE TYPE <replaceable class="parameter">name</replaceable>
   </para>
 
   <para>
-   If the optional boolean
+   If the optional Boolean
    parameter <replaceable class="parameter">collatable</replaceable>
    is true, column definitions and expressions of the type may carry
    collation information through use of

doc/src/sgml/ref/ecpg-ref.sgml

@@ -143,7 +143,7 @@ PostgreSQL documentation
          <listitem>
          <para>
          Do not use indicators but instead use special values to represent
-         NULLs. Historically there have been databases using this approach.
+         null values. Historically there have been databases using this approach.
          </para>
          </listitem>
         </varlistentry>
@@ -152,7 +152,7 @@ PostgreSQL documentation
          <listitem>
          <para>
          Prepare all statements before using them. Libecpg will keep a cache of
-         prepared statments and reuse a statement if it gets executed again. If the
+         prepared statements and reuse a statement if it gets executed again. If the
          cache runs full, libecpg will free the least used statement.
          </para>
          </listitem>
@@ -161,7 +161,7 @@ PostgreSQL documentation
          <term><option>questionmarks</option></term>
          <listitem>
          <para>
-         Allow questionmark as placeholder for compatibility reasons. 
+         Allow question mark as placeholder for compatibility reasons.
          This used to be the default long ago.
          </para>
          </listitem>

doc/src/sgml/ref/pg_basebackup.sgml

@@ -59,7 +59,7 @@ PostgreSQL documentation
   </para>
 
   <para>
-   There can be multiple pg_basebackups running at the same time, but it is
+   There can be multiple <command>pg_basebackup</command>s running at the same time, but it is
    better from a performance point of view to take only one backup, and copy
    the result.
   </para>
@@ -127,7 +127,7 @@ PostgreSQL documentation
             Write the output as tar files in the target directory. The main
             data directory will be written to a file named
             <filename>base.tar</filename>, and all other tablespaces will
-            be named after the tablespace oid.
+            be named after the tablespace OID.
             </para>
            <para>
             If the value <literal>-</literal> (dash) is specified as
@@ -235,7 +235,7 @@ PostgreSQL documentation
       <listitem>
        <para>
         Enables verbose mode. Will output some extra steps during startup and
-        shutdown, as well as show the exact filename that is currently being
+        shutdown, as well as show the exact file name that is currently being
         processed if progress reporting is also enabled.
        </para>
       </listitem>

doc/src/sgml/ref/pg_dump.sgml

@@ -142,7 +142,7 @@ PostgreSQL documentation
       <listitem>
        <para>
         Output commands to clean (drop)
-        database objects prior to outputing the commands for creating them.
+        database objects prior to outputting the commands for creating them.
         (Restore might generate some harmless errors.)
        </para>