Spellchecking and such

Author: petere

doc/src/sgml/backup.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.90 2006/10/12 19:38:08 neilc Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.91 2006/10/23 18:10:30 petere Exp $ -->
 
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -977,7 +977,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
     If recovery fails for an external reason, such as a system crash or
     the WAL archive has become inaccessible, then the recovery can be
     simply restarted and it will restart almost from where it failed.
-    Restartable recovery works by writing a restartpoint record to the control
+    Restartable recovery works by writing a restart-point record to the control
     file at the first safely usable checkpoint record found after 
     <varname>checkpoint_timeout</> seconds. 
    </para>
@@ -1188,7 +1188,7 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"'  # Windows
 
    <para>
     If we take a backup of the server files whilst a recovery is in progress,
-    we will be able to restart the recovery from the last restartpoint. 
+    we will be able to restart the recovery from the last restart point. 
     That backup now has many of the changes from previous WAL archive files,
     so this version is now an updated version of the original base backup.
     If we need to recover, it will be faster to recover from the 
@@ -1595,7 +1595,7 @@ if (!triggered)
 
    <para>
     An external program can call <function>pg_xlogfile_name_offset()</>
-    to find out the filename and the exact byte offset within it of
+    to find out the file name and the exact byte offset within it of
     the latest WAL pointer.  If the external program regularly polls
     the server it can find out how far forward the pointer has
     moved. It can then access the WAL file directly and copy those

doc/src/sgml/catalogs.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/catalogs.sgml,v 2.134 2006/09/22 23:20:13 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/catalogs.sgml,v 2.135 2006/10/23 18:10:30 petere Exp $ -->
 <!--
  Documentation of the system catalogs, directed toward PostgreSQL developers
  -->
@@ -405,7 +405,7 @@
       <entry><structfield>amclusterable</structfield></entry>
       <entry><type>bool</type></entry>
       <entry></entry>
-      <entry>Can an index of this type be CLUSTERed on?</entry>
+      <entry>Can an index of this type be clustered on?</entry>
      </row>
 
      <row>
@@ -496,7 +496,7 @@
       <entry><structfield>amoptions</structfield></entry>
       <entry><type>regproc</type></entry>
       <entry><literal><link linkend="catalog-pg-proc"><structname>pg_proc</structname></link>.oid</literal></entry>
-      <entry>Function to parse and validate reloptions for an index</entry>
+      <entry>Function to parse and validate <structfield>reloptions</> for an index</entry>
      </row>
 
     </tbody>
@@ -1209,7 +1209,7 @@
       <entry><structfield>vac_scale_factor</structfield></entry>
       <entry><type>float4</type></entry>
       <entry></entry>
-      <entry>Multiplier for reltuples to add to
+      <entry>Multiplier for <structfield>reltuples</> to add to
        <structfield>vac_base_thresh</></entry>
      </row>
 
@@ -1224,7 +1224,7 @@
       <entry><structfield>anl_scale_factor</structfield></entry>
       <entry><type>float4</type></entry>
       <entry></entry>
-      <entry>Multiplier for reltuples to add to
+      <entry>Multiplier for <structfield>reltuples</> to add to
        <structfield>anl_base_thresh</></entry>
      </row>
 
@@ -2043,7 +2043,7 @@
        operation.  All rows inserted or deleted by transaction IDs before this one
        have been marked as known good or deleted.  This
        is used to determine when commit-log space can be recycled.
-       If InvalidTransactionId, then the minimum is unknown and can be
+       If <symbol>InvalidTransactionId</symbol>, then the minimum is unknown and can be
        determined by scanning <structname>pg_class</>.<structfield>relvacuumxid</>.
       </entry>
      </row>
@@ -2058,7 +2058,7 @@
        relabeled with a permanent (<quote>frozen</>) transaction ID in this
        database.  This is useful to check whether a database must be
        vacuumed soon to avoid transaction ID wrap-around problems.
-       If InvalidTransactionId, then the minimum is unknown and can be
+       If <symbol>InvalidTransactionId</symbol>, then the minimum is unknown and can be
        determined by scanning <structname>pg_class</>.<structfield>relminxid</>.
       </entry>
      </row>
