diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 47702cdfb0..753444d078 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -115,7 +115,7 @@ evaluating my query?
4.12) What is Genetic Query Optimization?
4.13) How do I do regular expression searches
-and case-insensitive regexp searching?
+and case-insensitive regular expression searching?
4.14) In a query, how do I detect if a field
is NULL?
4.15) What is the difference between the
@@ -351,7 +351,7 @@ http://www.PostgreSQL.org/docs/postgres.
in the distribution.
-There is a PostgreSQL book availiable at
http://www.PostgreSQL.org/docs/awbook.html
@@ -982,7 +982,7 @@ For further information see the documentation.
4.13) How do I do regular expression searches and
-case-insensitive regexp searching?
+case-insensitive regular expression searching?
The ~ operator does regular-expression matching, and ~*
does case-insensitive regular-expression matching. There is no
diff --git a/doc/src/sgml/ref/alter_user.sgml b/doc/src/sgml/ref/alter_user.sgml
index 922633a74a..8579b4f09a 100644
--- a/doc/src/sgml/ref/alter_user.sgml
+++ b/doc/src/sgml/ref/alter_user.sgml
@@ -1,5 +1,5 @@
@@ -167,7 +167,7 @@ ALTER USER manuel VALID UNTIL 'Jan 31 2030';
Change a user's valid until date, specifying that his
- authorisation should expire at midday on 4th May 1998 using
+ authorization should expire at midday on 4th May 1998 using
the time zone which is one hour ahead of UTC:
ALTER USER chris VALID UNTIL 'May 4 12:00:00 1998 +1';
diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml
index 3d7145c2db..9852f39f3a 100644
--- a/doc/src/sgml/ref/cluster.sgml
+++ b/doc/src/sgml/ref/cluster.sgml
@@ -1,5 +1,5 @@
@@ -129,7 +129,7 @@ ERROR: Relation table does not exis
In other words, as the class is updated, the changes are
not clustered. No attempt is made to keep new instances or
updated tuples clustered. If one wishes, one can
- recluster manually by issuing the command again.
+ re-cluster manually by issuing the command again.
diff --git a/doc/src/sgml/ref/create_constraint.sgml b/doc/src/sgml/ref/create_constraint.sgml
index 474b848a91..c8759c8f18 100644
--- a/doc/src/sgml/ref/create_constraint.sgml
+++ b/doc/src/sgml/ref/create_constraint.sgml
@@ -1,5 +1,5 @@
@@ -76,7 +76,7 @@ CREATE CONSTRAINT TRIGGER name
attributes
- Contraint attributes.
+ Constraint attributes.
diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index e75d86cd2e..f46e9796ee 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -1,5 +1,5 @@
@@ -301,7 +301,7 @@ CREATE FUNCTION point(complex) RETURNS point
LANGUAGE 'c';
- The C decalaration of the function is:
+ The C declaration of the function is:
Point * complex_to_point (Complex *z)
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 7dc04b0aaf..41037655c6 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -1,5 +1,5 @@
@@ -1351,7 +1351,7 @@ ERROR: name referential integrity
Define a UNIQUE table constraint for the table distributors:
CREATE TABLE distributors (
- did DECIMAL(03),
+ did DECIMAL(3),
name VARCHAR(40),
UNIQUE(name)
);
@@ -1737,7 +1737,7 @@ CREATE TABLE films (
CREATE TABLE distributors (
- did DECIMAL(03) PRIMARY KEY DEFAULT NEXTVAL('serial'),
+ did DECIMAL(3) PRIMARY KEY DEFAULT NEXTVAL('serial'),
name VARCHAR(40) NOT NULL CHECK (name <> '')
);
@@ -1762,7 +1762,7 @@ CREATE TABLE distributors (
CREATE TABLE films (
code CHAR(5),
title VARCHAR(40),
- did DECIMAL(03),
+ did DECIMAL(3),
date_prod DATE,
kind CHAR(10),
len INTERVAL HOUR TO MINUTE,
@@ -1801,9 +1801,9 @@ CREATE TABLE distributors (
CREATE TABLE films (
- code CHAR(05),
+ code CHAR(5),
title VARCHAR(40),
- did DECIMAL(03),
+ did DECIMAL(3),
date_prod DATE,
kind CHAR(10),
len INTERVAL HOUR TO MINUTE,
@@ -1819,7 +1819,7 @@ CREATE TABLE films (
CREATE TABLE distributors (
- did DECIMAL(03),
+ did DECIMAL(3),
name CHAR VARYING(40),
PRIMARY KEY(did)
);
@@ -1827,7 +1827,7 @@ CREATE TABLE distributors (
CREATE TABLE distributors (
- did DECIMAL(03) PRIMARY KEY,
+ did DECIMAL(3) PRIMARY KEY,
name VARCHAR(40)
);
@@ -1881,7 +1881,7 @@ CREATE GLOBAL TEMPORARY TABLE table
CREATE TEMPORARY TABLE actors (
- id DECIMAL(03),
+ id DECIMAL(3),
name VARCHAR(40),
CONSTRAINT actor_id CHECK (id < 150)
) ON COMMIT DELETE ROWS;
diff --git a/doc/src/sgml/ref/drop_type.sgml b/doc/src/sgml/ref/drop_type.sgml
index 35e1d1d391..789d8b3798 100644
--- a/doc/src/sgml/ref/drop_type.sgml
+++ b/doc/src/sgml/ref/drop_type.sgml
@@ -1,5 +1,5 @@
@@ -109,7 +109,7 @@ ERROR: RemoveType: type 'typename'
Refer to CREATE TYPE for
- inforamation on how to create types.
+ information on how to create types.
It is the user's responsibility to remove any operators,
diff --git a/doc/src/sgml/ref/fetch.sgml b/doc/src/sgml/ref/fetch.sgml
index 6c0edfd074..cb5c33fdcb 100644
--- a/doc/src/sgml/ref/fetch.sgml
+++ b/doc/src/sgml/ref/fetch.sgml
@@ -1,5 +1,5 @@
@@ -187,7 +187,7 @@ ERROR: FETCH/RELATIVE at current position is not supported
- SQL92 allows one to repetatively retrieve the cursor
+ SQL92 allows one to repetitively retrieve the cursor
at its "current position" using the syntax
FETCH RELATIVE 0 FROM cursor
diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml
index f427eb133c..07d415f8fb 100644
--- a/doc/src/sgml/ref/lock.sgml
+++ b/doc/src/sgml/ref/lock.sgml
@@ -1,5 +1,5 @@
@@ -284,7 +284,7 @@ ERROR name: Table does not exist.
For example, an application runs a transaction at READ COMMITTED isolation
- level and needs to ensure the existance of data in a table for the
+ level and needs to ensure the existence of data in a table for the
duration of the
transaction. To achieve this you could use SHARE lock mode over the
table before querying. This will protect data from concurrent changes
diff --git a/doc/src/sgml/ref/pgctl-ref.sgml b/doc/src/sgml/ref/pgctl-ref.sgml
index 88cb70056f..c85b5e31e1 100644
--- a/doc/src/sgml/ref/pgctl-ref.sgml
+++ b/doc/src/sgml/ref/pgctl-ref.sgml
@@ -1,5 +1,5 @@
@@ -119,7 +119,7 @@ pg_ctl [-D datadir] status
Immediate mode sends SIGUSR1
to the backends and lets them abort. In this case, database recovery
- will be neccessary on the next startup.
+ will be necessary on the next startup.
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index 9c0e168910..5ca738796e 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1,5 +1,5 @@
@@ -306,7 +306,7 @@ WHERE boolean_expr
boolean_expr
can consist of any expression which evaluates to a boolean value.
- In many cases, this expression will be
+ In many cases, this expression will be:
expr cond_op expr