Spell-check and markup police

doc/src/sgml/ref/alter_table.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.34 2001/12/08 03:24:33 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.35 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -246,7 +246,7 @@ DROP TABLE temp;
    Usage
   </title>
   <para>
-   To add a column of type VARCHAR to a table:
+   To add a column of type <type>varchar</type> to a table:
    <programlisting>
 ALTER TABLE distributors ADD COLUMN address VARCHAR(30);
    </programlisting>
@@ -288,7 +288,7 @@ ALTER TABLE distributors ADD CONSTRAINT distfk FOREIGN KEY (address) REFERENCES
   </para>
 
   <para> 
-   To add a (multi-column) unique constraint to a table:
+   To add a (multicolumn) unique constraint to a table:
    <programlisting>
 ALTER TABLE distributors ADD CONSTRAINT dist_id_zipcode_key UNIQUE (dist_id, zipcode);
    </programlisting>

doc/src/sgml/ref/analyze.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.5 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.6 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -152,7 +152,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep
    distribution in each column.  One or both of these may be omitted if
    <command>ANALYZE</command> deems them uninteresting (for example, in
    a unique-key column, there are no common values) or if the column
-   datatype does not support the appropriate operators.  There is more
+   data type does not support the appropriate operators.  There is more
    information about the statistics in the <citetitle>User's
    Guide</citetitle>.
   </para>

doc/src/sgml/ref/close.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.9 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.10 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -125,7 +125,7 @@ NOTICE PerformPortalClose: portal "<replaceable class="PARAMETER">cursor</replac
    Usage
   </title>
   <para>
-   Close the cursor liahona:
+   Close the cursor <literal>liahona</literal>:
   </para>
   <programlisting>
 CLOSE liahona;

doc/src/sgml/ref/copy.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.26 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.27 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -74,7 +74,7 @@ COPY [ BINARY ] <replaceable class="parameter">table</replaceable> [ WITH OIDS ]
       <term><replaceable class="parameter">filename</replaceable></term>
       <listitem>
        <para>
-	The absolute Unix pathname of the input or output file.
+	The absolute Unix file name of the input or output file.
        </para>
       </listitem>
      </varlistentry>
@@ -181,7 +181,7 @@ ERROR: <replaceable>reason</replaceable>
   </para>
 
   <para>
-   <command>COPY</command> with a filename instructs
+   <command>COPY</command> with a file name instructs
    the <productname>PostgreSQL</productname> backend
    to directly read from or write to a file.
    The file must be accessible to the backend and the name must be specified
@@ -262,8 +262,8 @@ ERROR: <replaceable>reason</replaceable>
     directly by the backend, not by the client application.  Therefore,
     they must reside on or be accessible to the database server machine,
     not the client.  They must be accessible to and readable or writable
-    by the <application>PostgreSQL</application> user (the userid the
-    backend runs as), not the client.
+    by the <application>PostgreSQL</application> user (the user ID the
+    server runs as), not the client.
     <command>COPY</command> naming a file is only allowed to database
     superusers, since it allows writing on any file that the backend has
     privileges to write on.
@@ -483,7 +483,7 @@ The typlen field is interpreted thus:
       <term>&gt; 0</term>
       <listitem>
        <para>
-        Field is a fixed-length datatype.  Exactly N
+        Field is a fixed-length data type.  Exactly N
 	bytes of data follow the typlen word.
        </para>
       </listitem>
@@ -493,7 +493,7 @@ The typlen field is interpreted thus:
       <term>-1</term>
       <listitem>
        <para>
-	Field is a varlena datatype.  The next four
+	Field is a varlena data type.  The next four
 	bytes are the varlena header, which contains
 	the total value length including itself.
        </para>
@@ -519,7 +519,7 @@ but very useful check that the data is as expected.
 
     <para>
 There is no alignment padding or any other extra data between fields.
