Copy-editing.

diff --git a/doc/src/sgml/history.sgml b/doc/src/sgml/history.sgml
index c9de0111a65461a6a16b773cfca47f3606bd007a..49218a01e89ebf491c9d436cadc455bf016261cd 100644 (file)
--- a/doc/src/sgml/history.sgml
+++ b/doc/src/sgml/history.sgml
@@ -42,8 +42,8 @@ $Header$
    <productname>Postgres</productname> has undergone  several  major  releases  since
    then.   The  first <quote>demoware</quote> system became operational
    in 1987 and was shown at the  1988  <acronym>ACM-SIGMOD</acronym>  
-   Conference.   We  released Version 1, described in 
-   <xref linkend="STON90a">,
+   Conference.   Version 1, described in 
+   <xref linkend="STON90a">, was released
    to a few external users in June 1989.  In response to a
    critique  of  the  first rule system 
    (<xref linkend="STON89">), 
@@ -54,7 +54,7 @@ $Header$
    released  in  June 1990 with the new rule system.  
    Version 3 appeared in 1991 and added support for  multiple
    storage  managers,  an  improved  query executor, and a
-   rewritten rewrite rule  system.   For  the  most  part,
+   rewritten rewrite rule  system.   For  the  most  part, subsequent
    releases  until <productname>Postgres95</productname> (see below)
    focused on portability and reliability.
   </para>
@@ -87,7 +87,8 @@ $Header$
    obvious that maintenance of the prototype code and 
    support  was  taking  up large amounts of time that should
    have been devoted to database research.  In  an  effort
-   to  reduce  this support burden, the project officially
+   to  reduce  this support burden, the Berkeley
+   <productname>Postgres</productname> project officially
    ended with Version 4.2.
   </para>
  </sect2>

diff --git a/doc/src/sgml/intro.sgml b/doc/src/sgml/intro.sgml
index 7ebece6153a32ec761d37742e26839837cae7e2a..a6a5e60017c05e1bd0f5e83f960df4b3b1f3e7ac 100644 (file)
--- a/doc/src/sgml/intro.sgml
+++ b/doc/src/sgml/intro.sgml
@@ -42,7 +42,7 @@ $Header$
     processing applications.
     The relational  model  successfully  replaced  previous
     models  in  part  because  of its <quote>Spartan simplicity</quote>.
-    However, as mentioned, this simplicity often makes  the
+    However, this simplicity makes  the
     implementation  of  certain applications very difficult.
     <productname>PostgreSQL</productname> offers  substantial additional
     power  by  incorporating  the following additional
@@ -86,7 +86,7 @@ $Header$
     category of databases referred to as
     <firstterm>object-relational</firstterm>. Note that this is distinct
     from those referred to as <firstterm>object-oriented</firstterm>,
-    which in general are not as well suited to supporting the
+    which in general are not as well suited to supporting
     traditional relational database languages.
     So, although <productname>PostgreSQL</productname> has some
     object-oriented features, it is firmly in the relational database

diff --git a/doc/src/sgml/notation.sgml b/doc/src/sgml/notation.sgml
index e5277c075814d9e2ba398ae7ec6af8e3abc85de9..970de9fd0acc19137c104dd88901187434bc5192 100644 (file)
--- a/doc/src/sgml/notation.sgml
+++ b/doc/src/sgml/notation.sgml
@@ -33,7 +33,7 @@ $Header$
   Anything in braces
   (<literal>{</literal> and <literal>}</literal>) and containing vertical bars
   (<literal>|</literal>)
-  indicates that you must choose one.
+  indicates that you must choose one alternative.
  </para>
 
  <para>