From 753efc10085c9d681a70718b0e2c622fad139efd Mon Sep 17 00:00:00 2001
From: Aleksander Alekseev <aleksander@tigerdata.com>
Date: Tue, 7 Apr 2026 14:48:15 +0300
Subject: [PATCH v1] Improve wording in the documentation added by 1ff3180ca016

Author: Aleksander Alekseev <aleksander@tigerdata.com>
Discussion: https://postgr.es/m/CACG=ezZOrNsuLoETLD1gAswZMuH2nGGq7Ogcc0QOE5hhWaw=cw@mail.gmail.com
---
 doc/src/sgml/maintenance.sgml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 652b291de15..35dd7bc9c18 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -1188,11 +1188,11 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
     relation that support parallel vacuum.  For manual <command>VACUUM</command>,
     this is limited by the <literal>PARALLEL</literal> option, which is
     further capped by <xref linkend="guc-max-parallel-maintenance-workers"/>.
-    For autovacuum, it is limited by the table's
-    <xref linkend="reloption-autovacuum-parallel-workers"/> if any which is
-    capped limited by
-    <xref linkend="guc-autovacuum-max-parallel-workers"/> parameter.  Please
-    note that it is not guaranteed that the number of parallel workers that was
+    For autovacuum, it is limited by
+    <xref linkend="guc-autovacuum-max-parallel-workers"/>, which can be
+    further reduced on a per-table basis using the
+    <xref linkend="reloption-autovacuum-parallel-workers"/> storage parameter.
+    Please note that it is not guaranteed that the number of parallel workers that was
     calculated will be used during execution.  It is possible for a vacuum to
     run with fewer workers than specified, or even with no workers at all.
    </para>
-- 
2.43.0

