If you quote the following sentence also, you have the answer:
Events do not travel, they just occur. However, the term event is
often used metonymically to denote the notification message itself,
which may lead to some confusion.
From the context it is clear that the two other quotes are talking about the event notification message rather than the triggering event. It is common to use the word event to describe both the triggering event and the notification message.
The confusion does not stop here. In C# the keyword
Event-interface is the base interface for event notification objects. But the term event is also used for the event handlers, e.g. some documentation will use the term "the onlick event" when talking about the event handler which is invoked when the click event is triggered. During the browser wars, Internet Explorer introduced the
attachEvent() method which does (almost) exactly the same as
addEventListener() in the DOM standard. So the distinction between event and event listener is not clear in the API's either.
In short, the word "event" is used broadly to describe the various different parts which interact in an event driven architecture. So if you need to be precise, it is a good idea to use more specific terms like event notification object, event emitter, event listener and so on.