With the addition of proposer-based timestamps to Tendermint, we should add a high-level explanation document so that users of v0.36 can get an understanding of how the system is effected by the new algorithm. This document will aim to clarify what operators need to do ahead of v0.36 to prepare for the change when updating so as to avoid causing any issues with their chains. This document should also document how an application may change the consensus parameters to be more loose in case they need the chain to make progress in the event of poorly synced clocks or large message delays.