Reorder docs on lexical structure slightly for clarity.

Thom Brown

1 files changed, 7 insertions, 7 deletions

diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index 4ae3df325c9..f3cff8ed2d8 100644
--- a/doc/src/sgml/syntax.sgml
+++ b/doc/src/sgml/syntax.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.152 2010/08/12 02:03:58 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.153 2010/08/13 01:12:38 rhaas Exp $ -->
 
 <chapter id="sql-syntax">
  <title>SQL Syntax</title>
@@ -47,12 +47,6 @@
    special character is adjacent to some other token type).
   </para>
 
-  <para>
-   Additionally, <firstterm>comments</firstterm> can occur in SQL
-   input.  They are not tokens, they are effectively equivalent to
-   whitespace.
-  </para>
-
    <para>
     For example, the following is (syntactically) valid SQL input:
 <programlisting>
@@ -66,6 +60,12 @@ INSERT INTO MY_TABLE VALUES (3, 'hi there');
    </para>
 
   <para>
+   Additionally, <firstterm>comments</firstterm> can occur in SQL
+   input.  They are not tokens, they are effectively equivalent to
+   whitespace.
+  </para>
+
+  <para>
    The SQL syntax is not very consistent regarding what tokens
    identify commands and which are operands or parameters.  The first
    few tokens are generally the command name, so in the above example