Clarifications to Device specification and consistent terminology (#197)

* Ensure consistent terminology with binary protocol
* Clarify that reply must be sent before rebooting
* Clarify dump bit behavior
* Indicate device name payload type is array

This is an alternative to explicitly specifying the length in the title
while maintaining good readability in document TOC.

* Fix core register backlinks and naming convention
* Ensure R_WHO_AM_I spec is consistent with core.yml
* Clarify alternative to ALIVE_EN bit
* Clarify that the R_HEARTBEAT event is mandatory
* Improve formatting and table punctuation
* Use consistent notation for array registers
* Missing requirements language
* Clarify wording of INTERFACE_HASH
* Use consistent wording for references to WHO_AM_I

Author: glopesdev