resilience based on message replay and some fixes

- remove extraneous “to”
- clarify wording of responsiveness effect of non-blocking nature
- add resource insulation to stay responsive during over-load
- remark that location transparency and message passing enable seamless
  recovery after total failure, even at a remote location