Make an editorial pass over the 9.0 release notes.

This is mostly about grammar, style, and presentation, though I did find
a few small factual errors.

doc/src/sgml/config.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.294.2.6 2010/08/22 02:37:38 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.294.2.7 2010/08/23 02:43:35 tgl Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -3474,7 +3474,7 @@ local0.*    /var/log/postgresql
             </row>
             <row>
              <entry><literal>%e</literal></entry>
-             <entry>SQL state</entry>
+             <entry>SQLSTATE error code</entry>
              <entry>no</entry>
             </row>
             <row>
@@ -3545,7 +3545,7 @@ FROM pg_stat_activity;
         <para>
          <application>Syslog</> produces its own 
          time stamp and process ID information, so you probably do not want to
-         use those escapes if you are logging to <application>syslog</>.
+         include those escapes if you are logging to <application>syslog</>.
         </para>
        </tip>
       </listitem>
@@ -3672,7 +3672,7 @@ FROM pg_stat_activity;
         virtual transaction ID,
         regular transaction ID,
         error severity,
-        SQL state code,
+        SQLSTATE code,
         error message,
         error message detail,
         hint,

doc/src/sgml/ddl.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.93.2.1 2010/07/29 19:34:36 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.93.2.2 2010/08/23 02:43:35 tgl Exp $ -->
 
 <chapter id="ddl">
  <title>Data Definition</title>
@@ -36,7 +36,7 @@
    is fixed, and each column has a name.  The number of rows is
    variable &mdash; it reflects how much data is stored at a given moment.
    SQL does not make any guarantees about the order of the rows in a
-   table.  When a table is read, the rows will appear in random order,
+   table.  When a table is read, the rows will appear in an unspecified order,
    unless sorting is explicitly requested.  This is covered in <xref
    linkend="queries">.  Furthermore, SQL does not assign unique
    identifiers to rows, so it is possible to have several completely
@@ -846,7 +846,7 @@ CREATE TABLE order_items (
    </para>
   </sect2>
 
-  <sect2>
+  <sect2 id="ddl-constraints-exclusion">
    <title>Exclusion constraints</title>
 
    <indexterm>