@@ -3353,7 +3353,7 @@
       <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
       <entry>
        An array with the data types of the function arguments.  This includes
-       only input arguments (including INOUT arguments), and thus represents
+       only input arguments (including <literal>INOUT</literal> arguments), and thus represents
        the call signature of the function.
       </entry>
      </row>
@@ -3364,7 +3364,7 @@
       <entry><literal><link linkend="catalog-pg-type"><structname>pg_type</structname></link>.oid</literal></entry>
       <entry>
        An array with the data types of the function arguments.  This includes
-       all arguments (including OUT and INOUT arguments); however, if all the
+       all arguments (including <literal>OUT</literal> and <literal>INOUT</literal> arguments); however, if all the
        arguments are IN arguments, this field will be null.
        Note that subscripting is 1-based, whereas for historical reasons
        <structfield>proargtypes</> is subscripted from 0.
@@ -3377,10 +3377,10 @@
       <entry></entry>
       <entry>
         An array with the modes of the function arguments, encoded as
-        <literal>i</literal> for IN arguments,
-        <literal>o</literal> for OUT arguments,
-        <literal>b</literal> for INOUT arguments.
-        If all the arguments are IN arguments, this field will be null.
+        <literal>i</literal> for <literal>IN</> arguments,
+        <literal>o</literal> for <literal>OUT</> arguments,
+        <literal>b</literal> for <literal>INOUT</> arguments.
+        If all the arguments are <literal>IN</literal> arguments, this field will be null.
         Note that subscripts correspond to positions of
         <structfield>proallargtypes</> not <structfield>proargtypes</>.
       </entry>
@@ -5031,7 +5031,7 @@
 
   <para>
    Advisory locks can be acquired on keys consisting of either a single
-   bigint value or two integer values.  A bigint key is displayed with its
+   <type>bigint</type> value or two integer values.  A <type>bigint</type> key is displayed with its
    high-order half in the <structfield>classid</> column, its low-order half
    in the <structfield>objid</> column, and <structfield>objsubid</> equal
    to 1.  Integer keys are displayed with the first key in the

doc/src/sgml/client-auth.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.93 2006/09/16 00:30:11 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.94 2006/10/23 18:10:30 petere Exp $ -->
 
 <chapter id="client-authentication">
  <title>Client Authentication</title>
@@ -947,9 +947,9 @@ ldap://ldap.example.net/dc=example,dc=net;EXAMPLE\
    </para>
    <para>
     The server will bind to the distinguished name specified as
-    <replaceable>base dn</> using the username supplied by the client.
+    <replaceable>base dn</> using the user name supplied by the client.
     If <replaceable>prefix</> and <replaceable>suffix</> is 
-    specified, it will be prepended and appended to the username
+    specified, it will be prepended and appended to the user name
     before the bind. Typically, the prefix parameter is used to specify
     <replaceable>cn=</>, or <replaceable>DOMAIN\</> in an Active
     Directory environment.

doc/src/sgml/config.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.91 2006/10/19 22:55:25 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.92 2006/10/23 18:10:30 petere Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -75,7 +75,7 @@ shared_buffers = 128MB
 <programlisting>
 include 'filename'
 </programlisting>
-    If the filename is not an absolute path, it is taken as relative to
+    If the file name is not an absolute path, it is taken as relative to
     the directory containing the referencing configuration file.
     Inclusions can be nested.
    </para>
@@ -206,7 +206,7 @@ SET ENABLE_SEQSCAN TO OFF;
        <para>
          Specifies the main server configuration file
          (customarily called <filename>postgresql.conf</>).
-         This parameter can only be set on the postgres command line.
+         This parameter can only be set on the <command>postgres</command> command line.
        </para>
       </listitem>
      </varlistentry>
@@ -265,7 +265,7 @@ SET ENABLE_SEQSCAN TO OFF;
 
      <para>
       If you wish to keep the configuration files elsewhere than the
-      data directory, the postgres <option>-D</option>
+      data directory, the <command>postgres</command> <option>-D</option>
       command-line option or <envar>PGDATA</envar> environment variable
       must point to the directory containing the configuration files,
       and the <varname>data_directory</> parameter must be set in
