Copy-edit vacuuumdb --analyze-in-stages doc blurb

I had made a few typos, and Nikolai Berkoff made a wording change
suggestion.

Discussion: https://postgr.es/m/VMwe7-sGegrQPQ7fJjSCdsEbESKeJFOb6G4DFxxNrf45I7DzHio7sNUH88wWRMnAy5a5G0-FB31dxPM47ldigW6WdiCPncHgqO9bNl6F240=@pm.me

diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml
index d8cbf0e189d98a3a700834dcbee8ebe2e53e07ea..956c0f01cbc741d624c15bfac619543976865002 100644 (file)
--- a/doc/src/sgml/ref/vacuumdb.sgml
+++ b/doc/src/sgml/ref/vacuumdb.sgml
@@ -397,7 +397,7 @@ PostgreSQL documentation
       <listitem>
        <para>
         Only calculate statistics for use by the optimizer (no vacuum),
-        like <option>--analyze-only</option>.  Run several (currently three)
+        like <option>--analyze-only</option>.  Run three
         stages of analyze; the first stage uses the lowest possible statistics
         target (see <xref linkend="guc-default-statistics-target"/>)
         to produce usable statistics faster, and subsequent stages build the
@@ -405,10 +405,10 @@ PostgreSQL documentation
        </para>
 
        <para>
-        This option is only useful to analyze a database that current has
-        no statistics or wholly incorrect ones, such as if it is newly
+        This option is only useful to analyze a database that currently has
+        no statistics or has wholly incorrect ones, such as if it is newly
         populated from a restored dump or by <command>pg_upgrade</command>.
-        Be aware that running this option in a database with existing
+        Be aware that running with this option in a database with existing
         statistics may cause the query optimizer choices to become
         transiently worse due to the low statistics targets of the early
         stages.