Documentation cleanup

Author: petere

doc/src/sgml/ecpg.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.53 2003/10/17 18:57:00 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.54 2003/11/12 22:47:47 petere Exp $
 -->
 
 <chapter id="ecpg">
@@ -284,7 +284,7 @@ EXEC SQL COMMIT;
   </para>
 
   <para>
-   Single-row Select:
+   Single-row select:
 <programlisting>
 EXEC SQL SELECT foo INTO :FooBar FROM table1 WHERE ascii = 'doodad';
 </programlisting>
@@ -359,7 +359,7 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
    The second option is to execute a statement to switch the current
    connection.  That statement is:
 <programlisting>
-SET CONNECTION <replaceable>connection-name</replaceable>;
+EXEC SQL SET CONNECTION <replaceable>connection-name</replaceable>;
 </programlisting>
    This option is particularly convenient if many statements are to be
    executed on the same connection.
@@ -392,7 +392,7 @@ SET CONNECTION <replaceable>connection-name</replaceable>;
     write the name of a C variable into the SQL statement, prefixed by
     a colon.  For example:
 <programlisting>
-INSERT INTO sometable VALUES (:v1, 'foo', :v2);
+EXEC SQL INSERT INTO sometable VALUES (:v1, 'foo', :v2);
 </programlisting>
     This statements refers to two C variables named
     <varname>v1</varname> and <varname>v2</varname> and also uses a
@@ -592,7 +592,7 @@ EXEC SQL BEGIN DECLARE SECTION;
 const char *stmt = "CREATE TABLE test1 (...);";
 EXEC SQL END DECLARE SECTION;
 
-EXECUTE IMMEDIATE :stmt;
+EXEC SQL EXECUTE IMMEDIATE :stmt;
 </programlisting>
    You may not execute statements that retrieve data (e.g.,
    <command>SELECT</command>) this way.
@@ -611,9 +611,9 @@ EXEC SQL BEGIN DECLARE SECTION;
 const char *stmt = "INSERT INTO test1 VALUES(?, ?);";
 EXEC SQL END DECLARE SECTION;
 
-PREPARE mystmt FROM :stmt;
+EXEC SQL PREPARE mystmt FROM :stmt;
  ...
-EXECUTE mystmt USING 42, 'foobar';
+EXEC SQL EXECUTE mystmt USING 42, 'foobar';
 </programlisting>
    If the statement you are executing returns values, then add an
    <literal>INTO</literal> clause:
@@ -624,9 +624,9 @@ int v1, v2;
 VARCHAR v3;
 EXEC SQL END DECLARE SECTION;
 
-PREPARE mystmt FROM :stmt;
+EXEC SQL PREPARE mystmt FROM :stmt;
  ...
-EXECUTE mystmt INTO v1, v2, v3 USING 37;
+EXEC SQL EXECUTE mystmt INTO v1, v2, v3 USING 37;
 </programlisting>
    An <command>EXECUTE</command> command may have an
    <literal>INTO</literal> clause, a <literal>USING</literal> clause,
@@ -668,7 +668,7 @@ EXEC SQL DEALLOCATE PREPARE <replaceable>name</replaceable>;
 EXEC SQL ALLOCATE DESCRIPTOR <replaceable>identifier</replaceable>;
 </programlisting>
    The identifier serves as the <quote>variable name</quote> of the
-   descriptor area.  The scope of the allocated descriptor is WHAT?.
+   descriptor area.  <comment>The scope of the allocated descriptor is WHAT?.</comment>
    When you don't need the descriptor anymore, you should deallocate
    it:
 <programlisting>

doc/src/sgml/extend.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.25 2003/09/11 21:42:19 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.26 2003/11/12 22:47:47 petere Exp $
 -->
 
  <chapter id="extend">
@@ -105,52 +105,74 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.25 2003/09/11 21:42:19 momj
 
    <para>
     <productname>PostgreSQL</productname> data types are divided into base
-    types, composite types, domain types, and pseudo-types.
+    types, composite types, domains, and pseudo-types.
    </para>
 
