A recipe-style program runs its lines in order and finishes: read two numbers, add them, print the sum. A game cannot work that way. It has no idea when the player will press the space bar, or whether they will press it at all. So instead of a fixed order, the program says in advance: when the space bar is pressed, run jump. That pairing of an event (space bar pressed) with a handler (jump) is set up once, and then the program waits.
Each event carries a little information: a click event says where the pointer was, and a key event says which key. In Scratch, the block 'when this sprite clicked' is an event and the blocks under it are the handler. In JavaScript, button.addEventListener('click', showMessage) attaches the handler showMessage to the button's click event. Click three times and showMessage runs three times; do not click and it never runs.
Not everything that changes is an event. A loop that checks the score 60 times a second is the program asking a question over and over, not reacting to a signal. A calculation that runs line by line after the program starts is plain sequence. What marks an event is that something outside the program's own steps, a person, the clock or the network, decides when the code runs.
Think of it like this. A doorbell works like an event: nobody checks the porch every minute; when a visitor presses the button, the chime (the handler) sounds. Wire the button to nothing and the press still happens but nobody hears it, just like an event with no handler attached. One difference: a single program event can trigger several handlers.
Core idea. Event-driven programs wait for things to happen rather than following a fixed sequence.