diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index 3df32b58ee6..c582021d29d 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -377,15 +377,11 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ <replaceable class="paramet
    </para>
 
    <para>
-    We recommend that active production databases be
-    vacuumed frequently (at least nightly), in order to
-    remove dead rows. After adding or deleting a large number
-    of rows, it might be a good idea to issue a <command>VACUUM
-    ANALYZE</command> command for the affected table. This will update the
-    system catalogs with
-    the results of all recent changes, and allow the
-    <productname>PostgreSQL</productname> query planner to make better
-    choices in planning queries.
+    We recommend that all databases be vacuumed regularly in
+    order to remove dead rows.  <productname>PostgreSQL</productname> includes
+    an <quote>autovacuum</quote> facility which can automate routine vacuum
+    maintenance.  For more information about automatic and manual vacuuming,
+    see <xref linkend="routine-vacuuming"/>.
    </para>
 
    <para>
@@ -412,12 +408,6 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ <replaceable class="paramet
     details.
    </para>
 
-   <para>
-    <productname>PostgreSQL</productname> includes an <quote>autovacuum</quote>
-    facility which can automate routine vacuum maintenance.  For more
-    information about automatic and manual vacuuming, see
-    <xref linkend="routine-vacuuming"/>.
-   </para>
    <para>
     Each backend running <command>VACUUM</command> without the
     <literal>FULL</literal> option will report its progress in the