Copy-editing.

diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
index dc3379d8cd5b3a782ce6e449206e328100188236..31237a4440393368ed84ae7b0d8a58fe6c5220b8 100644 (file)
--- a/doc/src/sgml/advanced.sgml
+++ b/doc/src/sgml/advanced.sgml
@@ -132,7 +132,7 @@ ERROR:  <unnamed> referential integrity violation - key referenced from we
    <para>
     The behavior of foreign keys can be finely tuned to your
     application.  We will not go beyond this simple example in this
-    tutorial and refer you to the <citetitle>Reference
+    tutorial, but just refer you to the <citetitle>Reference
     Manual</citetitle> for more information.  Making correct use of
     foreign keys will definitely improve the quality of your database
     applications, so you are strongly encouraged to learn about them.

diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml
index c79b27850d6b06a3f7df3dbd3670a94171ed3b84..c319a6847472b9a8095c7a054eab12b3a1e5c1be 100644 (file)
--- a/doc/src/sgml/query.sgml
+++ b/doc/src/sgml/query.sgml
@@ -15,8 +15,8 @@ $Header$
     way a complete tutorial on <acronym>SQL</acronym>.  Numerous books
     have been written on <acronym>SQL92</acronym>, including <xref
     linkend="MELT93"> and <xref linkend="DATE97">.
-    You should be aware that some language
-    features are extensions to the standard.
+    You should be aware that some <productname>PostgreSQL</productname>
+    language features are extensions to the standard.
    </para>
 
    <para>
@@ -44,7 +44,7 @@ $Header$
 
     The <literal>\i</literal> command reads in commands from the
     specified file. The <literal>-s</literal> option puts you in
-    single step mode which pauses before sending a query to the
+    single step mode which pauses before sending each query to the
     server.  The commands used in this section are in the file
     <filename>basics.sql</filename>.
    </para>
@@ -78,11 +78,12 @@ $Header$
     <indexterm><primary>column</primary></indexterm>
 
     Each table is a named collection of <firstterm>rows</firstterm>.
-    Each row has the same set of named <firstterm>columns</firstterm>,
+    Each row of a given table has the same set of named
+    <firstterm>columns</firstterm>,
     and each column is of a specific data type.  Whereas columns have
     a fixed order in each row, it is important to remember that SQL
     does not guarantee the order of the rows within the table in any
-    way (unless they are explicitly sorted).
+    way (although they can be explicitly sorted for display).
    </para>
 
    <para>
@@ -200,7 +201,10 @@ DROP TABLE <replaceable>tablename</replaceable>;
 INSERT INTO weather VALUES ('San Francisco', 46, 50, 0.25, '1994-11-27');
 </programlisting>
 
-    Note that all data types use rather obvious input formats.  The
+    Note that all data types use rather obvious input formats.
+    Constants that are not simple numeric values usually must be
+    surrounded by single quotes (<literal>'</>), as in the example.
+    The
     <type>date</type> column is actually quite flexible in what it
     accepts, but for this tutorial we will stick to the unambiguous
     format shown here.
@@ -223,7 +227,7 @@ INSERT INTO weather (city, temp_lo, temp_hi, prcp, date)
     VALUES ('San Francisco', 43, 57, 0.0, '1994-11-29');
 </programlisting>
     You can list the columns in a different order if you wish or
-    even omit some columns, e.g., unknown precipitation:
+    even omit some columns, e.g., if the precipitation is unknown:
 <programlisting>
 INSERT INTO weather (date, city, temp_hi, temp_lo)
     VALUES ('1994-11-29', 'Hayward', 54, 37);
@@ -654,7 +658,9 @@ SELECT city, max(temp_lo)
 (2 rows)
 </screen>
 
-    which gives us one output row per city.  We can filter these grouped
+    which gives us one output row per city.  Each aggregate result is
+    computed over the table rows matching that city.
+    We can filter these grouped
     rows using <literal>HAVING</literal>:
 
 <programlisting>
@@ -671,8 +677,9 @@ SELECT city, max(temp_lo)
 (1 row)
 </screen>
 
-    which gives us the same results for only the cities that have some
-    below-forty readings.  Finally, if we only care about cities whose
+    which gives us the same results for only the cities that have all
+    <literal>temp_lo</> values below forty.  Finally, if we only care about
+    cities whose
     names begin with <quote><literal>S</literal></quote>, we might do
 
 <programlisting>

diff --git a/doc/src/sgml/start.sgml b/doc/src/sgml/start.sgml
index be3b169bad03184948c9dd76c97216cec0752f46..4a0f538b5f98975c927e1b89b7dee0a19365ef37 100644 (file)
--- a/doc/src/sgml/start.sgml
+++ b/doc/src/sgml/start.sgml
@@ -160,7 +160,7 @@ $Header$
 <screen>
 CREATE DATABASE
 </screen>
-    Is so, this step was successful and you can skip over the
+    If so, this step was successful and you can skip over the
     remainder of this section.
    </para>
 
@@ -173,7 +173,7 @@ createdb: command not found
     installed at all or the search path was not set correctly.  Try
     calling the command with an absolute path instead:
 <screen>
-<prompt>$</prompt> <userinput>/usr/local/pgsql/bin/createdb</userinput>
+<prompt>$</prompt> <userinput>/usr/local/pgsql/bin/createdb mydb</userinput>
 </screen>
     The path at your site might be different.  Contact your site
     administrator or check back in the installation instructions to
@@ -249,7 +249,7 @@ createdb: database creation failed
 <screen>
 <prompt>$</prompt> <userinput>dropdb mydb</userinput>
 </screen>
-    (In this case, the database name does not default to the user
+    (For this command, the database name does not default to the user
     account name.  You always need to specify it.)  This action
     physically removes all files associated with the database and
     cannot be undone, so this should only be done with a great deal of