@@ -1422,8 +1422,8 @@ SET ENABLE_SEQSCAN TO OFF;
         or power failure. The risks are similar to turning off
         <varname>fsync</>, though smaller.  It may be safe to turn off
         this parameter if you have hardware (such as a battery-backed disk
-        controller) or filesystem software (e.g., Reiser4) that reduces
-        the risk of partial page writes to an acceptably low level.
+        controller) or file-system software that reduces
+        the risk of partial page writes to an acceptably low level (e.g., ReiserFS 4).
        </para>
 
        <para>
@@ -3901,18 +3901,18 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
       <listitem>
        <para>
         This controls whether the array input parser recognizes
-        unquoted <literal>NULL</> as specifying a NULL array element.
+        unquoted <literal>NULL</> as specifying a null array element.
         By default, this is <literal>on</>, allowing array values containing
-        NULLs to be entered.  However, <productname>PostgreSQL</> versions
-        before 8.2 did not support NULLs in arrays, and therefore would
+        null values to be entered.  However, <productname>PostgreSQL</> versions
+        before 8.2 did not support null values in arrays, and therefore would
         treat <literal>NULL</> as specifying a normal array element with
         the string value <quote>NULL</>.  For backwards compatibility with
         applications that require the old behavior, this variable can be
         turned <literal>off</>.
        </para>
 
        <para>
-        Note that it is possible to create array values containing NULLs
+        Note that it is possible to create array values containing null values
         even when this variable is <literal>off</>.
        </para>
       </listitem>

doc/src/sgml/cvs.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/cvs.sgml,v 1.37 2006/03/10 19:10:47 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/cvs.sgml,v 1.38 2006/10/23 18:10:30 petere Exp $ -->
 
 <appendix id="cvs">
  <appendixinfo>
@@ -91,7 +91,7 @@ cvs -z3 -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot co -P pgsql
       <para>
        If you have a fast link to the Internet, you may not need
        <option>-z3</option>, which instructs
-       <productname>CVS</productname> to use gzip compression for transferred data.  But
+       <productname>CVS</productname> to use <command>gzip</command> compression for transferred data.  But
        on a modem-speed link, it's a very substantial win.
       </para>
      </note>
@@ -131,8 +131,8 @@ cvs -z3
 update -d -P
 </programlisting>
 
-     This supplies the <option>-z3</option> option to all cvs commands, and the
-     <option>-d</option> and <option>-P</option> options to cvs update.  Then you just have
+     This supplies the <option>-z3</option> option to all <command>cvs</> commands, and the
+     <option>-d</option> and <option>-P</option> options to <command>cvs update</>.  Then you just have
      to say
 <programlisting>
 cvs update
@@ -206,7 +206,7 @@ cvs checkout -r REL6_4 tc
 
   <para>
    When you tag more than one file with the same tag you can think
-   about the tag as <quote>a curve drawn through a matrix of filename vs.
+   about the tag as <quote>a curve drawn through a matrix of file name vs.
    revision number</quote>.  Say we have 5 files with the following revisions:
 
    <programlisting>
@@ -304,7 +304,7 @@ cvs commit
    A major advantage to using
    <productname>CVSup</productname> is that it can reliably
    replicate the <emphasis>entire</emphasis> CVS repository on your local system,
-   allowing fast local access to cvs operations such as <option>log</option>
+   allowing fast local access to <command>cvs</> operations such as <option>log</option>
    and <option>diff</option>. Other advantages include fast synchronization to
    the <productname>PostgreSQL</productname> server due to an efficient
    streaming transfer protocol which only sends the changes since the last update.
@@ -445,7 +445,7 @@ CVSROOT/loginfo*
    </para>
 
    <para>
-    The following is a suggested <productname>CVSup</productname> config file from
+    The following is a suggested <productname>CVSup</productname> configuration file from
     the <productname>PostgreSQL</>
     <ulink url="ftp://ftp.postgresql.org/pub/CVSup/README.cvsup">
     ftp site</ulink>
@@ -570,7 +570,7 @@ mv cvsup.1 ../doc/man/man1/
       <step>
        <para>
 	If there is a directory structure in the tar file, then unpack
