From 773d02724c8aa4294f46b183afccd021be9dd610 Mon Sep 17 00:00:00 2001
From: Justin Pryzby <pryzbyj@telsasoft.com>
Date: Tue, 15 Mar 2022 13:38:08 -0500
Subject: [PATCH 3/3] f!3

---
 doc/src/sgml/maintenance.sgml | 10 +++++-----
 doc/src/sgml/ref/analyze.sgml | 12 ++++++------
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 9e6909cd748..34d72dba784 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -295,8 +295,8 @@
     analyze on the parent table.  If the parent table is empty or rarely
     changed, it may never be processed by autovacuum, and the statistics for
     the inheritance tree as a whole won't be collected. It is necessary to
-    run <command>ANALYZE</command> on the parent table manually, to keep
-    the statistics up to date.
+    run <command>ANALYZE</command> on the parent table manually in order to
+    keep the statistics up to date.
    </para>
 
    <para>
@@ -359,11 +359,11 @@
 
    <tip>
     <para>
-     The autovacuum daemon may not issue <command>ANALYZE</command> commands
+     The autovacuum daemon does not issue <command>ANALYZE</command> commands
      for partitioned tables.  Inheritance parents will only be analyzed if the
      parent itself is changed - changes to child tables do not trigger
      autoanalyze on the parent table.  If your queries require statistics on
-     parent tables for proper planning, it's necessary to periodically run
+     parent tables for proper planning, it is necessary to periodically run
      a manual <command>ANALYZE</command> on those tables to keep the statistics
      up to date.
     </para>
@@ -844,7 +844,7 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
    <para>
     Partitioned tables are not processed by autovacuum.  Statistics
     should be collected by running a manual <command>ANALYZE</command> when it is
-    first populated, and updated whenever the distribution of data in its
+    first populated, and again whenever the distribution of data in its
     partitions changes significantly.
    </para>
 
diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml
index 764cfb19718..8268ba87f63 100644
--- a/doc/src/sgml/ref/analyze.sgml
+++ b/doc/src/sgml/ref/analyze.sgml
@@ -267,22 +267,22 @@ ANALYZE [ VERBOSE ] [ <replaceable class="parameter">table_and_columns</replacea
     sampling rows from all partitions; in addition, it will recurse into each
     partition and update its statistics.  Each leaf partition is analyzed only
     once, even with multi-level partitioning.  No statistics are collected for
-    the parent table (ignoring data from partitions), because with partitioning
-    it's guaranteed to be empty.
+    only the parent table (without data from its partitions), because with
+    partitioning it's guaranteed to be empty.
   </para>
 
   <para>
     By constrast, if the table being analyzed has inheritance children,
-    <command>ANALYZE</command> gathers two sets of statistics: once on the rows
-    of the parent table only, and a second one including rows of both the parent
+    <command>ANALYZE</command> gathers two sets of statistics: one on the rows
+    of the parent table only, and a second including rows of both the parent
     table and all of its children.  This second set of statistics is needed when
-    planning queries that process the whole inheritance tree at once.  The child
+    planning queries that process the inheritance tree as a whole.  The child
     tables themselves are not individually analyzed in this case.
   </para>
 
   <para>
     The autovacuum daemon does not process partitioned tables, nor does it
-    process inheritance parents due to modifications to its child tables.
+    process inheritance parents if only the children are ever modified.
     It is usually necessary to periodically run a manual
     <command>ANALYZE</command> to keep the statistics of the table hierarchy
     up to date.
-- 
2.17.1