-   <para>
-    Base  types  are those, like <type>int4</type>, that are implemented
-    below the level of the  <acronym>SQL</> language (typically in a low-level
-    language such as C).  They generally correspond  to
-    what are often known as abstract data types.
-    <productname>PostgreSQL</productname>
-    can only operate on such types through functions provided
-    by  the  user and only understands the behavior of such
-    types to the extent that the user describes them.  Base types are
-    further subdivided into scalar and array types.  For each scalar type,
-    a corresponding array type is automatically created that can hold
-    variable-size arrays of that scalar type.
-   </para>
+   <sect2>
+    <title>Base Types</title>
 
-   <para>
-    Composite  types, or row types,  are  created whenever the user creates a
-    table; it's also possible to define a <quote>stand-alone</> composite
-    type with no associated table.  A composite type is simply a list of
-    base types with associated field names.  A value of a composite type
-    is a row or record of field values.  The user can access the component
-    fields from <acronym>SQL</> queries.
-   </para>
+    <para>
+     Base types are those, like <type>int4</type>, that are
+     implemented below the level of the <acronym>SQL</> language
+     (typically in a low-level language such as C).  They generally
+     correspond to what are often known as abstract data types.
+     <productname>PostgreSQL</productname> can only operate on such
+     types through functions provided by the user and only understands
+     the behavior of such types to the extent that the user describes
+     them.  Base types are further subdivided into scalar and array
+     types.  For each scalar type, a corresponding array type is
+     automatically created that can hold variable-size arrays of that
+     scalar type.
+    </para>
+   </sect2>
 
-   <para>
-    A domain type is based on a particular base
-    type and for many purposes is interchangeable with its base type.
-    However, a domain may have constraints that restrict its valid values
-    to a subset of what the underlying base type would allow.  Domains can
-    be created by simple <acronym>SQL</> commands.
-   </para>
+   <sect2>
+    <title>Composite Types</title>
 
-   <para>
-    Finally, there are a few <quote>pseudo-types</> for special purposes.
-    Pseudo-types cannot appear as fields of tables or composite types, but
-    they can be used to declare the argument and result types of functions.
-    This provides a mechanism within the type system to identify special
-    classes of functions.  <xref
-    linkend="datatype-pseudotypes-table"> lists the existing
-    pseudo-types.
-   </para>
+    <para>
+     Composite types, or row types, are created whenever the user
+     creates a table; it's also possible to define a
+     <quote>stand-alone</> composite type with no associated table.  A
+     composite type is simply a list of base types with associated
+     field names.  A value of a composite type is a row or record of
+     field values.  The user can access the component fields from
+     <acronym>SQL</> queries.
+    </para>
+   </sect2>
+
+   <sect2>
+    <title>Domains</title>
+
+    <para>
+     A domain is based on a particular base type and for many purposes
+     is interchangeable with its base type.  However, a domain may
+     have constraints that restrict its valid values to a subset of
+     what the underlying base type would allow.
+    </para>
+
+    <para>
+     Domains can be created using the <acronym>SQL</> commands
+     <command>CREATE DOMAIN</command>.  Their creation and use is not
+     discussed in this chapter.
+    </para>
+   </sect2>
+
+   <sect2>
+    <title>Pseudo-Types</title>
+
+    <para>
+     There are a few <quote>pseudo-types</> for special purposes.
+     Pseudo-types cannot appear as columns of tables or attributes of
+     composite types, but they can be used to declare the argument and
+     result types of functions.  This provides a mechanism within the
+     type system to identify special classes of functions.  <xref
+     linkend="datatype-pseudotypes-table"> lists the existing
+     pseudo-types.
+    </para>
+   </sect2>
 
    <sect2 id="extend-types-polymorphic">
-    <title>Polymorphic Types and Functions</title>
+    <title>Polymorphic Types</title>
 
    <indexterm zone="extend-types-polymorphic">
     <primary>polymorphic type</primary>

doc/src/sgml/install-win32.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/install-win32.sgml,v 1.15 2003/11/04 09:55:38 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/install-win32.sgml,v 1.16 2003/11/12 22:47:47 petere Exp $
 -->
 
 <chapter id="install-win32">
@@ -109,7 +109,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/install-win32.sgml,v 1.15 2003/11/04 09:55:
 
  <para>
   <application>psql</application> is compiled as a <quote>console
-  application</>. As the Win32 console windows use a different
+  application</>. As the Windows console windows use a different
   encoding than the rest of the system, you must take special care
   when using 8-bit characters at the <application>psql</application>
   prompt. When <application>psql</application> detects a problematic