-	the tar file within /usr/local/src and move the binaries into
+	the tar file within <filename>/usr/local/src</filename> and move the binaries into
 	the appropriate location as above.
        </para>
       </step>
@@ -645,7 +645,7 @@ $ which cvsup
 
       <step>
        <para>
-	Install the Modula-3 rpms:
+	Install the Modula-3 RPMs:
 
 <programlisting>
 # rpm -Uvh pm3*.rpm

doc/src/sgml/datatype.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.179 2006/10/18 16:43:13 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.180 2006/10/23 18:10:30 petere Exp $ -->
 
  <chapter id="datatype">
   <title id="datatype-title">Data Types</title>
@@ -3362,7 +3362,7 @@ SELECT * FROM pg_attribute
    </indexterm>
 
    <para>
-    <acronym>XML</> (eXtensible Markup Language) support is not one
+    <acronym>XML</> (Extensible Markup Language) support is not one
     capability, but a variety of features supported by a database
     system. These capabilities include storage, import/export,
     validation, indexing, efficiency of modification, searching,
@@ -3429,7 +3429,7 @@ SELECT * FROM pg_attribute
       indexes to index specific <acronym>XML</> fields. To index the
       full contents of <acronym>XML</> documents, the full-text indexing
       tool <filename>/contrib/tsearch2</> can be used. Of course,
-      tsearch2 indexes have no <acronym>XML</> awareness so additional
+      Tsearch2 indexes have no <acronym>XML</> awareness so additional
       <filename>/contrib/xml2</> checks should be added to queries.
      </para>
     </listitem>
@@ -3466,7 +3466,7 @@ SELECT * FROM pg_attribute
     <listitem>
 
      <para>
-      <filename>/contrib/xml2</> supports <acronym>XSLT</> (XML
+      <filename>/contrib/xml2</> supports <acronym>XSLT</> (Extensible
       Stylesheet Language Transformation).
      </para>
     </listitem>

doc/src/sgml/ddl.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.66 2006/10/22 03:03:40 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.67 2006/10/23 18:10:30 petere Exp $ -->
 
 <chapter id="ddl">
  <title>Data Definition</title>
@@ -2586,7 +2586,7 @@ UNION ALL SELECT * FROM measurement_y2006m01;
 
     However, the need to
     recreate the view adds an extra step to adding and dropping
-    individual partitions of the dataset.
+    individual partitions of the data set.
    </para>
    </sect2>
 
@@ -2778,15 +2778,15 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2006-01-01';
       Constraint exclusion only works when the query's <literal>WHERE</>
       clause contains constants.  A parameterized query will not be
       optimized, since the planner cannot know what partitions the
-      parameter value might select at runtime.  For the same reason,
+      parameter value might select at run time.  For the same reason,
       <quote>stable</> functions such as <function>CURRENT_DATE</function>
       must be avoided.
      </para>
     </listitem>
 
     <listitem>
      <para>
-      Avoid cross-datatype comparisons in the <literal>CHECK</>
+      Avoid cross-data type comparisons in the <literal>CHECK</>
       constraints, as the planner will currently fail to prove such
       conditions false.  For example, the following constraint
       will work if <varname>x</varname> is an <type>integer</type>
@@ -2802,7 +2802,7 @@ CHECK ( x = 1::bigint )
       The problem is not limited to the <type>bigint</type> data type
       &mdash; it can occur whenever the default data type of the
       constant does not match the data type of the column to which it
-      is being compared.  Cross-datatype comparisons in the supplied
+      is being compared.  Cross-data type comparisons in the supplied
       queries are usually OK, just not in the <literal>CHECK</> conditions.
      </para>
     </listitem>

doc/src/sgml/docguide.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.58 2006/10/23 14:13:43 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.59 2006/10/23 18:10:30 petere Exp $ -->
 
 <appendix id="docguide">
  <title>Documentation</title>
@@ -290,7 +290,7 @@ make install
         <envar>SGML_CATALOG_FILES</envar> to point to the file
         whenever you use <application>jade</application> later on.
         (This method is also an option if OpenJade is already
-        installed and you want to install the rest of the toolchain
+        installed and you want to install the rest of the tool chain
         locally.)
        </para>
       </step>