chore: fix spelling errors (#2144)

chore: spelling errors fixes

Co-authored-by: github-merge-queue <118344674+github-merge-queue@users.noreply.github.com>

.changelog/v5.1.1/api-breaking/provider/2095-proto-message-fix.md

@@ -1,2 +1,2 @@
-- Fix incorrect message defitions in the proto files of the provider module
+- Fix incorrect message definitions in the proto files of the provider module
  ([\#2095](https://github.com/cosmos/interchain-security/pull/2095))

.changelog/v5.1.1/state-breaking/provider/2095-proto-message-fix.md

@@ -1,2 +1,2 @@
-- Fix incorrect message defitions in the proto files of the provider module
+- Fix incorrect message definitions in the proto files of the provider module
  ([\#2095](https://github.com/cosmos/interchain-security/pull/2095))

CHANGELOG.md

@@ -7,13 +7,13 @@
 ### API BREAKING
 
 - [Provider](x/ccv/provider)
- - Fix incorrect message defitions in the proto files of the provider module
+ - Fix incorrect message definitions in the proto files of the provider module
  ([\#2095](https://github.com/cosmos/interchain-security/pull/2095))
 
 ### STATE BREAKING
 
 - [Provider](x/ccv/provider)
- - Fix incorrect message defitions in the proto files of the provider module
+ - Fix incorrect message definitions in the proto files of the provider module
  ([\#2095](https://github.com/cosmos/interchain-security/pull/2095))
 
 ## v5.1.0

docs/docs/integrators/integrating_inactive_validators.md

@@ -4,7 +4,7 @@ sidebar_position: 1
 
 # Inactive Validators Integration Guide
 
-With the [inactive validators feature of Interchain Security](../adrs/adr-017-allowing-inactive-validators.md), validators outside of the active set on the provider chain can validate on consumer chains that allow this. Technically, this is achieved by *increasing* the MaxValidators paramater in the staking module, to let additional validators be part of the set of bonded validators. However, to keep the set of validators participating in consensus on the Cosmos Hub the same, we introduce the MaxProviderConsensusValidators parameter in the provider module, which will restrict the number of validators that actively validate on the provider chain.
+With the [inactive validators feature of Interchain Security](../adrs/adr-017-allowing-inactive-validators.md), validators outside of the active set on the provider chain can validate on consumer chains that allow this. Technically, this is achieved by *increasing* the MaxValidators parameter in the staking module, to let additional validators be part of the set of bonded validators. However, to keep the set of validators participating in consensus on the Cosmos Hub the same, we introduce the MaxProviderConsensusValidators parameter in the provider module, which will restrict the number of validators that actively validate on the provider chain.
 
 To clarify the terminology: