Minor SGML markup fixes.

doc/src/sgml/config.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.16 2005/09/13 01:51:18 alvherre Exp $
+$PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.17 2005/09/13 15:24:56 neilc Exp $
 -->
 <chapter Id="runtime-config">
   <title>Run-time Configuration</title>
@@ -1715,20 +1715,20 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"'  # Windows
        <para>
         Sets the planner's assumption about the effective size of the
         disk cache that is available to a single index scan.  This is
-        factored into estimates of the cost of using an index; a higher
-        value makes it more likely index scans will be used, a lower
-        value makes it more likely sequential scans will be used. When
-        setting this parameter you should consider both
+        factored into estimates of the cost of using an index; a
+        higher value makes it more likely index scans will be used, a
+        lower value makes it more likely sequential scans will be
+        used. When setting this parameter you should consider both
         <productname>PostgreSQL</productname>'s shared buffers and the
         portion of the kernel's disk cache that will be used for
-        <productname>PostgreSQL</productname> data files.  Also, take into
-        account the expected number of concurrent queries using different
-        indexes, since they will have to share the available space.
-        This parameter has no effect on the size of shared memory
-        allocated by PostgreSQL, nor does it reserve kernel disk cache;
-        it is used only for estimation purposes.
-        The value is measured in disk pages, which are
-        normally 8192 bytes each. The default is 1000.
+        <productname>PostgreSQL</productname> data files.  Also, take
+        into account the expected number of concurrent queries using
+        different indexes, since they will have to share the available
+        space.  This parameter has no effect on the size of shared
+        memory allocated by <productname>PostgreSQL</productname>, nor
+        does it reserve kernel disk cache; it is used only for
+        estimation purposes.  The value is measured in disk pages,
+        which are normally 8192 bytes each. The default is 1000.
        </para>
       </listitem>
      </varlistentry>
@@ -3662,7 +3662,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
         determines whether OIDs will be included in tables created by
         <command>SELECT INTO</command>. In <productname>PostgreSQL</>
         8.1 <varname>default_with_oids</> is disabled by default; in
-        prior versions of PostgreSQL, it was on by default.
+        prior versions of <productname>PostgreSQL</productname>, it
+        was on by default.
        </para>
 
        <para>

doc/src/sgml/datatype.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.158 2005/05/30 19:32:44 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.159 2005/09/13 15:24:56 neilc Exp $
 -->
 
  <chapter id="datatype">
@@ -1770,7 +1770,7 @@ January 8 04:05:06 1999 PST
       literals be explicitly typed:
       <programlisting>TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'</programlisting>
       If a literal is not explicitly indicated as being of <type>timestamp with time zone</type>,
-      PostgreSQL will silently ignore any time zone indication in the literal.
+      <productname>PostgreSQL</productname> will silently ignore any time zone indication in the literal.
       That is, the resulting date/time value is derived from the date/time
       fields in the input value, and is not adjusted for time zone.
      </para>

doc/src/sgml/ref/alter_sequence.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.10 2005/08/01 16:11:14 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.11 2005/09/13 15:24:57 neilc Exp $
 PostgreSQL documentation
 -->
 
@@ -132,7 +132,7 @@ ALTER SEQUENCE <replaceable class="parameter">name</replaceable> SET SCHEMA <rep
      </varlistentry>
 
      <varlistentry>
-      <term>CYCLE</term>
+      <term><literal>CYCLE</literal></term>
       <listitem>
        <para>
         The optional <literal>CYCLE</literal> key word may be used to enable
@@ -150,7 +150,7 @@ ALTER SEQUENCE <replaceable class="parameter">name</replaceable> SET SCHEMA <rep
      </varlistentry>
 
      <varlistentry>
-      <term>NO CYCLE</term>
+      <term><literal>NO CYCLE</literal></term>
       <listitem>
        <para>
         If the optional <literal>NO CYCLE</literal> key word is
@@ -197,7 +197,7 @@ ALTER SEQUENCE serial RESTART WITH 105;
 
   <para>
    <command>ALTER SEQUENCE</command> will not immediately affect
-   <literal>nextval</> results in backends,
+   <function>nextval</> results in backends,
    other than the current one, that have preallocated (cached) sequence
    values. They will use up all cached values prior to noticing the changed
    sequence parameters.  The current backend will be affected immediately.