Spelling fixes

doc/src/sgml/config.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.300 2010/07/24 12:16:20 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.301 2010/07/27 19:01:16 petere Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -2265,7 +2265,7 @@ SET ENABLE_SEQSCAN TO OFF;
        <para>
         Sets the planner's estimate of the cost of a disk page fetch
         that is part of a series of sequential fetches.  The default is 1.0.
-        This value can be overriden for a particular tablespace by setting
+        This value can be overridden for a particular tablespace by setting
         the tablespace parameter of the same name
         (see <xref linkend="sql-altertablespace">).
        </para>
@@ -2281,7 +2281,7 @@ SET ENABLE_SEQSCAN TO OFF;
        <para>
         Sets the planner's estimate of the cost of a
         non-sequentially-fetched disk page.  The default is 4.0.
-        This value can be overriden for a particular tablespace by setting
+        This value can be overridden for a particular tablespace by setting
         the tablespace parameter of the same name
         (see <xref linkend="sql-altertablespace">).
        </para>

doc/src/sgml/datatype.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.253 2010/07/24 16:46:57 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.254 2010/07/27 19:01:16 petere Exp $ -->
 
  <chapter id="datatype">
   <title>Data Types</title>
@@ -1256,7 +1256,7 @@ SELECT E'\\xDEADBEEF';
     represented as an ASCII character into special escape sequences.
     If, from the point of view of the application, representing bytes
     as characters makes sense, then this representation can be
-    convenient.  But in practice it is usually confusing becauses it
+    convenient.  But in practice it is usually confusing because it
     fuzzes up the distinction between binary strings and character
     strings, and also the particular escape mechanism that was chosen is
     somewhat unwieldy.  So this format should probably be avoided

doc/src/sgml/install-win32.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/install-win32.sgml,v 1.57 2010/03/17 17:12:31 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/install-win32.sgml,v 1.58 2010/07/27 19:01:16 petere Exp $ -->
 
 <chapter id="install-win32">
  <title>Installation from Source Code on <productname>Windows</productname></title>
@@ -19,7 +19,7 @@
  <para>
   There are several different ways of building PostgreSQL on
   <productname>Windows</productname>. The simplest way to build with
-  Microsoft tools is to intall a modern version of the
+  Microsoft tools is to install a modern version of the
   <productname>Microsoft Platform SDK</productname> and use use the included
   compiler. It is also possible to build with the full
   <productname>Microsoft Visual C++ 2005 or 2008</productname>. In some cases

doc/src/sgml/installation.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.348 2010/07/05 18:54:37 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.349 2010/07/27 19:01:16 petere Exp $ -->
 
 <chapter id="installation">
  <title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -2327,7 +2327,7 @@ hosts=local4,bind4
 -bash-3.00$ createlang plperl template1
 createlang: language installation failed: ERROR:  could not load library "/opt/dbs/pgsql748/lib/plperl.so": A memory address is not in the address space for the process.
 </screen>
-    Running as a non-owner in the group posessing the PostgreSQL
+    Running as a non-owner in the group possessing the PostgreSQL
     installation:
 <screen>
 -bash-3.00$ createlang plperl template1

doc/src/sgml/libpq.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.315 2010/07/18 11:37:25 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.316 2010/07/27 19:01:16 petere Exp $ -->
 
 <chapter id="libpq">
  <title><application>libpq</application> - C Library</title>
@@ -1766,7 +1766,7 @@ PGresult *PQexecParams(PGconn *conn,
             to be text strings.
            </para>
            <para>
-            Values passed in binary format require knowlege of
+            Values passed in binary format require knowledge of
             the internal representation expected by the backend.
             For example, integers must be passed in network byte
             order.  Passing <type>numeric</> values requires

doc/src/sgml/release-9.0.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/release-9.0.sgml,v 2.42 2010/07/12 18:30:36 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/release-9.0.sgml,v 2.43 2010/07/27 19:01:16 petere Exp $ -->
 
  <sect1 id="release-9-0">
   <title>Release 9.0</title>
@@ -685,7 +685,7 @@
     <title>Monitoring</title>
     <para>
      With increased use of PostgreSQL in high-end production systems,
-     users need increased monitoring.  PostgresSQL 9.0 continues to add
+     users need increased monitoring.  PostgreSQL 9.0 continues to add
      more ways to monitor PostgreSQL applications.
     </para>
 
@@ -744,7 +744,7 @@
        Add <link
        linkend="monitoring-stats-funcs-table"><function>pg_stat_reset_shared('bgwriter')</></link>
        to reset the cluster-wide shared statistics of the
-       bgwriter (Greg Smith)
+       background writer (Greg Smith)
       </para>
      </listitem>
 
@@ -753,7 +753,7 @@
        Add <link
        linkend="monitoring-stats-funcs-table"><function>pg_stat_reset_single_table_counters()</></link>
        and <function>pg_stat_reset_single_function_counters()</>
-       to allow the reseting of statistics counters for individual
+       to allow the resetting of statistics counters for individual
        tables and indexes (Magnus Hagander)
       </para>
      </listitem>

doc/src/sgml/wal.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.70 2010/07/16 11:35:40 heikki Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.71 2010/07/27 19:01:16 petere Exp $ -->
 
 <chapter id="wal">
  <title>Reliability and the Write-Ahead Log</title>
@@ -91,7 +91,7 @@
   <para>
    Many file systems that use write barriers (e.g.  <acronym>ZFS</>,
    <acronym>ext4</>) internally use <command>FLUSH CACHE EXT</> or
-   <command>SYNCHRONIZE CACHE</> commands to flush data to the platers on
+   <command>SYNCHRONIZE CACHE</> commands to flush data to the platters on
    write-back-enabled drives.  Unfortunately, such write barrier file
    systems behave suboptimally when combined with battery-backed unit
    (<acronym>BBU</>) disk controllers.  In such setups, the synchronize

doc/src/sgml/xml2.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/xml2.sgml,v 1.7 2009/05/18 11:08:24 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/xml2.sgml,v 1.8 2010/07/27 19:01:16 petere Exp $ -->
 
 <sect1 id="xml2">
  <title>xml2</title>
@@ -386,7 +386,7 @@ WHERE t.author_id = p.person_id;
    </synopsis>
 
    <para>
-    This function appplies the XSL stylesheet to the document and returns
+    This function applies the XSL stylesheet to the document and returns
     the transformed result. The paramlist is a list of parameter
     assignments to be used in the transformation, specified in the form
     <literal>a=1,b=2</>. Note that the