diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index 52f28bca7a..22966c06dc 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -125,11 +125,11 @@
If an INSERT contains an ON CONFLICT
DO UPDATE> clause, it is possible that the effects of all
row-level BEFORE> INSERT triggers
- and all row-level BEFORE UPDATE triggers can
+ and all row-level BEFORE UPDATE triggers can
both be applied in a way that is apparent from the final state of
the updated row, if an EXCLUDED> column is referenced.
There need not be an EXCLUDED> column reference for
- both sets of BEFORE row-level triggers to execute, though. The
+ both sets of row-level BEFORE triggers to execute, though. The
possibility of surprising outcomes should be considered when there
are both BEFORE> INSERT and
BEFORE> UPDATE row-level triggers
@@ -327,7 +327,7 @@
Statement-level triggers follow simple visibility rules: none of
the changes made by a statement are visible to statement-level
- triggers that are invoked before the statement, whereas all
+ BEFORE triggers, whereas all
modifications are visible to statement-level AFTER>
triggers.