[css-animations-2] Nope, the trigger state actually does live on the trigger, duh.

Author: tabatkins

css-animations-2/Overview.bs

@@ -889,7 +889,7 @@ or leaves the trigger's <dfn export for="timeline trigger">exit range</dfn>.
 It is defined on an element with the 'timeline-trigger' shorthand property,
 or its longhands.
 
-A [=timeline trigger=] [=trigger instance=] has a binary <dfn export for="timeline trigger">trigger state</dfn> associated with it;
+A [=timeline trigger=] has a binary <dfn export for="timeline trigger">trigger state</dfn> associated with it;
 it is initially "untriggered".
 While it's "untriggered",
 the associated [=timeline=] entering (or starting in) the trigger's [=enter range=]
@@ -1113,10 +1113,9 @@ An [=event trigger=] can be defined as either stateless or stateful:
 [=Event triggers=] are activated when one of its associated {{Event}}s are fired on the page
 with the trigger-defining element as its {{Event/target}}.
 If it's stateful,
-then its [=trigger instance=] has a binary <dfn export for="event trigger">trigger state</dfn>
-associated with it,
+it has a binary <dfn export for="event trigger">trigger state</dfn> associated with it,
 initially "untriggered":
-while "untriggered", it only activates when the [=event trigger=] receives one of its [=enter events=],
+while "untriggered", it only activates when the defining element receives one of its [=enter events=],
 performing an associated <dfn export for="event trigger">enter action</dfn>
 and switching its [=event trigger/trigger state=] to "triggered";
 while "triggered", it only activates when it receives one of its [=exit events=],