I know just enough about GNU/Linux I/O to be dangerous, so I can start to build an inkling of understanding based on this information: "watching" a file descriptor is probably how we register event listeners, and "edge vs. level" is most likely a decision about when handlers receive their data. But that's about as far as I can get before I have to start descending into the terms I don't completely understand. When I find something that explains those, it will probably rely on a bunch of other terms that I must descend into, and so forth. By the time I finally recurse all the way back up to my original quest for knowledge ("What does event-driven mean?"), I will be so inundated with new information that nothing sticks!
Thanks for the suggestion about Twisted, EM and Node.js... I'll have to make some time to play with them soon.
Even just playing with writing some meaningful client-side JavaScript will be enough to give you more of a 'feel' for event-driven programming...
It's not going to give you a huge amount of knowledge straight out but it will definitely give you enough to get you started if you decide to go further.