-Note also that the format does not distinguish whether a datatype is
+Note also that the format does not distinguish whether a data type is
 pass-by-reference or pass-by-value.  Both of these provisions are
 deliberate: they might help improve portability of the files (although
 of course endianness and floating-point-format issues can still keep

doc/src/sgml/ref/create_constraint.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.4 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.5 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -67,7 +67,7 @@ CREATE CONSTRAINT TRIGGER <replaceable class="parameter">name</replaceable>
       <term><replaceable class="PARAMETER">constraint</replaceable></term>
       <listitem>
        <para>
-	Actual onstraint specification.
+	Actual constraint specification.
        </para>
       </listitem>
      </varlistentry>

doc/src/sgml/ref/create_database.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.22 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.23 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -51,7 +51,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
       <term><replaceable class="parameter">dbpath</replaceable></term>
       <listitem>
        <para>
-	An alternate filesystem location in which to store the new database,
+	An alternate file-system location in which to store the new database,
 	specified as a string literal;
 	or <literal>DEFAULT</literal> to use the default location.
        </para>

doc/src/sgml/ref/create_group.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.6 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.7 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -110,7 +110,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be:
   </title>
   <para>
    CREATE GROUP will create a new group in the database installation.
-   Refer to the adminstrator's guide for information about using groups
+   Refer to the <citetitle>Administrator's Guide</citetitle> for information about using groups
    for authentication.
    You must be a database superuser to use this command.
   </para>

doc/src/sgml/ref/create_index.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.25 2001/12/08 03:24:34 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.26 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -77,7 +77,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
       <listitem>
        <para>
 	The name of the access method to be used for
-	the index. The default access method is BTREE.
+	the index. The default access method is <literal>BTREE</literal>.
 	<application>PostgreSQL</application> provides four access methods for indexes:
 
 	<variablelist>
@@ -86,7 +86,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
 	  <listitem>
 	   <para>
 	    an implementation of Lehman-Yao
-	    high-concurrency btrees.
+	    high-concurrency B-trees.
 	   </para>
 	  </listitem>
 	 </varlistentry>
@@ -94,7 +94,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
 	 <varlistentry>
 	  <term>RTREE</term>
 	  <listitem>
-	   <para>implements standard rtrees using Guttman's
+	   <para>implements standard R-trees using Guttman's
 	    quadratic split algorithm.
 	   </para>
 	  </listitem>
@@ -221,7 +221,7 @@ ERROR: Cannot create index: 'index_name' already exists.
    In the first syntax shown above, the key field(s) for the
    index are specified as column names.
    Multiple fields can be specified if the index access method supports
-   multi-column indexes.
+   multicolumn indexes.
   </para>
 
   <para>
@@ -236,10 +236,10 @@ ERROR: Cannot create index: 'index_name' already exists.
   </para>
 
   <para>
-   <application>PostgreSQL</application> provides btree, rtree, hash, and GiST access methods for
-   indexes.  The btree access method is an implementation of
-   Lehman-Yao high-concurrency btrees.  The rtree access method
-   implements standard rtrees using Guttman's quadratic split algorithm.
+   <application>PostgreSQL</application> provides B-tree, R-tree, hash, and GiST access methods for
+   indexes.  The B-tree access method is an implementation of
+   Lehman-Yao high-concurrency B-trees.  The R-tree access method
+   implements standard R-trees using Guttman's quadratic split algorithm.
    The hash access method is an implementation of Litwin's linear
    hashing.  We mention the algorithms used solely to indicate that all
    of these access methods are fully dynamic and do not have to be
@@ -293,7 +293,7 @@ ERROR: Cannot create index: 'index_name' already exists.
 
    <para>
     The <productname>PostgreSQL</productname>
-    query optimizer will consider using a btree index whenever
+    query optimizer will consider using a B-tree index whenever
     an indexed attribute is involved in a comparison using one of:
 
     <simplelist type="inline">
@@ -307,7 +307,7 @@ ERROR: Cannot create index: 'index_name' already exists.
 
    <para>
     The <productname>PostgreSQL</productname>
-    query optimizer will consider using an rtree index whenever
+    query optimizer will consider using an R-tree index whenever
     an indexed attribute is involved in a comparison using one of:
 
     <simplelist type="inline">
@@ -329,17 +329,17 @@ ERROR: Cannot create index: 'index_name' already exists.
    </para>
 
    <para>
-    Currently, only the btree and gist access methods support multi-column
+    Currently, only the B-tree and gist access methods support multi-column
     indexes. Up to 16 keys may be specified by default (this limit
     can be altered when building
-    <application>PostgreSQL</application>).  Only btree currently supports
+    <application>PostgreSQL</application>).  Only B-tree currently supports
     unique indexes.
    </para>
 
   <para>
    An <firstterm>operator class</firstterm> can be specified for each
    column of an index.  The operator class identifies the operators to
