Fix a batch of speling misteaks identified by Peter's spell-checker tool.

4 files changed, 9 insertions, 9 deletions

diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml
index 089695b1bbc..dc4b2e776b9 100644
--- a/doc/src/sgml/ref/create_sequence.sgml
+++ b/doc/src/sgml/ref/create_sequence.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.35 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.36 2003/09/20 20:12:05 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -230,7 +230,7 @@ SELECT * FROM <replaceable>seqname</replaceable>;
   <para>
    Furthermore, although multiple sessions are guaranteed to allocate
    distinct sequence values, the values may be generated out of
-   sequence when all the sessions are considered.  FFor example, with
+   sequence when all the sessions are considered.  For example, with
    a <replaceable class="parameter">cache</replaceable> setting of 10,
    session A might reserve values 1..10 and return
    <function>nextval</function>=1, then session B might reserve values
diff --git a/doc/src/sgml/ref/ecpg-ref.sgml b/doc/src/sgml/ref/ecpg-ref.sgml
index fc4aeef337c..f47c33601b8 100644
--- a/doc/src/sgml/ref/ecpg-ref.sgml
+++ b/doc/src/sgml/ref/ecpg-ref.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.27 2003/08/31 17:32:23 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.28 2003/09/20 20:12:05 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -42,7 +42,7 @@ PostgreSQL documentation
   <para>
    <command>ecpg</command> will convert each input file given on the
    command line to the corresponding C output file.  Input files
-   preferrably have the extension <filename>.pgc</filename>, in which
+   preferably have the extension <filename>.pgc</filename>, in which
    case the extension will be replaced by <filename>.c</filename> to
    determine the output file name.  If the extension of the input file
    is not <filename>.pgc</filename>, then the output file name is
diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
index d0fb343bbd9..b2ad6310525 100644
--- a/doc/src/sgml/ref/grant.sgml
+++ b/doc/src/sgml/ref/grant.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.35 2003/09/11 21:42:20 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.36 2003/09/20 20:12:05 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -316,7 +316,7 @@ GRANT SELECT, UPDATE, INSERT ON mytable TO GROUP todos;
 
    <para>
    If the <quote>Access privileges</> column is empty for a given object,
-it means the object has default privileges (that is, its privileges columm
+it means the object has default privileges (that is, its privileges column
 is null).  Default privileges always include all privileges for the owner,
 and may include some privileges for <literal>PUBLIC</> depending on the
 object type, as explained above.  The first <command>GRANT</> or
diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml
index 60f0d66bfbc..7c9c9fc7f77 100644
--- a/doc/src/sgml/ref/notify.sgml
+++ b/doc/src/sgml/ref/notify.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.24 2003/09/15 03:21:51 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.25 2003/09/20 20:12:05 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -35,7 +35,7 @@ NOTIFY <replaceable class="PARAMETER">name</replaceable>
   </para>
 
   <para>
-   The information passed to the client for a notifiation event includes the notification
+   The information passed to the client for a notification event includes the notification
    name and the notifying session's server process <acronym>PID</>.  It is up to the
    database designer to define the notification names that will be used in a given
    database and what each one means.
@@ -111,7 +111,7 @@ NOTIFY <replaceable class="PARAMETER">name</replaceable>
    are the same, the notification event is one's own work bouncing
    back, and can be ignored.  (Despite what was said in the preceding
    paragraph, this is a safe technique.
-   <productname>PostgreSQL</productname> keeps self-notifiications
+   <productname>PostgreSQL</productname> keeps self-notifications
    separate from notifications arriving from other sessions, so you
    cannot miss an outside notification by ignoring your own
    notifications.)