Update wording and cleanup for new items.

diff --git a/doc/FAQ b/doc/FAQ
index faf7a59c93dc2ea26398c7e4c334a66d8ba93f5a..3afcbb33be81656920f8faa5382a1379b9e54b72 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
                 Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Tue Nov 22 10:21:51 EST 2005
+   Last updated: Tue Nov 22 10:31:18 EST 2005
    
    Current maintainer: Bruce Momjian ([email protected])
    
@@ -212,8 +212,8 @@
           + Debugging information
           + Debugger backtrace output
      * The bug is new. The following might happen:
-          + A patch has been created and will be included in the next
-            major or minor release
+          + A patch is created and will be included in the next major or
+            minor release
           + The bug cannot be fixed immediately and is added to the TODO
             list
        
@@ -236,9 +236,9 @@
    efficient to respond directly to email and keep the TODO list
    up-to-date. In practice, bugs don't last very long in the software,
    and bugs that affect a large number of users are fixed rapidly. The
-   only single place to find all changes, improvements, and fixes in a
-   PostgreSQL release is to read our CVS logs messages. Even the release
-   notes do not contain every change made to the software.
+   only place to find all changes, improvements, and fixes in a
+   PostgreSQL release is to read the CVS log messages. Even the release
+   notes do not list every change made to the software.
    
   1.10) What documentation is available?
   

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 634286dc82937e7544b54dc2e81fe7e7031b5c13..8bf6153c789186b727b92f4cfc1ee51a46b3850c 100644 (file)
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
   alink="#0000ff">
     Frequently Asked Questions (FAQ) for PostgreSQL
 
-    Last updated: Tue Nov 22 10:21:51 EST 2005
+    Last updated: Tue Nov 22 10:31:18 EST 2005
 
     Current maintainer: Bruce Momjian (
     "mailto:[email protected]">[email protected])
@@ -272,7 +272,7 @@
     
     The bug is new.  The following might happen:
         
-   A patch has been created and will be included in the next major 
+   A patch is created and will be included in the next major 
    or minor release
    The bug cannot be fixed immediately and is added
    to the TODO
@@ -312,10 +312,11 @@
     TODO
     list up-to-date. In practice, bugs don't last very long in the
     software, and bugs that affect a large number of users are fixed
-    rapidly. The only single place to find all changes, improvements,
-    and fixes in a PostgreSQL release is to read our CVS logs messages.
-    Even the release notes do not contain every change made to the
-    software.
+    rapidly. The only place to find all changes, improvements, and
+    fixes in a PostgreSQL release is to read the
+    CVS
+    log messages.  Even the release notes do not list every change
+    made to the software.
     
     1.10) What documentation is available?