-   be used by the index for that column.  For example, a btree index on
+   be used by the index for that column.  For example, a B-tree index on
    four-byte integers would use the <literal>int4_ops</literal> class;
    this operator class includes comparison functions for four-byte
    integers.  In practice the default operator class for the field's
@@ -355,7 +355,7 @@ ERROR: Cannot create index: 'index_name' already exists.
     <listitem>
      <para>
       The operator classes <literal>box_ops</literal> and
-      <literal>bigbox_ops</literal> both support rtree indexes on the
+      <literal>bigbox_ops</literal> both support R-tree indexes on the
       <literal>box</literal> data type.
       The difference between them is that <literal>bigbox_ops</literal>
       scales box coordinates down, to avoid floating-point exceptions from
@@ -389,7 +389,7 @@ SELECT am.amname AS acc_method,
   <title>
    Usage
   </title>
-  <para>To create a btree index on the field <literal>title</literal>
+  <para>To create a B-tree index on the field <literal>title</literal>
    in the table <literal>films</literal>:
   </para>
   <programlisting>
@@ -402,7 +402,7 @@ CREATE UNIQUE INDEX title_idx
 Is this example correct?
 </comment>
   <para>
-   To create a rtree index on a point attribute so that we
+   To create a R-tree index on a point attribute so that we
    can efficiently use box operators on the result of the
    conversion function:
   </para>

doc/src/sgml/ref/create_operator.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.23 2002/01/07 02:29:15 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.24 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -175,7 +175,7 @@ CREATE
   </para>
   <para>
    The operator <replaceable class="parameter">name</replaceable>
-   is a sequence of up to NAMEDATALEN-1 (31 by default) characters
+   is a sequence of up to <symbol>NAMEDATALEN</>-1 (31 by default) characters
    from the following list:
    <literallayout>
 + - * / &lt; &gt; = ~ ! @ # % ^ &amp; | ` ? $
@@ -186,7 +186,7 @@ CREATE
     <listitem>
      <para>
      <literal>$</literal> cannot be defined as a single-character operator,
-     although it can be part of a multi-character operator name.
+     although it can be part of a multicharacter operator name.
      </para>
     </listitem>
     <listitem>
@@ -197,7 +197,7 @@ CREATE
     </listitem>
     <listitem>
      <para>
-     A multi-character operator name cannot end in <literal>+</literal> or
+     A multicharacter operator name cannot end in <literal>+</literal> or
      <literal>-</literal>,
      unless the name also contains at least one of these characters:
      <literallayout>
@@ -299,7 +299,7 @@ MYBOXES.description !== box '((0,0), (1,1))'
    query  optimizer in performing joins.  
    <productname>PostgreSQL</productname> can always
    evaluate a join (i.e., processing a clause with two  tuple
-   variables separated by an operator that returns a boolean)
+   variables separated by an operator that returns a <type>boolean</type>)
    by iterative substitution [WONG76].  
    In addition, <productname>PostgreSQL</productname>
    can use a hash-join algorithm along

doc/src/sgml/ref/create_sequence.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.23 2001/12/08 03:24:35 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.24 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -265,9 +265,9 @@ SELECT * FROM <replaceable>seqname</replaceable>;
     will be lost when that session ends.  Furthermore, although multiple backends are guaranteed to
     allocate distinct sequence values, the values may be generated out of
     sequence when all the backends are considered.  (For example, with a <replaceable class="parameter">cache</replaceable>
-    setting of 10, backend A might reserve values 1..10 and return nextval=1, 
+    setting of 10, backend A might reserve values 1..10 and return <function>nextval</function>=1, 
     then
-    backend B might reserve values 11..20 and return nextval=11 before backend
+    backend B might reserve values 11..20 and return <function>nextval</function>=11 before backend
     A has generated nextval=2.)  Thus, with a <replaceable class="parameter">cache</replaceable> setting of one it is safe
     to assume that <function>nextval</> values are generated sequentially; with a <replaceable class="parameter">cache</replaceable>
     setting greater than one you should only assume that the <function>nextval</> values

