Minor copy-editing.

doc/src/sgml/datatype.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.129 2003/11/04 09:55:38 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.130 2003/11/06 22:21:47 tgl Exp $
 -->
 
  <chapter id="datatype">
@@ -250,8 +250,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.129 2003/11/04 09:55:38 p
     <type>varchar</type>, <type>date</type>, <type>double
     precision</type>, <type>integer</type>, <type>interval</type>,
     <type>numeric</type>, <type>decimal</type>, <type>real</type>,
-    <type>smallint</type>, <type>time</type>, <type>timestamp</type>
-    (both with or without time zone).
+    <type>smallint</type>, <type>time</type> (with or without time zone),
+    <type>timestamp</type> (with or without time zone).
    </para>
   </note>
 

doc/src/sgml/datetime.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.36 2003/09/20 20:12:04 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.37 2003/11/06 22:21:47 tgl Exp $
 -->
 
  <appendix id="datetime-appendix">
@@ -995,7 +995,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.36 2003/09/20 20:12:04 tg
   <para>
    The Julian Date was invented by the French scholar
    Joseph Justus Scaliger (1540-1609)
-   and probably takes its name from the Scaliger's father,
+   and probably takes its name from Scaliger's father,
    the Italian scholar Julius Caesar Scaliger (1484-1558).
    Astronomers have used the Julian period to assign a unique number to
    every day since 1 January 4713 BC. This is the so-called Julian Date
@@ -1007,7 +1007,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.36 2003/09/20 20:12:04 tg
    The <quote>Julian Date</quote> is different from the <quote>Julian
    Calendar</quote>.  The Julian calendar
    was introduced by Julius Caesar in 45 BC. It was in common use
-   until the 1582, when countries started changing to the Gregorian
+   until the year 1582, when countries started changing to the Gregorian
    calendar.  In the Julian calendar, the tropical year is
    approximated as 365 1/4 days = 365.25 days. This gives an error of
    about 1 day in 128 years.
@@ -1042,7 +1042,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.36 2003/09/20 20:12:04 tg
    So, 1700, 1800, 1900, 2100, and 2200 are not leap years. But 1600,
    2000, and 2400 are leap years.
 
-   By contrast, in the older Julian calendar only years divisible by 4 are leap years.
+   By contrast, in the older Julian calendar all years divisible by 4 are leap
+   years.
   </para>
 
   <para>

doc/src/sgml/queries.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/queries.sgml,v 1.26 2003/11/04 09:55:38 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/queries.sgml,v 1.27 2003/11/06 22:21:47 tgl Exp $ -->
 
 <chapter id="queries">
  <title>Queries</title>
@@ -44,7 +44,7 @@ SELECT * FROM table1;
   client application.  For example, the
   <application>psql</application> program will display an ASCII-art
   table on the screen, while client libraries will offer functions to
-  retrieve individual rows and columns.)  The select list
+  extract individual values from the query result.)  The select list
   specification <literal>*</literal> means all columns that the table
   expression happens to provide.  A select list can also select a
   subset of the available columns or make calculations using the

doc/src/sgml/syntax.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.87 2003/11/04 19:18:15 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.88 2003/11/06 22:21:47 tgl Exp $
 -->
 
 <chapter id="sql-syntax">
@@ -205,7 +205,7 @@ UPDATE "my_table" SET "a" = 5;
     should be equivalent to <literal>"FOO"</literal> not
     <literal>"foo"</literal> according to the standard.  If you want
     to write portable applications you are advised to always quote a
-    particular name or never quote it.
+    particular name or never quote it.)
    </para>
   </sect2>
 
@@ -241,13 +241,13 @@ UPDATE "my_table" SET "a" = 5;
       <secondary>escaping</secondary>
      </indexterm>
      A string constant in SQL is an arbitrary sequence of characters
-     bounded by single quotes (<quote>'</quote>), e.g., <literal>'This
+     bounded by single quotes (<literal>'</literal>), e.g., <literal>'This
      is a string'</literal>.  SQL allows single quotes to be embedded
-     in strings by typing two adjacent single quotes (e.g.,
-     <literal>'Dianne''s horse'</literal>).  In
+     in strings by typing two adjacent single quotes, e.g.,
+     <literal>'Dianne''s horse'</literal>.  In
      <productname>PostgreSQL</productname> single quotes may
-     alternatively be escaped with a backslash (<quote>\</quote>,
-     e.g., <literal>'Dianne\'s horse'</literal>).
+     alternatively be escaped with a backslash (<literal>\</literal>),
+     e.g., <literal>'Dianne\'s horse'</literal>.
     </para>
 
     <para>
@@ -838,7 +838,7 @@ SELECT 3 OPERATOR(pg_catalog.+) 4;
    <itemizedlist>
     <listitem>
      <para>
-      A constant or literal value; see <xref linkend="sql-syntax-constants">.
+      A constant or literal value.
      </para>
     </listitem>