Fix a few more double words in docs.

doc/src/sgml/external-projects.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.15 2007/01/31 20:56:17 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.16 2007/05/03 15:47:48 alvherre Exp $ -->
 
  <appendix id="external-projects">
   <title>External Projects</title>
@@ -31,7 +31,7 @@
     currently closed to new projects in favor of PgFoundry, it still
     contains many active and relevant projects. Other popular
     <productname>PostgreSQL</productname>-related projects are hosted
-    independently, or on other project-hosting sites such such as <ulink
+    independently, or on other project-hosting sites such as <ulink
     url="http://sourceforge.net/">SourceForge.net</ulink>. You should search
     the web if you don't find the project you are looking for.
    </para>

doc/src/sgml/maintenance.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.72 2007/04/18 20:44:53 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.73 2007/05/03 15:47:48 alvherre Exp $ -->
 
 <chapter id="maintenance">
  <title>Routine Database Maintenance Tasks</title>
@@ -490,7 +490,7 @@ HINT:  Stop the postmaster and use a standalone backend to VACUUM in "mydb".
 
    <para>
     There is a limit of <xref linkend="guc-autovacuum-max-workers"> worker
-    processes that may be running at at any time, so if the <command>VACUUM</>
+    processes that may be running at any time, so if the <command>VACUUM</>
     and <command>ANALYZE</> work to do takes too long to run, the deadline may
     be failed to meet for other databases.  Also, if a particular database
     takes long to process, more than one worker may be processing it

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

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.190 2007/03/26 17:23:37 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.191 2007/05/03 15:47:48 alvherre Exp $
 PostgreSQL documentation
 -->
 
@@ -114,7 +114,7 @@ PostgreSQL documentation
        argument on the command line.
       </para>
       <para>
-       If this parameter contains an <symbol>=</symbol> sign, it it treated as a
+       If this parameter contains an <symbol>=</symbol> sign, it is treated as a
        <parameter>conninfo</parameter> string. See <xref linkend="libpq-connect"> for more information.
       </para>
       </listitem>

doc/src/sgml/release.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.502 2007/04/20 03:27:23 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.503 2007/05/03 15:47:48 alvherre Exp $ -->
 <!--
 
 Typical markup:
@@ -16463,7 +16463,7 @@ Fix for SELECT timespan('21:11:26'::time) (Tom)
 netmask('x.x.x.x/0') is 255.255.255.255 instead of 0.0.0.0 (Oleg Sharoiko)
 Add btree index on NUMERIC (Jan)
 Perl fix for large objects containing NUL characters (Douglas Thomson)
-ODBC fix for for large objects (free)
+ODBC fix for large objects (free)
 Fix indexing of cidr data type
 Fix for Ethernet MAC addresses (macaddr type) comparisons
 Fix for date/time types when overflows happened in computations (Tom)
@@ -19056,7 +19056,7 @@ more compliant to the SQL-92 standard):
 
         "WITH GRANT OPTION" is not supported.  Only class owners can change
         access control
-   - The default access control is to to grant users readonly access.
+   - The default access control is to grant users readonly access.
      You must explicitly grant insert/update access to users.  To change
      this, modify the line in
                 src/backend/utils/acl.h