doc/src/sgml/ref/create_table.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.51 2002/01/03 06:26:22 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.52 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -367,7 +367,7 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
       match type.  There are three match types: <literal>MATCH
       FULL</>, <literal>MATCH PARTIAL</>, and a default match type if
       none is specified. <literal>MATCH FULL</> will not allow one
-      column of a multi-column foreign key to be NULL unless all
+      column of a multicolumn foreign key to be NULL unless all
       foreign key columns are NULL. The default match type allows some
       foreign key columns to be NULL while other parts of the foreign
       key are not NULL. <literal>MATCH PARTIAL</> is not yet
@@ -583,7 +583,7 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
     <para>
      Unique constraints and primary keys are not inherited in the
      current implementation.  This makes the combination of
-     inheritance and unique constraints rather disfunctional.
+     inheritance and unique constraints rather dysfunctional.
     </para>
    </listitem>
   </itemizedlist>
@@ -800,7 +800,7 @@ CREATE { GLOBAL | LOCAL } TEMPORARY TABLE <replaceable class="parameter">table</
     The <literal>NULL</> <quote>constraint</quote> (actually a
     non-constraint) is a <productname>PostgreSQL</productname>
     extension to SQL92 that is included for compatibility with some
-    other RDBMSes (and for symmetry with the <literal>NOT
+    other RDBMS (and for symmetry with the <literal>NOT
     NULL</literal> constraint).  Since it is the default for any
     column, its presence is simply noise.
    </para>

doc/src/sgml/ref/create_trigger.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.21 2001/12/08 03:24:35 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.22 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -232,7 +232,7 @@ CREATE TABLE distributors (
        <listitem>
         <para>
          SQL99 allows you to define aliases for the <quote>old</quote>
-         and <quote>new</quote> rows or tables for use in the definiton
+         and <quote>new</quote> rows or tables for use in the definition
          of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
          tablename REFERENCING OLD ROW AS somename NEW ROW AS
          othername ...</literal>).  Since

doc/src/sgml/ref/create_type.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.25 2001/12/08 03:24:35 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.26 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -238,7 +238,7 @@ CREATE
    declared as taking one argument of type <type>opaque</type>,
    or as taking two arguments of types
    <type>opaque</type>, <type>OID</type>.
-   (The first argument is actually of the datatype itself, but since the
+   (The first argument is actually of the data type itself, but since the
    output function must be declared first, it's easier to declare it as
    accepting type <type>opaque</type>.  The second argument is again
    the array element type for array types.)
@@ -282,7 +282,7 @@ CREATE
 
   <para>
    A default value may be specified, in case a user wants columns of the
-   datatype to default to something other than NULL.
+   data type to default to something other than NULL.
    Specify the default with the <option>DEFAULT</option> keyword.
    (Such a default may be overridden by an explicit <option>DEFAULT</option>
    clause attached to a particular column.)
@@ -311,7 +311,7 @@ CREATE
 
   <para>
    The <replaceable class="parameter">alignment</replaceable> keyword
-   specifies the storage alignment required for the datatype.  The
+   specifies the storage alignment required for the data type.  The
    allowed values equate to alignment on 1, 2, 4, or 8 byte boundaries.
    Note that variable-length types must have an alignment of at least
    4, since they necessarily contain an <type>int4</> as their first component.
@@ -339,7 +339,7 @@ CREATE
    <title>Array Types</title>
 
    <para>
-    Whenever a user-defined datatype is created, 
+    Whenever a user-defined data type is created, 
     <productname>PostgreSQL</productname> automatically creates an
     associated array type, whose name consists of the base type's
     name prepended with an underscore.  The parser understands this
@@ -358,7 +358,7 @@ CREATE
     identical things, and you want to allow the N things to be accessed
     directly by subscripting, in addition to whatever operations you plan
     to provide for the type as a whole.  For example, type <type>name</>
-    allows its constitutent <type>char</>s to be accessed this way.
+    allows its constituent <type>char</>s to be accessed this way.
     A 2-D <type>point</> type could allow its two component floats to be
     accessed like <literal>point[0]</> and <literal>point[1]</>.
     Note that

doc/src/sgml/ref/createdb.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.23 2001/12/08 03:24:35 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.24 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -238,7 +238,7 @@ PostgreSQL documentation
   <informalexample>
    <para>
     To create the database <literal>demo</literal> using the
-    server on host eden, port 5000, using the
+    server on host <literal>eden</>, port 5000, using the
     <literal>LATIN1</literal> encoding scheme with a look at the
     underlying query:
 <screen>

doc/src/sgml/ref/createuser.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.22 2001/12/08 03:24:35 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.23 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -255,7 +255,7 @@ PostgreSQL documentation
   <informalexample>
    <para>
     To create the same user <literal>joe</literal> using the
-    server on host eden, port 5000, avoiding the prompts and
+    server on host <literal>eden</>, port 5000, avoiding the prompts and
     taking a look at the underlying query:
 <screen>
 <prompt>$ </prompt><userinput>createuser -p 5000 -h eden -D -A -e joe</userinput>

doc/src/sgml/ref/drop_aggregate.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.15 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -47,7 +47,7 @@ DROP AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( <replaceable
       <term><replaceable class="parameter">type</replaceable></term>
       <listitem>
        <para>
-	The input datatype of an existing aggregate function,
+	The input data type of an existing aggregate function,
 	or <literal>*</literal> if the function accepts any input type.
 	(Refer to the <citetitle>PostgreSQL User's Guide</citetitle> for
 	further information about data types.)

doc/src/sgml/ref/drop_operator.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.13 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -176,7 +176,7 @@ DROP OPERATOR ^ (int4, int4);
    </programlisting>
   </para>
   <para>
-   Remove left unary negation operator (<literal>! b</literal>) for booleans:
+   Remove left unary negation operator (<literal>! b</literal>) for <type>boolean</type>:
    <programlisting>
 DROP OPERATOR ! (none, bool);
    </programlisting>

doc/src/sgml/ref/drop_type.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.14 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -105,7 +105,7 @@ ERROR:  RemoveType: type '<replaceable class="parameter">typename</replaceable>'
     <para>
      It is the user's responsibility to remove any operators,
      functions, aggregates, access methods, subtypes, and tables that
-     use a deleted type.  However, the associated array datatype
+     use a deleted type.  However, the associated array data type
      (which was automatically created by <command>CREATE TYPE</command>)
      will be removed automatically.
     </para>

doc/src/sgml/ref/drop_user.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.14 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -72,7 +72,7 @@ ERROR:  DROP USER: user "<replaceable class="parameter">name</replaceable>" does
        </computeroutput></term>
       <listitem>
        <para>
-	This message occurs if the username is not found.
+	This message occurs if the user name is not found.
        </para>
       </listitem>
      </varlistentry>

doc/src/sgml/ref/dropdb.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.14 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -40,7 +40,7 @@ PostgreSQL documentation
 	Specifies the host name of the machine on which the 
 	server
 	is running.  If host begins with a slash, it is used 
-	as the directory for the unix domain socket.
+	as the directory for the Unix domain socket.
        </para>
       </listitem>
      </varlistentry>
@@ -193,7 +193,7 @@ PostgreSQL documentation
   <informalexample>
    <para>
     To destroy the database <literal>demo</literal> using the
-    server on host eden, port 5000, with verification and a peek
+    server on host <literal>eden</literal>, port 5000, with verification and a peek
     at the underlying query:
 <screen>
 <prompt>$ </prompt><userinput>dropdb -p 5000 -h eden -i -e demo</userinput>

doc/src/sgml/ref/dropuser.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.15 2001/12/08 03:24:36 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.16 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -184,7 +184,7 @@ PostgreSQL documentation
   <informalexample>
    <para>
     To remove user <literal>joe</literal> using the postmaster on host
-    eden, port 5000, with verification and a peek at the underlying
+    <literal>eden</literal>, port 5000, with verification and a peek at the underlying
     query:
 <screen>
 <prompt>$ </prompt><userinput>dropuser -p 5000 -h eden -i -e joe</userinput>

doc/src/sgml/ref/ecpg-ref.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.17 2002/01/18 20:32:54 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.18 2002/01/20 22:19:56 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -84,7 +84,7 @@ PostgreSQL documentation
       <term>-o <replaceable>outfile</replaceable></term>
       <listitem>
        <para>
-	Specifies that <application>ecpg</application> should write all its output to outfile.
+	Specifies that <application>ecpg</application> should write all its output to <replaceable>outfile</replaceable>.
 	If no such option is given the output is written to
 	<filename><replaceable>name</replaceable>.c</filename>,
 	assuming the input file was 
@@ -255,7 +255,7 @@ EXEC SQL INCLUDE sqlca;
       The <literal>sqlca</literal> is in lowercase.
       While SQL convention may be 
       followed, i.e., using uppercase to separate embedded SQL 
-      from C statements, sqlca (which includes the <filename>sqlca.h</>
+      from C statements, <literal>sqlca</literal> (which includes the <filename>sqlca.h</>
       header file) <emphasis>must</> be lowercase.  This is because the
       EXEC SQL prefix indicates that this inclusion will be parsed by
       <application>ecpg</application>.
@@ -268,7 +268,7 @@ EXEC SQL INCLUDE sqlca;
     </note>
 
    <para>
-    The sqlprint command is used with the EXEC SQL WHENEVER
+    The <literal>sqlprint</literal> command is used with the <literal>EXEC SQL WHENEVER</literal>
     statement to turn on error handling throughout the 
     program:
 

doc/src/sgml/ref/grant.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.18 2002/01/18 01:04:53 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.19 2002/01/20 22:19:57 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -216,7 +216,7 @@ GRANT INSERT ON films TO PUBLIC;
   </para>
 
   <para>
-   Grant all privileges to user manuel on view kinds:
+   Grant all privileges to user <literal>manuel</literal> on view <literal>kinds</literal>:
 
 <programlisting>
 GRANT ALL PRIVILEGES ON kinds TO manuel;

doc/src/sgml/ref/load.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/load.sgml,v 1.11 2001/11/18 20:35:02 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/load.sgml,v 1.12 2002/01/20 22:19:57 petere Exp $
 -->
 
 <refentry id="SQL-LOAD">
@@ -33,10 +33,10 @@ LOAD '<replaceable class="PARAMETER">filename</replaceable>'
   </para>
 
   <para>
-   The filename is specified in the same way as for shared library
+   The file name is specified in the same way as for shared library
    names in <xref linkend="sql-createfunction" endterm="sql-createfunction-title">; in particular, one
    may rely on a search path and automatic addition of the system's standard
-   shared library filename extension.  See the
+   shared library file name extension.  See the
    <citetitle>Programmer's Guide</citetitle> for more detail.
   </para>
  </refsect1>

doc/src/sgml/ref/pg_config-ref.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.8 2001/09/16 16:11:09 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.9 2002/01/20 22:19:57 petere Exp $ -->
 
 <refentry id="app-pgconfig">
  <docinfo>
@@ -50,7 +50,7 @@
    To use <application>pg_config</>, supply one or more of the following options:
    <variablelist>
     <varlistentry>
-     <term>--bindir</>
+     <term><option>--bindir</option></>
      <listitem>
       <para>
        Print the location of user executables. Use this, for example, to find
@@ -61,7 +61,7 @@
     </varlistentry>
 
     <varlistentry>
-     <term>--includedir</>
+     <term><option>--includedir</option></>
      <listitem>
       <para>
        Print the location of C and C++ header files of the client interfaces.
@@ -70,7 +70,7 @@
     </varlistentry>
 
     <varlistentry>
-     <term>--includedir-server</>
+     <term><option>--includedir-server</option></>
      <listitem>
       <para>
        Print the location of C and C++ header files for server
@@ -80,7 +80,7 @@
     </varlistentry>
 
     <varlistentry>
-     <term>--libdir</>
+     <term><option>--libdir</option></>
      <listitem>
       <para>
        Print the location of object code libraries.
@@ -89,7 +89,7 @@
     </varlistentry>
 
     <varlistentry>
-     <term>--pkglibdir</>
+     <term><option>--pkglibdir</option></>
      <listitem>
       <para>
        Print the location of dynamically loadable modules, or where
@@ -101,7 +101,7 @@
     </varlistentry>
 
     <varlistentry>
-     <term>--configure</>
+     <term><option>--configure</option></>
      <listitem>
       <para>
        Print the options that were given to the <filename>configure</>
@@ -115,7 +115,7 @@
     </varlistentry>
 
     <varlistentry>
-     <term>--version</>
+     <term><option>--version</option></>
      <listitem>
       <para>
        Print the version of <productname>PostgreSQL</> and exit.

doc/src/sgml/ref/select_into.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.15 2001/12/08 03:24:39 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.16 2002/01/20 22:19:57 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -123,7 +123,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
    <command>SELECT INTO</command> creates a new table and fills it
    with data computed by a query.  The data is not returned to the
    client, as it is with a normal <command>SELECT</command>.  The new
-   table's columns have the names and datatypes associated with the
+   table's columns have the names and data types associated with the
    output columns of the <command>SELECT</command>.
 
    <note>
@@ -132,7 +132,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
      is functionally equivalent to <command>SELECT INTO</command>.
      <command>CREATE TABLE AS</command> is the recommended syntax, since
      <command>SELECT INTO</command> is not standard.  In fact, this form of
-     <command>SELECT INTO</command> is not available in PL/pgSQL or ecpg,
+     <command>SELECT INTO</command> is not available in <application>PL/pgSQL</application> or <xref linkend="app-ecpg">,
      because they interpret the INTO clause differently.
     </para>
    </note>
@@ -147,7 +147,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
    <para>
     SQL92 uses <command>SELECT ... INTO</command> to represent selecting
     values into scalar variables of a host program, rather than creating
-    a new table.  This indeed is the usage found in PL/pgSQL and ecpg.
+    a new table.  This indeed is the usage found in <application>PL/pgSQL</application> and <xref linkend="app-ecpg">.
     The <productname>PostgreSQL</productname> usage of <command>SELECT
     INTO</command> to represent table creation is historical.  It's best
     to use <command>CREATE TABLE AS</command> for this purpose in new code.

doc/src/sgml/ref/set_session_auth.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_session_auth.sgml,v 1.3 2001/11/18 20:35:02 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_session_auth.sgml,v 1.4 2002/01/20 22:19:57 petere Exp $ -->
 <refentry id="SQL-SET-SESSION-AUTHORIZATION">
  <docinfo>
   <date>2001-04-21</date>
@@ -25,7 +25,7 @@ SET SESSION AUTHORIZATION '<parameter>username</parameter>'
 
   <para>
    This command sets the session user identifier and the current user
-   identifer of the current SQL-session context to be
+   identifier of the current SQL-session context to be
    <parameter>username</parameter>.
   </para>
 
@@ -34,7 +34,7 @@ SET SESSION AUTHORIZATION '<parameter>username</parameter>'
    authenticated) user name provided by the client.  The current user
    identifier is normally equal to the session user identifier, but
    may change temporarily in the context of <quote>setuid</quote>
-   functions and similar mechanisms.  The current user identifer is
+   functions and similar mechanisms.  The current user identifier is
    relevant for permission checking.
   </para>
 

doc/src/sgml/ref/set_transaction.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.7 2001/12/08 03:24:39 thomas Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.8 2002/01/20 22:19:57 petere Exp $ -->
 <refentry id="SQL-SET-TRANSACTION">
  <docinfo>
   <date>2000-11-24</date>
@@ -29,7 +29,7 @@ SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL
    This command sets the transaction isolation level.  The
    <command>SET TRANSACTION</command> command sets the characteristics
    for the current SQL-transaction. It has no effect on any subsequent
-   transactions.  This command cannot be used after the first DML
+   transactions.  This command cannot be used after the first query or data-modification
    statement (<command>SELECT</command>, <command>INSERT</command>,
    <command>DELETE</command>, <command>UPDATE</command>,
    <command>FETCH</command>, <command>COPY</command>) of a transaction
@@ -59,7 +59,7 @@ SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL
      <listitem>
       <para>
        The current transaction can only see rows committed before
-       first DML statement was executed in this transaction.
+       first query or data-modification statement was executed in this transaction.
       </para>
       <tip>
        <para>
@@ -101,7 +101,7 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>'
     <productname>PostgreSQL</productname> does not provide the
     isolation levels <option>READ UNCOMMITTED</option> 
     and <option>REPEATABLE READ</option>. Because
-    of multi-version concurrency control, the serializable level is not
+    of multiversion concurrency control, the serializable level is not
     truly serializable. See the <citetitle>User's Guide</citetitle> for
     details.
    </para>