Minor fixups for markup and wording.

diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml
index 6f802346fdd71cdb770a69ce0e14bfd7e462e9f1..b72a213e7e387863c21c255a622e2d2b8a950747 100644 (file)
--- a/doc/src/sgml/ref/create_sequence.sgml
+++ b/doc/src/sgml/ref/create_sequence.sgml
@@ -1,5 +1,5 @@
 
 
@@ -210,7 +210,7 @@ ERROR:  DefineSequence: MINVALUE (min
   
   
    CREATE SEQUENCE will enter a new sequence number generator
-   into the current data base. This involves creating and initialising a
+   into the current data base. This involves creating and initializing a
    new single-row
    table with the name seqname.
    The generator will be "owned" by the user issuing the command.
@@ -238,20 +238,19 @@ ERROR:  DefineSequence: MINVALUE (min
    Use a query like
 
    
-SELECT * FROM sequence_name;
+SELECT * FROM seqname;
    
 
    to get the parameters of a sequence.
 
-   Aside from fetching the original
-   parameters, you can use
+   As an alternative to fetching the
+   parameters from the original definition as above, you can use
 
    
-SELECT last_value FROM sequence_name;
+SELECT last_value FROM seqname;
    
 
    to obtain the last value allocated by any backend.
-   parameters, you can use
   
 
   
@@ -263,7 +262,7 @@ SELECT last_value FROM sequence_name;
    
     Unexpected results may be obtained if a cache setting greater than one
     is used for a sequence object that will be used concurrently by multiple
-    backends.  Each backend will allocate "cache" successive sequence values
+    backends.  Each backend will allocate and cache successive sequence values
     during one access to the sequence object and increase the sequence
     object's last_value accordingly.  Then, the next cache-1 uses of nextval
     within that backend simply return the preallocated values without touching
@@ -291,7 +290,7 @@ SELECT last_value FROM sequence_name;
     Notes
    
    
-    Refer to the DROP SEQUENCE statement to remove a sequence.
+    Use DROP SEQUENCE to remove a sequence.
    
    
     Each backend uses its own cache to store allocated numbers.

diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
index c41ad4bfe875aa48b09350f002b034ab0a2669ba..98ade29ff3062553fdfb21c66f003db39dbd3bb1 100644 (file)
--- a/doc/src/sgml/ref/postgres-ref.sgml
+++ b/doc/src/sgml/ref/postgres-ref.sgml
@@ -1,5 +1,5 @@
 
 
@@ -125,7 +125,8 @@ postgres [ -B nBuffers ] [ -C ] [ -
       
        
    Override restrictions, so system table structures can be modified.
-   These tables are typically those with a leading "pg_" in the table name.
+   These tables are typically those with a leading
+   "pg_" in the table name.
        
       
      
@@ -134,9 +135,11 @@ postgres [ -B nBuffers ] [ -C ] [ -
       -P
       
        
-   Ignore system indexes to scan/update system tuples. Reindex command
-   for system table/indexes requires this option. System tables are
-   typically those with a leading "pg_" in the table name.
+   Ignore system indexes to scan/update system
+   tuples. REINDEX for system tables/indexes
+   requires this option. System tables are
+   typically those with a leading "pg_" in the
+   table name.