Minor SGML improvements.

diff --git a/doc/src/sgml/ref/alter_domain.sgml b/doc/src/sgml/ref/alter_domain.sgml
index 6b84902fe1c543e6ddfbe5e28d8d37e72646c614..7ecee65021c72b5920c2b3c5536f3cc61fbf1bb0 100644 (file)
--- a/doc/src/sgml/ref/alter_domain.sgml
+++ b/doc/src/sgml/ref/alter_domain.sgml
@@ -1,5 +1,5 @@
 
 
@@ -139,7 +139,7 @@ ALTER DOMAIN name
      
 
      
-      CASCADE
+      CASCADE
       
        
         Automatically drop objects that depend on the constraint.
@@ -148,7 +148,7 @@ ALTER DOMAIN name
      
 
      
-      RESTRICT
+      RESTRICT
       
        
         Refuse to drop the constraint if there are any dependent
@@ -174,11 +174,11 @@ ALTER DOMAIN name
   Examples
 
   
-   To add a NOT NULL constraint to a domain:
+   To add a NOT NULL constraint to a domain:
    
 ALTER DOMAIN zipcode SET NOT NULL;
    
-   To remove a NOT NULL constraint from a domain:
+   To remove a NOT NULL constraint from a domain:
    
 ALTER DOMAIN zipcode DROP NOT NULL;
    

diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml
index 9fd5cab253fb8b0cae46bca0d0c4a6e82588a59e..ff375e01f97e0ba35898b0f848b381a42240b5b8 100644 (file)
--- a/doc/src/sgml/ref/cluster.sgml
+++ b/doc/src/sgml/ref/cluster.sgml
@@ -1,5 +1,5 @@
 
 
@@ -129,9 +129,10 @@ CLUSTER
    
 
    
-    Because the planner records statistics about the ordering of tables, it
-    is advisable to run ANALYZE on the newly clustered
-    table.  Otherwise, the planner may make poor choices of query plans.
+    Because the planner records statistics about the ordering of
+    tables, it is advisable to run 
+    endterm="sql-analyze-title"> on the newly clustered table.
+    Otherwise, the planner may make poor choices of query plans.
    
 
    
@@ -175,7 +176,7 @@ CLUSTER emp_ind ON emp;
   
 
   
-   Cluster the employees relation using the same
+   Cluster the employees table using the same
    index that was used before:
 
 CLUSTER emp;


diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml

index 667a6df2bbf1047d707345c5165e39c243b038a8..8bd220f77a7fb7df20b2aa8cd6807849efce6a5c 100644 (file)

--- a/doc/src/sgml/ref/truncate.sgml
+++ b/doc/src/sgml/ref/truncate.sgml
@@ -1,5 +1,5 @@
 
 
@@ -60,8 +60,8 @@ TRUNCATE [ TABLE ] name
   
 
   
-   TRUNCATE will not run any user-defined ON DELETE triggers
-   that might exist for the table.
+   TRUNCATE will not run any user-defined ON
+   DELETE triggers that might exist for the table.
   
  
 


diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml

index 5cee5f991f99e60bbab9edc458987383c4ceff9c..930ce7e3bac988f82bc4efa0d83981a5042c1693 100644 (file)

--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 
 
@@ -64,14 +64,14 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ 
   
 
   
-   <command>FREEZE> is a special-purpose option that
+   <literal>FREEZE> is a special-purpose option that
    causes tuples to be marked frozen as soon as possible,
    rather than waiting until they are quite old.  If this is done when there
    are no other open transactions in the same database, then it is guaranteed
    that all tuples in the database are frozen and will not be
    subject to transaction ID wraparound problems, no matter how long the
    database is left unvacuumed.
-   <command>FREEZE> is not recommended for routine use.  Its only
+   <literal>FREEZE> is not recommended for routine use.  Its only
    intended usage is in connection with preparation of user-defined template
    databases, or other databases that are completely read-only and will not
    receive routine maintenance VACUUM operations.

diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index 667a6df2bbf1047d707345c5165e39c243b038a8..8bd220f77a7fb7df20b2aa8cd6807849efce6a5c 100644 (file)
--- a/doc/src/sgml/ref/truncate.sgml
+++ b/doc/src/sgml/ref/truncate.sgml
@@ -1,5 +1,5 @@
 
 
@@ -60,8 +60,8 @@ TRUNCATE [ TABLE ] name
   
 
   
-   TRUNCATE will not run any user-defined ON DELETE triggers
-   that might exist for the table.
+   TRUNCATE will not run any user-defined ON
+   DELETE triggers that might exist for the table.
   
  
 

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index 5cee5f991f99e60bbab9edc458987383c4ceff9c..930ce7e3bac988f82bc4efa0d83981a5042c1693 100644 (file)
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 
 
@@ -64,14 +64,14 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ 
   
 
   
-   <command>FREEZE> is a special-purpose option that
+   <literal>FREEZE> is a special-purpose option that
    causes tuples to be marked frozen as soon as possible,
    rather than waiting until they are quite old.  If this is done when there
    are no other open transactions in the same database, then it is guaranteed
    that all tuples in the database are frozen and will not be
    subject to transaction ID wraparound problems, no matter how long the
    database is left unvacuumed.
-   <command>FREEZE> is not recommended for routine use.  Its only
+   <literal>FREEZE> is not recommended for routine use.  Its only
    intended usage is in connection with preparation of user-defined template
    databases, or other databases that are completely read-only and will not
    receive routine maintenance VACUUM operations.