--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2484,9 +2484,9 @@ include_dir 'conf.d'
         In <literal>minimal</literal> level, no information is logged for
-        tables or indexes for the remainder of a transaction that creates or
-        truncates them.  This can make bulk operations much faster (see
-        <xref linkend="populate-pitr"/>).  But minimal WAL does not contain
-        enough information to reconstruct the data from a base backup and the
-        WAL logs, so <literal>replica</literal> or higher must be used to
-        enable WAL archiving (<xref linkend="guc-archive-mode"/>) and
-        streaming replication.
+        permanent relations for the remainder of a transaction that creates,
+        rewrites, or truncates them.  This can make bulk operations much
+        faster (see <xref linkend="populate-pitr"/>).  But minimal WAL does
+        not contain enough information to reconstruct the data from a base
+        backup and the WAL logs, so <literal>replica</literal> or higher must
+        be used to enable WAL archiving (<xref linkend="guc-archive-mode"/>)
+        and streaming replication.
        </para>
@@ -2891,9 +2891,9 @@ include_dir 'conf.d'
         When <varname>wal_level</varname> is <literal>minimal</literal> and a
-        transaction commits after creating or rewriting a permanent table,
-        materialized view, or index, this setting determines how to persist
-        the new data.  If the data is smaller than this setting, write it to
-        the WAL log; otherwise, use an fsync of the data file.  Depending on
-        the properties of your storage, raising or lowering this value might
-        help if such commits are slowing concurrent transactions.  The default
-        is two megabytes (<literal>2MB</literal>).
+        transaction commits after creating, rewriting, or truncating a
+        permanent relation, this setting determines how to persist the new
+        data.  If the data is smaller than this setting, write it to the WAL
+        log; otherwise, use an fsync of the data file.  Depending on the
+        properties of your storage, raising or lowering this value might help
+        if such commits are slowing concurrent transactions.  The default is
+        two megabytes (<literal>2MB</literal>).
        </para>