From 28e8e2106983fc05e9415b078bcf6b158b49337e Mon Sep 17 00:00:00 2001
From: Justin Pryzby <pryzbyj@telsasoft.com>
Date: Mon, 4 Jul 2022 16:11:40 -0500
Subject: [PATCH] f

---
 doc/src/sgml/brin.sgml             | 28 ++++++++++++++--------------
 doc/src/sgml/ref/create_index.sgml |  2 +-
 2 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/doc/src/sgml/brin.sgml b/doc/src/sgml/brin.sgml
index 0a715d41c71..90897a4af07 100644
--- a/doc/src/sgml/brin.sgml
+++ b/doc/src/sgml/brin.sgml
@@ -76,17 +76,17 @@
   </para>
 
   <para>
-   There are several triggers for initial summarization of a page range
-   to occur.  If the table is vacuumed, either because
-   <xref linkend="sql-vacuum" /> has been manually invoked or because
-   autovacuum causes it,
+   There are several ways to trigger the initial summarization of a page range.
+   If the table is vacuumed, either manually or by
+   <link linkend="autovacuum">autovacuum</link>,
    all existing unsummarized page ranges are summarized.
-   Also, if the index has the
-   <xref linkend="index-reloption-autosummarize"/> parameter set to on,
-   then any run of autovacuum in the database will summarize all
-   unsummarized page ranges that have been completely filled recently,
-   regardless of whether the table is processed by autovacuum for other
-   reasons; see below.
+   Also, if the index's
+   <xref linkend="index-reloption-autosummarize"/> parameter is enabled,
+   whenever autovacuum runs in that database, summarization will
+   occur for all
+   unsummarized page ranges that have been filled,
+   regardless of whether the table itself is processed by autovacuum; see below.
+
    Lastly, the following functions can be used:
 
    <simplelist>
@@ -102,10 +102,10 @@
   </para>
 
   <para>
-   When autosummarization is enabled, each time a page range is filled a
-   request is sent to <literal>autovacuum</literal> for it to execute a targeted
-   summarization for that range, to be fulfilled at the end of the next
-   autovacuum worker run on the same database. If the request queue is full, the
+   When autosummarization is enabled, each time a page range is filled, a
+   request is sent to <literal>autovacuum</literal> to execute a targeted
+   summarization for that range, to be fulfilled the next time an autovacuum
+   worker finishes running in that database. If the request queue is full, the
    request is not recorded and a message is sent to the server log:
 <screen>
 LOG:  request for BRIN range summarization for index "brin_wi_idx" page 128 was not recorded
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index d3db03278d6..a5bac9f7373 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -578,7 +578,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
     </term>
     <listitem>
     <para>
-     Defines whether a summarization run is invoked for the previous page
+     Defines whether a summarization run is queued for the previous page
      range whenever an insertion is detected on the next one.
      See <xref linkend="brin-operation"/> for more details.
      The default is <literal>off</literal>.
-- 
2.17.1