From e885554c8dd8c91a216baf9d5f1c00cdfdfba1d2 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 23 Sep 2005 02:42:34 +0000
Subject: [PATCH] Clarify autovacuum wording.

---
 doc/src/sgml/release.sgml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 04e62d3d8a..4a8b6a0b85 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.372 2005/09/23 02:25:35 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.373 2005/09/23 02:42:34 momjian Exp $
 
 Typical markup:
 
@@ -177,9 +177,9 @@ pg_[A-Za-z0-9_]                 <application>
         Integrating autovacuum into the server allows it to be
         automatically started and stopped in sync with the database
         server, and allows autovacuum to be configured from
-        <filename>postgresql.conf</>.  Autovacuum now checks to see if
-        the database is in danger of xid wraparound and
-        <command>VACUUM</command>s the whole database if needed.
+        <filename>postgresql.conf</>.  Also autovacuum now checks
+        if the database is in danger of xid wraparound and
+        vacuums the database if needed.
        </para>
       </listitem>
      </varlistentry>