Yep, I knew about this going in and struggled to find something sane. So, the idea is, we want to remove whitespace only after the user stops typing / changing the document for a certain amount of time (2 seconds here). This means, what we're receiving, is the aggregate of n seconds worth of changes (i.e. if you power-code for 30 seconds straight, we might end up with quite a lot of changes to sift through). We have to do this, because if we try to immediately correct trailing whitespace, you literally couldn't type spaces.

The idea is, we don't have to be *super* accurate when calculating the range to fixup, we just don't want to go crazy over the entire document. I'll still use `x.After`, I just wanted to write more about the reasoning of this cray code :)