Merge PR #3912: Fix a bunch of typos while skimming through the docs

docs/_attic/sdk/core/app1.md

@@ -153,11 +153,11 @@ Along with the message, the Handler takes environmental information (a `Context`
 All information necessary for processing a message should be available in the context.
 
 Where is the KVStore in all of this? Access to the KVStore in a message handler is restricted by the Context via object-capability keys.
-Only handlers which were given explict access to a store's key will be able to access that store during message processsing.
+Only handlers which were given explicit access to a store's key will be able to access that store during message processsing.
 
 ### Context
 
-The SDK uses a `Context` to propogate common information across functions.
+The SDK uses a `Context` to propagate common information across functions.
 Most importantly, the `Context` restricts access to KVStores based on object-capability keys.
 Only handlers which have been given explicit access to a key will be able to access the corresponding store.
 
@@ -176,7 +176,7 @@ func newFooHandler(key sdk.StoreKey) sdk.Handler {
 `Context` is modeled after the Golang
 [context.Context](https://golang.org/pkg/context/), which has
 become ubiquitous in networking middleware and routing applications as a means
-to easily propogate request context through handler functions.
+to easily propagate request context through handler functions.
 Many methods on SDK objects receive a context as the first argument.
 
 The Context also contains the

docs/gaia/delegator-guide-cli.md

@@ -31,7 +31,7 @@ Please exercise extreme caution!
 
 - [Installing `gaiacli`](#installing-gaiacli)
 - [Cosmos Accounts](#cosmos-accounts)
-    + [Restoring an account from the fundrasier](#restoring-an-account-from-the-fundraiser)
+    + [Restoring an account from the fundraiser](#restoring-an-account-from-the-fundraiser)
     + [Creating an account](#creating-an-account)
 - [Accessing the Cosmos Hub network](#accessing-the-cosmos-hub-network)
     + [Running your own full-node](#running-your-own-full-node)
@@ -157,7 +157,7 @@ You will be prompted to input a passphrase that is used to encrypt the private k
 
 ### Creating an account
 
-To create an account, you just need to have `gaiacli` installed. Before creating it, you need to know where you intend to store and interract with your private keys. The best options are to store them in an offline dedicated computer or a ledger device. Storing them on your regular online computer involves more risk, since anyone who infiltrates your computer through the internet could exfiltrate your private keys and steal your funds.
+To create an account, you just need to have `gaiacli` installed. Before creating it, you need to know where you intend to store and interact with your private keys. The best options are to store them in an offline dedicated computer or a ledger device. Storing them on your regular online computer involves more risk, since anyone who infiltrates your computer through the internet could exfiltrate your private keys and steal your funds.
 
 #### Using a ledger device
 
@@ -365,7 +365,7 @@ For mainnet, the recommended `gas-prices` is `0.025uatom`.
 :::
 
 ::: warning
-**Before bonding Atoms, please read the [delegator faq](https://cosmos.network/resources/delegators) to understand the risk and responsabilities involved with delegating**
+**Before bonding Atoms, please read the [delegator faq](https://cosmos.network/resources/delegators) to understand the risk and responsibilities involved with delegating**
 :::
 
 ::: warning

docs/gaia/gaiacli.md

@@ -437,7 +437,7 @@ Once you begin an redelegation, you can see it's information by using the follow
 gaiacli query staking redelegation <delegator_addr> <src_val_addr> <dst_val_addr>
 ```
 
-Or if you want to check all your current unbonding-delegations with disctinct validators:
+Or if you want to check all your current unbonding-delegations with distinct validators:
 
 ```bash
 gaiacli query staking redelegations <account_cosmos>

docs/gaia/installation.md

@@ -24,7 +24,7 @@ If necessary, make sure you `git checkout` the correct
 [released version](https://github.com/cosmos/cosmos-sdk/releases).
 
 ::: warning
-For the mainnet, make sure your version if greather than `v0.33.0`
+For the mainnet, make sure your version if greater than `v0.33.0`
 ::: 
 
 ```bash
@@ -65,7 +65,7 @@ Build tags indicate special features that have been enabled in the binary.
 
 ### Install binary distribution via snap (Linux only)
 
-**Do not use snap at this time to install the binaries for production until we have a reproduceable binary system.**
+**Do not use snap at this time to install the binaries for production until we have a reproducible binary system.**
 
 
 ### Next

docs/gaia/validators/validator-faq.md

@@ -16,7 +16,7 @@ The Cosmos Hub is a public Proof-Of-Stake (PoS) blockchain, meaning that the wei
 
 Any user in the system can declare their intention to become a validator by sending a `create-validator` transaction. From there, they become validator candidates.
 
-The weight (i.e. voting power) of a validator determines wether or not they are an active validator. Initially, only the top 100 validators with the most voting power will be active validators. 
+The weight (i.e. voting power) of a validator determines whether or not they are an active validator. Initially, only the top 100 validators with the most voting power will be active validators. 
 
 ### What is a full-node?
 
@@ -94,7 +94,7 @@ After a validator is created with a `create-validator` transaction, they can be
 - `unbonded`: Validator is not in the active set, and therefore not signing blocs. Validator cannot be slashed, and does not earn any reward. It is still possible to delegate Atoms to this validator. Un-delegating from an `unbonded` validator is immediate.
 
 
-### What is 'self-delegation'? How can I increase my 'self-delegatino'?
+### What is 'self-delegation'? How can I increase my 'self-delegation'?
 
 Self-delegation is delegation from a validator to themselves. This amount can be increases by sending a `delegate` transaction from your validator's `application` application key.
 
@@ -113,13 +113,13 @@ Delegators are free to choose validators according to their own subjective crite
 
 Apart from these criteria, there will be a possibility for validators to signal a website address to complete their resume. Validators will need to build reputation one way or another to attract delegators. For example, it would be a good practice for validators to have their setup audited by third parties. Note though, that the Tendermint team will not approve or conduct any audit themselves. For more on due diligence, see [this blog post](https://medium.com/@interchain_io/3d0faf10ce6f)
 
-## Responsibilites
+## Responsibilities
 
 ### Do validators need to be publicly identified?
 
 No, they do not. Each delegator will value validators based on their own criteria. Validators will be able to register a website address when they nominate themselves so that they can advertise their operation as they see fit. Some delegators may prefer a website that clearly displays the team operating the validator and their resume, while others might prefer anonymous validators with positive track records.
 
-### What are the responsiblities of a validator?
+### What are the responsibilities of a validator?
 
 Validators have two main responsibilities:
 

docs/gaia/what-is-gaia.md

@@ -3,7 +3,7 @@
 `gaia` is the name of the Cosmos SDK application for the Cosmos Hub. It comes with 2 main entrypoints:
 
 - `gaiad`: The Gaia Daemon, runs a full-node of the `gaia` application.
-- `gaiacli`: The Gaia command-line interface, which enables interraction with a Gaia full-node.
+- `gaiacli`: The Gaia command-line interface, which enables interaction with a Gaia full-node.
 
 `gaia` is built on the Cosmos SDK using the following modules:
 

docs/spec/governance/01_concepts.md

@@ -123,7 +123,7 @@ that proposals are accepted if the proportion of `Yes` votes (excluding
 proportion of `NoWithVeto` votes is inferior to 1/3 (excluding `Abstain` 
 votes).
 
-Proposals can be accepted before the end of the voting period if they meet a special condtion. Namely, if the ratio of `Yes` votes to `InitTotalVotingPower`exceeds 2:3, the proposal will be immediately accepted, even if the `Voting period` is not finished. `InitTotalVotingPower` is the total voting power of all bonded Atom holders at the moment when the vote opens. 
+Proposals can be accepted before the end of the voting period if they meet a special condition. Namely, if the ratio of `Yes` votes to `InitTotalVotingPower`exceeds 2:3, the proposal will be immediately accepted, even if the `Voting period` is not finished. `InitTotalVotingPower` is the total voting power of all bonded Atom holders at the moment when the vote opens. 
 This condition exists so that the network can react quickly in case of urgency.
 
 ### Inheritance
@@ -143,7 +143,7 @@ At present, validators are not punished for failing to vote.
 
 ### Governance address
 
-Later, we may add permissionned keys that could only sign txs from certain modules. For the MVP, the `Governance address` will be the main validator address generated at account creation. This address corresponds to a different PrivKey than the Tendermint PrivKey which is responsible for signing consensus messages. Validators thus do not have to sign governance transactions with the sensitive Tendermint PrivKey.
+Later, we may add permissioned keys that could only sign txs from certain modules. For the MVP, the `Governance address` will be the main validator address generated at account creation. This address corresponds to a different PrivKey than the Tendermint PrivKey which is responsible for signing consensus messages. Validators thus do not have to sign governance transactions with the sensitive Tendermint PrivKey.
 
 ## Software Upgrade
 
@@ -172,4 +172,4 @@ Once a block contains more than 2/3rd *precommits* where a common
 nodes, non-validating full nodes and light-nodes) are expected to switch to the
 new version of the software. 
 
-*Note: Not clear how the flip is handled programatically*
+*Note: Not clear how the flip is handled programmatically*

docs/spec/governance/02_state.md

@@ -55,7 +55,7 @@ type ProposalStatus byte
 
 const (
     ProposalStatusOpen      = 0x1   // Proposal is submitted. Participants can deposit on it but not vote
-    ProposalStatusActive    = 0x2   // MinDeposit is reachhed, participants can vote
+    ProposalStatusActive    = 0x2   // MinDeposit is reached, participants can vote
     ProposalStatusAccepted  = 0x3   // Proposal has been accepted
     ProposalStatusRejected  = 0x4   // Proposal has been rejected
     ProposalStatusClosed   = 0x5   // Proposal never reached MinDeposit

docs/spec/slashing/04_begin_block.md

@@ -84,7 +84,7 @@ single slashing period is capped as described in [overview.md](overview.md) unde
 
 ## Uptime tracking
 
-At the beginning of each block, we update the signing info for each validator and check if they've dipped below the liveness threshhold over the tracked window.  If so, they will be slashed by `LivenessSlashAmount` and will be Jailed for `LivenessJailPeriod`.  Liveness slashes do NOT lead to a tombstombing.
+At the beginning of each block, we update the signing info for each validator and check if they've dipped below the liveness threshold over the tracked window.  If so, they will be slashed by `LivenessSlashAmount` and will be Jailed for `LivenessJailPeriod`.  Liveness slashes do NOT lead to a tombstombing.
 
 ```
 height := block.Height

docs/spec/staking/01_state.md

@@ -212,7 +212,7 @@ type RedelegationEntry struct {
 All queues objects are sorted by timestamp. The time used within any queue is
 first rounded to the nearest nanosecond then sorted. The sortable time format
 used is a slight modification of the RFC3339Nano and uses the the format string
-`"2006-01-02T15:04:05.000000000"`. Noteably This format: 
+`"2006-01-02T15:04:05.000000000"`. Notably this format: 
 
  - right pads all zeros
  - drops the time zone info (uses UTC)