Confusion about inmemoryBlockedOnConsumed
I'm having a hard time figuring out how `points` and `inmemoryBlockedOnConsumed` complement each other.

From my understanding, [after reading this page](https://github.com/animir/node-rate-limiter-flexible/wiki/In-memory-Block-Strategy#setup-in-memory-block-strategy), once `points` expire, we start consuming `inmemoryBlockedOnConsumed` points and once those expire, we block the key in memory (in the example `points` and `inmemoryBlockedOnConsumed` are both `5`, hence the `if 10 or more points are consumed` we block it.

However, [in this part of the docs](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#apply-in-memory-block-strategy-to-avoid-extra-requests-to-store),  it gives the idea that once the `300` points expire the key will be blocked in memory, so which one is it?

Since `inmemoryBlockedOnConsumed`'s default is 0, it gives the ideia that once `points` expire we immediately block the key in memory, which seems a sensible default. I'm having a hard time understanding why we would want to allow more updates to the store before the in-memory block, is it simply to avoid the latency of removing the in-memory block?