chore: remove repetitive words (#364)

Signed-off-by: vastonus <[email protected]>

Author: vastonus

cips/cip-032.md

@@ -27,7 +27,7 @@ Hyperlane on Celestia, more concretely, requires the addition of two SDK modules
 
 Similar to IBC, non-native tokens will initially not be allowed on Celestia's state machine. This is enforced by disabling the creation of [synthetic tokens](https://github.com/bcp-innovations/hyperlane-cosmos/blob/2617881125228632edb091f0663d133b76de11ee/x/warp/keeper/msg_server.go#L20).
 
-The only ISM (Interchain Security Module) that will be initially supported is the MultiSig ISM, which relies on attestations from N of M "validators". Note that the MultiSig ISM validator set can be different from the the PoS validator set.
+The only ISM (Interchain Security Module) that will be initially supported is the MultiSig ISM, which relies on attestations from N of M "validators". Note that the MultiSig ISM validator set can be different from the PoS validator set.
 
 ## Backwards Compatibility
 

cips/cip-template.md

@@ -84,7 +84,7 @@ TODO: Remove the previous comments before submitting
 
 This section is optional.
 
-The Test Cases section should include expected input/output pairs, but may include a succinct set of executable tests. It should not include project build files. No new requirements may be be introduced here (meaning an implementation following only the Specification section should pass all tests here.)
+The Test Cases section should include expected input/output pairs, but may include a succinct set of executable tests. It should not include project build files. No new requirements may be introduced here (meaning an implementation following only the Specification section should pass all tests here.)
 
 If the test suite is too large to reasonably be included inline, then consider adding it as one or more files in `../assets/cip-####/`. External links will not be allowed