Fix some typos in the documentation. Patch from Brian Gough. Backport

the relevant fixes to 8.2 as well.

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 2ffe07458690655efcd1491c16b1373d28656578..507b4b6142c348dfc48d695b7c129fd29f916d3a 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.198 2007/04/21 17:26:17 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.199 2007/05/03 15:05:56 neilc Exp $ -->
 
  <chapter id="datatype">
   <title id="datatype-title">Data Types</title>
@@ -3376,7 +3376,7 @@ SET xmloption TO { DOCUMENT | CONTENT };
 
    <para>
     When using the binary mode to pass query parameters to the server
-    and query results back the the client, no character set conversion
+    and query results back to the client, no character set conversion
     is performed, so the situation is different.  In this case, an
     encoding declaration in the XML data will be observed, and if it
     is absent, the data will be assumed to be in UTF-8 (as required by

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 7f77eae4252f3a42b3858af70000ab1dec770357..b11b176fe34bb70a5afa9ab28499483854f4eef9 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.73 2007/02/01 00:28:16 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.74 2007/05/03 15:05:56 neilc Exp $ -->
 
 <chapter id="ddl">
  <title>Data Definition</title>
@@ -2233,7 +2233,7 @@ VALUES ('New York', NULL, NULL, 'NY');
 
     <listitem>
      <para>
-      When queries or updates access a large percentage of a a single
+      When queries or updates access a large percentage of a single
       partition, performance can be improved by taking advantage
       of sequential scan of that partition instead of using an
       index and random access reads scattered across the whole table.
@@ -2556,7 +2556,7 @@ DO INSTEAD
 </programlisting>
 
         Note that the <literal>WHERE</literal> clause in each rule
-        exactly matches the the <literal>CHECK</literal>
+        exactly matches the <literal>CHECK</literal>
         constraint for its partition.
        </para>
       </listitem>

diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml
index 8ba9362e4c562e77fc82b87f16b89d3c4f91138b..1be0ae5b8e50aef4b19218fb07b7c1e012a63dae 100644 (file)
--- a/doc/src/sgml/plperl.sgml
+++ b/doc/src/sgml/plperl.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.64 2007/02/16 03:50:29 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.65 2007/05/03 15:05:56 neilc Exp $ -->
 
  <chapter id="plperl">
   <title>PL/Perl - Perl Procedural Language</title>
@@ -20,7 +20,7 @@
   <para> The usual advantage to using PL/Perl is that this allows use,
    within stored functions, of the manyfold <quote>string
     munging</quote> operators and functions available for Perl.  Parsing
-   complex strings might be be easier using Perl than it is with the
+   complex strings might be easier using Perl than it is with the
    string functions and control structures provided in PL/pgSQL.</para>
   
   <para>
@@ -619,7 +619,7 @@ CREATE FUNCTION badfunc() RETURNS integer AS $$
 $$ LANGUAGE plperl;
 </programlisting>
     The creation of this function will fail as its use of a forbidden
-    operation will be be caught by the validator.
+    operation will be caught by the validator.
   </para>
 
   <para>

diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml
index 7ee47162cd74aaa1ca0370704487e4d8b8680284..aaec698bcf4407efc88b298f210c94d768c1dc10 100644 (file)
--- a/doc/src/sgml/spi.sgml
+++ b/doc/src/sgml/spi.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.56 2007/04/16 01:14:55 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.57 2007/05/03 15:05:56 neilc Exp $ -->
 
 <chapter id="spi">
  <title>Server Programming Interface</title>
@@ -2233,7 +2233,7 @@ char * SPI_getvalue(HeapTuple <parameter>row</parameter>, TupleDesc <parameter>r
    Column value, or <symbol>NULL</symbol> if the column is null,
    <parameter>colnumber</parameter> is out of range
    (<varname>SPI_result</varname> is set to
-   <symbol>SPI_ERROR_NOATTRIBUTE</symbol>), or no no output function
+   <symbol>SPI_ERROR_NOATTRIBUTE</symbol>), or no output function is
    available (<varname>SPI_result</varname> is set to
    <symbol>SPI_ERROR_NOOUTFUNC</symbol>).
   </para>