Update adr-016-validator-consensus-key-rotation.md

Author: CreeptoGengar

docs/architecture/adr-016-validator-consensus-key-rotation.md

@@ -9,42 +9,42 @@
 
 Validator consensus key rotation feature has been discussed and requested for a long time, for the sake of safer validator key management policy (e.g. https://github.com/tendermint/tendermint/issues/1136). So, we suggest one of the simplest form of validator consensus key rotation implementation mostly onto Cosmos SDK.
 
-We don't need to make any update on consensus logic in Tendermint because Tendermint does not have any mapping information of consensus key and validator operator key, meaning that from Tendermint point of view, a consensus key rotation of a validator is simply a replacement of a consensus key to another.
+We don't need to make any update on consensus logic in Tendermint because Tendermint does not have any mapping information of consensus key and validator operator key, meaning that from Tendermint's point of view, a consensus key rotation of a validator is simply a replacement of a consensus key to another.
 
-Also, it should be noted that this ADR includes only the simplest form of consensus key rotation without considering multiple consensus keys concept. Such multiple consensus keys concept shall remain a long term goal of Tendermint and Cosmos SDK.
+Also, it should be noted that this ADR includes only the simplest form of consensus key rotation without considering the multiple consensus keys concept. Such multiple consensus keys concept shall remain a long term goal of Tendermint and Cosmos SDK.
 
 ## Decision
 
 ### Pseudo procedure for consensus key rotation
 
 * create new random consensus key.
-* create and broadcast a transaction with a `MsgRotateConsPubKey` that states the new consensus key is now coupled with the validator operator with signature from the validator's operator key.
+* create and broadcast a transaction with a `MsgRotateConsPubKey` that states the new consensus key is now coupled with the validator operator with a signature from the validator's operator key.
 * old consensus key becomes unable to participate on consensus immediately after the update of key mapping state on-chain.
 * start validating with new consensus key.
-* validators using HSM and KMS should update the consensus key in HSM to use the new rotated key after the height `h` when `MsgRotateConsPubKey` committed to the blockchain.
+* validators using HSM and KMS should update the consensus key in HSM to use the new rotated key after the height `h` when `MsgRotateConsPubKey` is committed to the blockchain.
 
 ### Considerations
 
 * consensus key mapping information management strategy
     * store history of each key mapping changes in the kvstore.
-    * the state machine can search corresponding consensus key paired with given validator operator for any arbitrary height in a recent unbonding period.
+    * the state machine can search corresponding consensus key paired with the given validator operator for any arbitrary height in a recent unbonding period.
     * the state machine does not need any historical mapping information which is past more than unbonding period.
 * key rotation costs related to LCD and IBC
-    * LCD and IBC will have traffic/computation burden when there exists frequent power changes
+    * LCD and IBC will have a traffic/computation burden when there exists frequent power changes
     * In current Tendermint design, consensus key rotations are seen as power changes from LCD or IBC perspective
-    * Therefore, to minimize unnecessary frequent key rotation behavior, we limited maximum number of rotation in recent unbonding period and also applied exponentially increasing rotation fee
+    * Therefore, to minimize unnecessary frequent key rotation behavior, we limited the maximum number of rotation in recent unbonding period and also applied exponentially increasing rotation fee
 * limits
     * a validator cannot rotate its consensus key more than `MaxConsPubKeyRotations` time for any unbonding period, to prevent spam.
     * parameters can be decided by governance and stored in genesis file.
 * key rotation fee
     * a validator should pay `KeyRotationFee` to rotate the consensus key which is calculated as below
     * `KeyRotationFee` = (max(`VotingPowerPercentage` *100, 1)* `InitialKeyRotationFee`) * 2^(number of rotations in `ConsPubKeyRotationHistory` in recent unbonding period)
 * evidence module
-    * evidence module can search corresponding consensus key for any height from slashing keeper so that it can decide which consensus key is supposed to be used for given height.
+    * evidence module can search corresponding consensus key for any height from slashing keeper so that it can decide which consensus key is supposed to be used for the given height.
 * abci.ValidatorUpdate
     * tendermint already has ability to change a consensus key by ABCI communication(`ValidatorUpdate`).
     * validator consensus key update can be done via creating new + delete old by change the power to zero.
-    * therefore, we expect we even do not need to change tendermint codebase at all to implement this feature.
+    * therefore, we expect we do not even need to change Tendermint codebase at all to implement this feature.
 * new genesis parameters in `staking` module
     * `MaxConsPubKeyRotations` : maximum number of rotation can be executed by a validator in recent unbonding period. default value 10 is suggested(11th key rotation will be rejected)
     * `InitialKeyRotationFee` : the initial key rotation fee when no key rotation has happened in recent unbonding period. default value 1atom is suggested(1atom fee for the first key rotation in recent unbonding period)
@@ -108,12 +108,12 @@ Proposed
 
 ### Positive
 
-* Validators can immediately or periodically rotate their consensus key to have better security policy
+* Validators can immediately or periodically rotate their consensus key to have a better security policy
 * improved security against Long-Range attacks (https://nearprotocol.com/blog/long-range-attacks-and-a-new-fork-choice-rule) given a validator throws away the old consensus key(s)
 
 ### Negative
 
-* Slash module needs more computation because it needs to lookup corresponding consensus key of validators for each height
+* Slash module needs more computation because it needs to look up the corresponding consensus key of validators for each height
 * frequent key rotations will make light client bisection less efficient
 
 ### Neutral