Minor SGML markup fixes.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 4d65dd6b8054b0d1986ff30944c3fc14499209a2..69bdc0d4a1fe9cf449543ed7b0b67adfa2cf9972 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,5 +1,5 @@
 
 
   Run-time Configuration
@@ -1715,20 +1715,20 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"'  # Windows
        
         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
         PostgreSQL's shared buffers and the
         portion of the kernel's disk cache that will be used for
-        PostgreSQL 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.
+        PostgreSQL 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.
        
       
      
@@ -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
         SELECT INTO. In PostgreSQL
         8.1 default_with_oids is disabled by default; in
-        prior versions of PostgreSQL, it was on by default.
+        prior versions of PostgreSQL, it
+        was on by default.
        
 
        

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index cea45aa7e518f88a6d278faf3a13d4735c5be8e5..099f5e8ab671b2c44505c1eabea6da2844293b29 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -1770,7 +1770,7 @@ January 8 04:05:06 1999 PST
       literals be explicitly typed:
       TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
       If a literal is not explicitly indicated as being of timestamp with time zone,
-      PostgreSQL will silently ignore any time zone indication in the literal.
+      PostgreSQL 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.
      

diff --git a/doc/src/sgml/ref/alter_sequence.sgml b/doc/src/sgml/ref/alter_sequence.sgml
index 413dfbdde633a3553590a7fbe76caae89b055ab0..4ab3db3ead1ca6e831536ade309f5603f20f1942 100644 (file)
--- a/doc/src/sgml/ref/alter_sequence.sgml
+++ b/doc/src/sgml/ref/alter_sequence.sgml
@@ -1,5 +1,5 @@
 
 
@@ -132,7 +132,7 @@ ALTER SEQUENCE name SET SCHEMA 
      
 
      
-      CYCLE
+      CYCLE
       
        
         The optional CYCLE key word may be used to enable
@@ -150,7 +150,7 @@ ALTER SEQUENCE name SET SCHEMA 
      
 
      
-      NO CYCLE
+      NO CYCLE
       
        
         If the optional NO CYCLE key word is
@@ -197,7 +197,7 @@ ALTER SEQUENCE serial RESTART WITH 105;
 
   
    ALTER SEQUENCE 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.