diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index e9214dc..4361cdd 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -125,18 +125,17 @@
    <para>
     The execution of an <literal>AFTER</literal> trigger can be deferred
     to the end of the transaction, rather than the end of the statement,
     if it was defined as a <firstterm>constraint trigger</firstterm>.
     In all cases, a trigger is executed as part of the same transaction as
     the statement that triggered it, so if either the statement or the
     trigger causes an error, the effects of both will be rolled back.
-    Also, the trigger will always run in the security context of the role
-    that executed the statement that caused the trigger to fire, unless
-    the trigger function is defined as <literal>SECURITY DEFINER</literal>,
-    in which case it will run as the function owner.
+    Also, the trigger will always run as the role that queued the trigger
+    event, unless the trigger function is defined as <literal>SECURITY
+    DEFINER</literal>, in which case it will run as the function owner.
    </para>
 
    <para>
     If an <command>INSERT</command> contains an <literal>ON CONFLICT
     DO UPDATE</literal> clause, it is possible for row-level
     <literal>BEFORE</literal> <command>INSERT</command> and then
     <literal>BEFORE</literal> <command>UPDATE</command> triggers