Spellchecking run, final cleanups

doc/src/sgml/ref/create_aggregate.sgml

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.32 2005/04/12 04:26:15 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.33 2005/11/04 23:14:02 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -143,11 +143,11 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1;
 </programlisting>
    Further assumptions are that the aggregate ignores null inputs, and that
    it delivers a null result if and only if there were no non-null inputs.
-   Ordinarily, a datatype's <literal>&lt;</> operator is the proper sort
+   Ordinarily, a data type's <literal>&lt;</> operator is the proper sort
    operator for <function>MIN</>, and <literal>&gt;</> is the proper sort
    operator for <function>MAX</>.  Note that the optimization will never
-   actually take effect unless the specified operator is the LessThan or
-   GreaterThan strategy member of a btree index opclass.
+   actually take effect unless the specified operator is the <quote>less than</quote> or
+   <quote>greater than</quote> strategy member of a B-tree index operator class.
   </para>
  </refsect1>
 
@@ -243,7 +243,7 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1;
       The associated sort operator for a <function>MIN</>- or
       <function>MAX</>-like aggregate.
       This is just an operator name (possibly schema-qualified).
-      The operator is assumed to have the same input datatypes as
+      The operator is assumed to have the same input data types as
       the aggregate.
      </para>
     </listitem>

doc/src/sgml/ref/create_domain.sgml

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.25 2005/11/01 21:09:50 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.26 2005/11/04 23:14:02 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -58,7 +58,7 @@ where <replaceable class="PARAMETER">constraint</replaceable> is:
   <caution>
   <para>
    At present, declaring a function result value as a domain 
-   is pretty dangerous, because none of the PLs enforce domain constraints 
+   is pretty dangerous, because none of the procedural languages enforce domain constraints 
    on their results.  You'll need to make sure that the function code itself
    respects the constraints.  In <application>PL/pgSQL</>, one possible
    workaround is to explicitly cast the result value to the domain type

doc/src/sgml/ref/pg_ctl-ref.sgml

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.31 2005/02/21 02:13:26 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.32 2005/11/04 23:14:02 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -308,7 +308,7 @@ PostgreSQL documentation
      <term><option>-U <replaceable class="parameter">username</replaceable></option></term>
      <listitem>
       <para>
-       Username for the user to start the service. For domain users, use the
+       User name for the user to start the service. For domain users, use the
        format <literal>DOMAIN\username</literal>.
       </para>
      </listitem>

doc/src/sgml/ref/pg_resetxlog.sgml

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_resetxlog.sgml,v 1.11 2005/06/08 15:50:21 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_resetxlog.sgml,v 1.12 2005/11/04 23:14:02 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -61,7 +61,7 @@ PostgreSQL documentation
    by specifying the <literal>-f</> (force) switch.  In this case plausible
    values will be substituted for the missing data.  Most of the fields can be
    expected to match, but manual assistance may be needed for the next OID,
-   next transaction ID, next multi-transaction ID and offset,
+   next transaction ID, next multitransaction ID and offset,
    WAL starting address, and database locale fields.
    The first five of these can be set using the switches discussed below.
    <command>pg_resetxlog</command>'s own environment is the source for its
@@ -78,8 +78,8 @@ PostgreSQL documentation
   <para>
    The <literal>-o</>, <literal>-x</>, <literal>-m</>, <literal>-O</>,
    and <literal>-l</>
-   switches allow the next OID, next transaction ID, next multi-transaction
-   ID, next multi-transaction offset, and WAL starting address values to
+   switches allow the next OID, next transaction ID, next multitransaction
+   ID, next multitransaction offset, and WAL starting address values to
    be set manually.  These are only needed when
    <command>pg_resetxlog</command> is unable to determine appropriate values
    by reading <filename>pg_control</>.  Safe values may be determined as
@@ -102,7 +102,7 @@ PostgreSQL documentation
 
     <listitem>
      <para>
-      A safe value for the next multi-transaction ID (<literal>-m</>)
+      A safe value for the next multitransaction ID (<literal>-m</>)
       may be determined by looking for the numerically largest
       file name in the directory <filename>pg_multixact/offsets</> under the
       data directory, adding one, and then multiplying by 65536.  As above,
@@ -113,7 +113,7 @@ PostgreSQL documentation
 
     <listitem>
      <para>
-      A safe value for the next multi-transaction offset (<literal>-O</>)
+      A safe value for the next multitransaction offset (<literal>-O</>)
       may be determined by looking for the numerically largest
       file name in the directory <filename>pg_multixact/members</> under the
       data directory, adding one, and then multiplying by 65536.  As above,

doc/src/sgml/ref/psql-ref.sgml

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.153 2005/11/01 21:09:50 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.154 2005/11/04 23:14:02 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -2015,7 +2015,7 @@ bar
         <term><varname>HISTFILE</varname></term>
         <listitem>
         <para>
-        The filename that will be used to store the history list. The default
+        The file name that will be used to store the history list. The default
         value is <filename>~/.psql_history</filename>.  For example, putting
 <programlisting>
 \set HISTFILE ~/.psql_history- :DBNAME