diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml
index 24acb96f1e81fdc985dfd74b2f40335ea8c50b85..5f40d81e0a89c527f45c25d5fb0c7a425ef86641 100644
--- a/doc/src/sgml/datetime.sgml
+++ b/doc/src/sgml/datetime.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.35 2003/09/11 16:22:42 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.36 2003/09/20 20:12:04 tgl Exp $
-->
<appendix id="datetime-appendix">
@@ -570,7 +570,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.35 2003/09/11 16:22:42 mo
<row>
<entry>AFT</entry>
<entry>+04:30</entry>
- <entry>Afganistan Time</entry>
+ <entry>Afghanistan Time</entry>
</row>
<row>
<entry>EAST</entry>
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index d9856c6d55e9500c5695569180aa57579b23af1b..14dda019a62d840c0f09437240166356edd625d2 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.51 2003/09/11 21:42:19 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.52 2003/09/20 20:12:04 tgl Exp $
-->
<chapter id="ecpg">
@@ -992,7 +992,7 @@ EXEC SQL WHENEVER SQLERROR STOP;
different action was set for the same condition between the first
<literal>EXEC SQL WHENEVER</literal> and the SQL statement causing
the condition, regardless of the flow of control in the C program.
- So neither of the two following C program exerpts will have the
+ So neither of the two following C program excerpts will have the
desired effect.
<programlisting>
/*
@@ -1072,7 +1072,7 @@ struct
If no error occurred in the last <acronym>SQL</acronym> statement,
<literal>sqlca.sqlcode</literal> will be 0 and
<literal>sqlca.sqlstate</literal> will be
- <literal>"00000"</literal>. If a warning or error occured, then
+ <literal>"00000"</literal>. If a warning or error occurred, then
<literal>sqlca.sqlcode</literal> will be negative and
<literal>sqlca.sqlstate</literal> will be different from
<literal>"00000"</literal>. A positive
diff --git a/doc/src/sgml/features.sgml b/doc/src/sgml/features.sgml
index 4056d770f187a511ddcfe3cbb7973b922f8038a1..09e0896020258b1fb0749c1f66ed70e8b450cd84 100644
--- a/doc/src/sgml/features.sgml
+++ b/doc/src/sgml/features.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.19 2003/09/11 21:42:19 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.20 2003/09/20 20:12:04 tgl Exp $
-->
<appendix id="features">
@@ -17,12 +17,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.19 2003/09/11 21:42:19 mo
The formal name of the SQL standard is ISO/IEC 9075 <quote>Database
Language SQL</quote>. A revised version of the standard is released
from time to time; the most recent one appearing in 1999. That
- version is refered to as ISO/IEC 9075:1999, or informally as SQL99.
+ version is referred to as ISO/IEC 9075:1999, or informally as SQL99.
The version prior to that was SQL92.
<productname>PostgreSQL</productname> development tends to aim for
conformance with the latest official version of the standard where
such conformance does not contradict traditional features or common
- sense. At the time of this writing, ballotting is under way for a
+ sense. At the time of this writing, balloting is under way for a
new revision of the standard, which, if approved, will eventually
become the conformance target for future
<productname>PostgreSQL</productname> development.
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 463e3c7a21e03d544dc31e54ef0989ad29368739..b97f9f7979946484201ebb0ec194cfbc36529419 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.174 2003/09/13 00:19:43 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.175 2003/09/20 20:12:04 tgl Exp $
PostgreSQL documentation
-->
@@ -469,7 +469,7 @@ PostgreSQL documentation
<row>
<entry> <literal><<</literal> </entry>
- <entry>biwise shift left</entry>
+ <entry>bitwise shift left</entry>
<entry><literal>1 << 4</literal></entry>
<entry><literal>16</literal></entry>
</row>
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 87afdbb2109458b1deab105dda51c3811e531991..c4b619e4e594c4604be460fb97f78acc65a679c3 100644
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/information_schema.sgml,v 1.8 2003/09/11 23:15:51 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/information_schema.sgml,v 1.9 2003/09/20 20:12:05 tgl Exp $ -->
<chapter id="information-schema">
<title>The Information Schema</title>
@@ -330,7 +330,7 @@
<literal>SELECT</literal>, <literal>INSERT</literal>,
<literal>UPDATE</literal>, <literal>REFERENCES</literal>. If you
want to make your applications fit for possible future
- developements, it is generally the right choice to use this view
+ developments, it is generally the right choice to use this view
instead of <literal>table_privileges</literal> if one of those
privilege types is concerned.
</para>
@@ -1508,7 +1508,7 @@ ORDER BY c.ordinal_position;
<entry><literal>object_type</literal</entry>
<entry><type>character_data</type></entry>
<entry>
- The type of the object that uses the array being descibed: one
+ The type of the object that uses the array being described: one
of <literal>TABLE</literal> (the array is used by a column of
that table), <literal>DOMAIN</literal> (the array is used by
that domain), <literal>ROUTINE</literal> (the array is used by
@@ -2424,7 +2424,7 @@ ORDER BY c.ordinal_position;
objects to a group that the current user is a member of. In
<productname>PostgreSQL</productname>, this currently only applies
to domains, and since domains do not have real privileges in
- <productname>PostgreSQL</productname>, this view is empty. Futher
+ <productname>PostgreSQL</productname>, this view is empty. Further
information can be found under <literal>usage_privileges</literal>.
In the future, this view may contain more useful information.
</para>
diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml
index ec79565fefa1d8e20e4e71e7b574cb7e0b3e226c..bff52a9668b1ae11acc218fc602b50b8dc641f58 100644
--- a/doc/src/sgml/jdbc.sgml
+++ b/doc/src/sgml/jdbc.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.48 2003/08/31 17:32:19 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.49 2003/09/20 20:12:05 tgl Exp $
-->
<chapter id="jdbc">
@@ -262,7 +262,7 @@ jdbc:postgresql://<replaceable class="parameter">host</replaceable>:<replaceable
</listitem>
</itemizedlist>
- The parametes have the following meanings:
+ The parameters have the following meanings:
<variablelist>
<varlistentry>
@@ -397,7 +397,7 @@ st.close();
<title>Getting results based on a cursor</title>
<para>By default the driver collects all the results for the
- query at once. This can be inconvieniant for large data sets so
+ query at once. This can be inconvenient for large data sets so
the JDBC driver provides a means of basing
a <classname>ResultSet</classname> on a database cursor and
only fetching a small number of rows.</para>
@@ -631,7 +631,7 @@ upperProc.close();
as <classname>ResultSet</classname> values.</para>
<example id="get-refcursor-from-function-call">
- <title>Gettig <type>refcursor</type> values from a
+ <title>Getting <type>refcursor</type> values from a
function</title>
<para>When calling a function that returns
@@ -741,7 +741,7 @@ st.close();
that contains a Large Object reference does not delete the Large Object.
Deleting the Large Object is a separate operation that needs to
be performed. Large Objects also have some security
- issues since anyone connected to the database cann view
+ issues since anyone connected to the database can view
and/or modify any Large Object, even if they don't have
permissions to view/update the row containing the Large Object reference.
</para>
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 7d91fdf808afddf55985d931878d24b70f50b4f2..cd2a8f491ff3a6734512fd150ea5ea47059f8d15 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.136 2003/09/11 21:42:20 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.137 2003/09/20 20:12:05 tgl Exp $
-->
<chapter id="libpq">
@@ -1945,7 +1945,7 @@ It is not thread-safe.
<para>
<function>PQescapeString</function> escapes a string for use within an SQL
-commmand. This is useful when inserting data values as literal constants
+command. This is useful when inserting data values as literal constants
in SQL commands. Certain characters (such as quotes and backslashes) must
be escaped to prevent them from being interpreted specially by the SQL parser.
<function>PQescapeString</> performs this operation.
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index b74d03804c5a7e83939a7df731f17d72696dbec8..edc9b1c267c6371fdf6a6ee204ad1e93ecee3910 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v 2.37 2003/09/12 22:17:23 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v 2.38 2003/09/20 20:12:05 tgl Exp $
-->
<chapter id="mvcc">
@@ -661,7 +661,7 @@ ERROR: could not serialize access due to concurrent update
</indexterm>
<para>
- The use of explicit locking can increase the likelyhood of
+ The use of explicit locking can increase the likelihood of
<firstterm>deadlocks</>, wherein two (or more) transactions each
hold locks that the other wants. For example, if transaction 1
acquires an exclusive lock on table A and then tries to acquire
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 1819a33c07ae8ef3f55f408b368d2fb460d0ea2f..ba41fda7932efeea65d00bcebc6d0ed3b059cfd0 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.44 2003/09/11 21:42:20 momjian Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.45 2003/09/20 20:12:05 tgl Exp $ -->
<chapter id="protocol">
<title>Frontend/Backend Protocol</title>
@@ -238,7 +238,7 @@
<para>
The authentication cycle ends with the server either rejecting the
- connection attempt (ErrorResponse), or sending AuthenticationOK.
+ connection attempt (ErrorResponse), or sending AuthenticationOk.
</para>
<para>
@@ -729,7 +729,7 @@
<command>BEGIN</>/<command>COMMIT</> transaction block (<quote>close</>
meaning to commit if no error, or roll back if error). Then a
ReadyForQuery response is issued. The purpose of Sync is to provide
- a resychronization point for error recovery. When an error is detected
+ a resynchronization point for error recovery. When an error is detected
while processing any extended-query message, the backend issues
ErrorResponse, then reads and discards messages until a Sync is reached,
then issues ReadyForQuery and returns to normal message processing.
diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml
index 089695b1bbc7edcfacc8b4041c9af6b94753fda2..dc4b2e776b912e7917ca9851783de7d3dd4e7fc1 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 fc4aeef337cb63c5b3e00f50d39df90a5474153d..f47c33601b8b063ce5d513d3fd6a8c35a1e03727 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 d0fb343bbd94793f85b327ecd53568284cb4151f..b2ad6310525f0dc9f9038ae8ac40fba3b0442a94 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 60f0d66bfbc2b3ffe79baffe179cdc9873602722..7c9c9fc7f77aadafbf17a3b3255f16d199dba159 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.)
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index c67e93ba8d8357cc27448e7002f91ee43ad47a86..0414f81e2a45b7dd8d6a35b68ecfc1bc9c63321a 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.207 2003/09/11 21:42:20 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.208 2003/09/20 20:12:05 tgl Exp $
-->
<appendix id="release">
@@ -782,7 +782,7 @@ Properly escape jdbc setObject() strings to improve security (Barry)
<listitem><para>Add locale variables (Peter)</para></listitem>
<listitem><para>Escape byes >= 0x7f for multibyte in PQescapeBytea/PQunescapeBytea (Tatsuo)</para></listitem>
<listitem><para>Add locale awareness to regular expression character classes</para></listitem>
-<listitem><para>Enable multibyte support by default (Tatso)</para></listitem>
+<listitem><para>Enable multibyte support by default (Tatsuo)</para></listitem>
<listitem><para>Add GB18030 multibyte support (Bill Huang)</para></listitem>
<listitem><para>Add CREATE/DROP CONVERSION, allowing loadable encodings (Tatsuo, Kaori)</para></listitem>
<listitem><para>Add pg_conversion table (Tatsuo)</para></listitem>
@@ -1058,7 +1058,7 @@ Properly escape jdbc setObject() strings to improve security (Barry)
<listitem><para>Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)</para></listitem>
<listitem><para>Fix for compressed transaction log id wraparound (Tom)</para></listitem>
<listitem><para>Fix PQescapeBytea/PQunescapeBytea so that they handle bytes > 0x7f (Tatsuo)</para></listitem>
-<listitem><para>Fix for psql and pg_dump crashing when invoked with non-existand long options (Tatsuo)</para></listitem>
+<listitem><para>Fix for psql and pg_dump crashing when invoked with non-existent long options (Tatsuo)</para></listitem>
<listitem><para>Fix crash when invoking geometric operators (Tom)</para></listitem>
<listitem><para>Allow OPEN cursor(args) (Tom)</para></listitem>
<listitem><para>Fix for rtree_gist index build (Teodor)</para></listitem>
@@ -1066,7 +1066,7 @@ Properly escape jdbc setObject() strings to improve security (Barry)
<listitem><para>contrib/intarray fixes (Oleg)</para></listitem>
<listitem><para>Fix for complex UNION/EXCEPT/INTERSECT queries using parens (Tom)</para></listitem>
<listitem><para>Fix to pg_convert (Tatsuo)</para></listitem>
-<listitem><para>Fix for crash with long DATA strings (Thomes, Neil)</para></listitem>
+<listitem><para>Fix for crash with long DATA strings (Thomas, Neil)</para></listitem>
<listitem><para>Fix for repeat(), lpad(), rpad() and long strings (Neil)</para></listitem>
</itemizedlist>
</sect2>
@@ -1099,7 +1099,7 @@ Properly escape jdbc setObject() strings to improve security (Barry)
<itemizedlist>
<listitem><para>Ensure that sequence counters do not go backwards after a crash (Tom)</para></listitem>
-<listitem><para>Fix pgaccess kanji-coversion key binding (Tatsuo)</para></listitem>
+<listitem><para>Fix pgaccess kanji-conversion key binding (Tatsuo)</para></listitem>
<listitem><para>Optimizer improvements (Tom)</para></listitem>
<listitem><para>Cash I/O improvements (Tom)</para></listitem>
<listitem><para>New Russian FAQ</para></listitem>
@@ -1447,7 +1447,7 @@ Properly escape jdbc setObject() strings to improve security (Barry)
<listitem><para>New TIMESTAMP WITHOUT TIMEZONE data type (Thomas)</para></listitem>
<listitem><para>Add ISO date/time specification with "T", yyyy-mm-ddThh:mm:ss (Thomas)</para></listitem>
<listitem><para>New xid/int comparison functions (Hiroshi)</para></listitem>
-<listitem><para>Add precision to TIME, TIMESTAMP, and INVERVAL data types (Thomas)</para></listitem>
+<listitem><para>Add precision to TIME, TIMESTAMP, and INTERVAL data types (Thomas)</para></listitem>
<listitem><para>Modify type coercion logic to attempt binary-compatible functions first (Tom)</para></listitem>
<listitem><para>New encode() function installed by default (Marko Kreen)</para></listitem>
<listitem><para>Improved to_*() conversion functions (Karel Zak)</para></listitem>
@@ -1584,7 +1584,7 @@ Properly escape jdbc setObject() strings to improve security (Barry)
<listitem><para>Fix for SQLPrimaryKeys in multibyte mode (Hiroshi)</para></listitem>
<listitem><para>Allow ODBC procedure calls (Hiroshi)</para></listitem>
<listitem><para>Improve boolean handing (Aidan Mountford)</para></listitem>
-<listitem><para>Most configuration options on setable via DSN (Hiroshi)</para></listitem>
+<listitem><para>Most configuration options now settable via DSN (Hiroshi)</para></listitem>
<listitem><para>Multibyte, performance fixes (Hiroshi)</para></listitem>
<listitem><para>Allow driver to be used with iODBC or unixODBC (Peter E)</para></listitem>
<listitem><para>MD5 password encryption support (Bruce)</para></listitem>
@@ -3351,7 +3351,7 @@ Add pg_dump -N flag to force double quotes around identifiers. This is
Fix for NOT in where clause causing crash(Bruce)
EXPLAIN VERBOSE coredump fix(Vadim)
Fix shared-library problems on Linux
-Fix test for table existance to allow mixed-case and whitespace in
+Fix test for table existence to allow mixed-case and whitespace in
the table name(Thomas)
Fix a couple of pg_dump bugs
Configure matches template/.similar entries better(Tom)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 853126c9812ce94b25e6b126e550c1c083fbcdc4..21089df67947a2c055d5d5e75878d8ac6ae4e7c5 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.208 2003/09/12 22:17:23 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.209 2003/09/20 20:12:05 tgl Exp $
-->
<Chapter Id="runtime">
@@ -3119,7 +3119,7 @@ kernel.shmmax = 134217728
</para>
<para>
- The symptom of this occuring is a kernel message looking like
+ The symptom of this occurring is a kernel message looking like
this (consult your system documentation and configuration on
where to look for such a message):
<programlisting>
@@ -3507,7 +3507,7 @@ openssl req -new -text -out server.req
</programlisting>
Fill out the information that <command>openssl</> asks for. Make sure
that you enter the local host name as <quote>Common Name</>; the challenge
- password can be left blank. The programm will generate a key that is
+ password can be left blank. The program will generate a key that is
passphrase protected; it will not accept a passphrase that is less
than four characters long. To remove the passphrase (as you must if
you want automatic start-up of the server), run the commands
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 2d3f574e39198f3fd8654f2433a252894e9c848c..352da5bab1bac8cfe17fdf49b13dd98ca041325e 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.24 2003/08/31 17:32:20 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.25 2003/09/20 20:12:05 tgl Exp $ -->
<chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
@@ -239,9 +239,10 @@
record to the log with <function>LogInsert</function> but before
performing a <function>LogFlush</function>. This delay allows other
server processes to add their commit records to the log so as to have all
- of them flushed with a single log sync. No sleep will occur if <varname>fsync</varname>
- is not enabled or if fewer than <varname>commit_siblings</varname>
- other sessons are currently in active transactions; this avoids
+ of them flushed with a single log sync. No sleep will occur if
+ <varname>fsync</varname>
+ is not enabled, nor if fewer than <varname>commit_siblings</varname>
+ other sessions are currently in active transactions; this avoids
sleeping when it's unlikely that any other session will commit soon.
Note that on most platforms, the resolution of a sleep request is
ten milliseconds, so that any nonzero <varname>commit_delay</varname>
diff --git a/doc/src/sgml/xplang.sgml b/doc/src/sgml/xplang.sgml
index c05c4948a2cb91bc362b8373217b53db9b95149d..c3482909eaa0ca24be1b1172636699d77660edf8 100644
--- a/doc/src/sgml/xplang.sgml
+++ b/doc/src/sgml/xplang.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xplang.sgml,v 1.23 2003/08/31 17:32:21 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/xplang.sgml,v 1.24 2003/09/20 20:12:05 tgl Exp $
-->
<chapter id="xplang">
@@ -68,7 +68,7 @@ createlang plpgsql template1
<para>
A procedural language is installed in a database in three steps,
which must be carried out by a database superuser. The
- <command>createlang</command> programm automates <xref
+ <command>createlang</command> program automates <xref
linkend="xplang-install-cr1"> and <xref
linkend="xplang-install-cr2">.
</para>
diff --git a/src/backend/catalog/sql_features.txt b/src/backend/catalog/sql_features.txt
index 0fe363db5a6c2db7aff5049e30dd9c1c5d04ac76..72b17d54e08be637db5ab22eb25c9458955705a2 100644
--- a/src/backend/catalog/sql_features.txt
+++ b/src/backend/catalog/sql_features.txt
@@ -13,7 +13,7 @@ B041 Extensions to embedded SQL exception declarations NO
B051 Enhanced execution rights NO
E011 Numeric data types YES
E011 Numeric data types 01 INTEGER and SMALLINT data types YES
-E011 Numeric data types 02 REAL, DOUBLE PRECISON, and FLOAT data types YES
+E011 Numeric data types 02 REAL, DOUBLE PRECISION, and FLOAT data types YES
E011 Numeric data types 03 DECIMAL and NUMERIC data types YES
E011 Numeric data types 04 Arithmetic operators YES
E011 Numeric data types 05 Numeric comparison YES