UML22 — AcceptEventAction - inconsistencies in Semantics and typos

AcceptEventAction - inconsistencies in Semantics and typos "If the event is a SignalEvent, the result token contains a signal object whose reception by the owning object caused the event. Signal objects may be copied in transmission and storage by the owning object, so identity might not be preserved. An action whose event is a signal event is informally called an accept signal action. If the event is a TimeEvent, the result token contains the time at which the event occurred. Such an action is informally called a wait time action. If the event is a ChangeEvent ot a CallEvent, the result is a control token, there are no output pins. See CommonBehavior for a description of Event specifications." - There is no metaclass SignalEvent. Probably, this should be SignalTrigger. - There is no metaclass TimeEvent. Probably, this should be TimeTrigger. - There is no metaclass ChangeEvent. Probably, this should be ChangeTrigger. - There is no metaclass CallEvent. Probably, this should be CallTrigger. Suggestion for editorial change: "If the trigger is a SignalTrigger, the result token contains a signal object whose reception by the owning object caused the event. Signal objects may be copied in transmission and storage by the owning object, so identity might not be preserved. An action whose trigger is a SignalTrigger is informally called an accept signal action. If the trigger is a TimeTrigger, there is exactly one output pin which contains the time at which the event occurred. Such an action is informally called a wait time action. If the trigger is a ChangeTrigger, the result is a control token, there are no output pins. See CommonBehavior for a description of Trigger specifications."

See resolution to 7399. Suggested editorial change has the same text as the FAS.