Minor improvements in description of spilled counters in pg_stat_replication_slots...

Per a suggestion by Justin Pryzby.

Discussion: https://postgr.es/m/CA+fd4k5_pPAYRTDrO2PbtTOe0eHQpBvuqmCr8ic39uTNmR49Eg@mail.gmail.com

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index aeb694d4a86d76a062ed7915e827d2ecbafaeb11..313e44ed54987993b9de90bb62680b19ce319d5e 100644 (file)
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -2614,10 +2614,9 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
         <structfield>spill_count</structfield> <type>bigint</type>
        </para>
        <para>
-        Number of times transactions were spilled to disk while performing
-        decoding of changes from WAL for this slot. Transactions
-        may get spilled repeatedly, and this counter gets incremented on every
-        such invocation.
+        Number of times transactions were spilled to disk while decoding changes
+        from WAL for this slot. Transactions may get spilled repeatedly, and
+        this counter gets incremented on every such invocation.
       </para></entry>
      </row>
 
@@ -2628,8 +2627,8 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
        <para>
         Amount of decoded transaction data spilled to disk while performing
         decoding of changes from WAL for this slot. This and other spill
-        counters can be used to gauge the I/O occurred during logical decoding
-        and accordingly can tune <literal>logical_decoding_work_mem</literal>.
+        counters can be used to gauge the I/O which occurred during logical
+        decoding and allow tuning <literal>logical_decoding_work_mem</literal>.
       </para></entry>
      </row>