diff --git a/doc/src/sgml/event-trigger.sgml b/doc/src/sgml/event-trigger.sgml
index c10627554bd..1197de78d02 100644
--- a/doc/src/sgml/event-trigger.sgml
+++ b/doc/src/sgml/event-trigger.sgml
@@ -147,13 +147,15 @@
     <title>table_rewrite</title>
 
    <para>
-    The <literal>table_rewrite</literal> event occurs just before a table is
-    rewritten by some actions of the commands <literal>ALTER TABLE</literal> and
-    <literal>ALTER TYPE</literal>.  While other
-    control statements are available to rewrite a table,
+    The <literal>table_rewrite</literal> event occurs just before a table or
+    materialized view is rewritten by some actions of the commands
+    <literal>ALTER TABLE</literal> and <literal>ALTER MATERIALIZED VIEW</literal>.
+    It can also be triggered by <literal>ALTER TYPE</literal> when a change to
+    a composite type causes one of its typed tables to be rewritten.
+    While other control statements are available to rewrite a relation,
     like <literal>CLUSTER</literal> and <literal>VACUUM</literal>,
     the <literal>table_rewrite</literal> event is not triggered by them.
-    To find the OID of the table that was rewritten, use the function
+    To find the OID of the relation being rewritten, use the function
     <literal>pg_event_trigger_table_rewrite_oid()</literal>, to discover the
     reason(s) for the rewrite, use the function
     <literal>pg_event_trigger_table_rewrite_reason()</literal> (see <xref