diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index f77e1fb673..5db6007899 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
@@ -179,15 +179,15 @@ NOTICE: Index index: Pages 28;
The open database is the target for VACUUM.
- We recommend that active production databases be cleaned nightly, in order
- to keep statistics relatively current. The VACUUM
- query may be executed at any time, however. In particular, after
- copying a large class into Postgres
- or after deleting a large number of
- records, it may be a good idea to issue a VACUUM ANALYZE
- query. This will update the system catalogs with the results of all
- recent changes, and allow the Postgres
- query optimizer to make better choices in planning user queries.
+ We recommend that active production databases be
+ VACUUMM-ed nightly, in order to keep remove
+ expired rows. After copying a large class into
+ Postgres or after deleting a large number
+ of records, it may be a good idea to issue a VACUUM
+ ANALYZE query. This will update the system catalogs with
+ the results of all recent changes, and allow the
+ Postgres query optimizer to make better
+ choices in planning user queries.