chore: fix some comments (#20119)

crypto/keys/ed25519/doc.go

@@ -3,7 +3,7 @@ package ed25519
 /*
 This package contains a wrapper around crypto/ed22519 to make it comply with the crypto interfaces.
 
-This package employs zip215 rules. We use https://github.com/hdevalence/ed25519consensus verification function. Ths is done in order to keep compatibility with Tendermints ed25519 implementation.
+This package employs zip215 rules. We use https://github.com/hdevalence/ed25519consensus verification function. This is done in order to keep compatibility with Tendermints ed25519 implementation.
 	- https://github.com/cometbft/cometbft/blob/master/crypto/ed25519/ed25519.go#L155
 
 This package works with correctly generated signatures. To read more about what this means see https://hdevalence.ca/blog/2020-10-04-its-25519am

x/auth/client/cli/tx_sign.go

@@ -140,7 +140,7 @@ func makeSignBatchCmd() func(cmd *cobra.Command, args []string) error {
 				// append messages
 				msgs = append(msgs, unsignedStdTx.GetMsgs()...)
 			}
-			// set the new appened msgs into builder
+			// set the new appended msgs into builder
 			err = txBuilder.SetMsgs(msgs...)
 			if err != nil {
 				return err

x/staking/README.md

@@ -292,7 +292,7 @@ A `ConsPubKeyRotationHistory` object is created every time a consensus pubkey ro
 
 An entry is added in `OldToNewConsKeyMap` collection for every rotation (Note: this is to handle the evidences when submitted with old cons key).
 
-An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is invovled in the history.
+An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is involved in the history.
 
 To prevent the spam: