chore: update documentation from cosmos-sdk/docs (#255)

Author: github-actions[bot]

docs/build/building-apps/upgrades/0.52.md

@@ -322,7 +322,7 @@ if err != nil {
 
 The vesting account message and CLI are removed. Existing vesting accounts remain, but you cannot create new ones.
 
-In order to create new vesting accounts you need to add the accounts module to your chain. We provide vesting acccounts by default which have simlar logic to the previous vesting accounts. If you would like custom vesting accounts, they can be implemented in `x/accounts`.
+In order to create new vesting accounts you need to add the accounts module to your chain. We provide vesting accounts by default which have similar logic to the previous vesting accounts. If you would like custom vesting accounts, they can be implemented in `x/accounts`.
 
 ### Introducing x/accounts AccountNumber 
 

docs/build/rfc/rfc-004-accounts.md

@@ -51,7 +51,7 @@ their structure and functionality.
 Instead of representing accounts as simple `google.Protobuf.Any` structures stored in state with no business logic
 attached, this proposal suggests a more sophisticated account representation that is closer to module entities.
 In fact, accounts should be able to receive messages and process them in the same way modules do, and be capable of storing
-state in a isolated (prefixed) portion of state belonging only to them, in the same way as modules do.
+state in an isolated (prefixed) portion of state belonging only to them, in the same way as modules do.
 
 ### Account Message Reception
 

docs/learn/advanced/17-autocli.md

@@ -304,7 +304,7 @@ To sign a file `sign-file` command offers some helpful flags:
       --encoding string          Choose an encoding method for the file content to be added as msg data (no-encoding|base64|hex) (default "no-encoding")
       --indent string            Choose an indent for the tx (default "  ")
       --notEmitUnpopulated       Don't show unpopulated fields in the tx
-      --output string            Choose an output format for the tx (json|text (default "json")
+      --output string            Choose an output format for the tx (json|text) (default "json")
       --output-document string   The document will be written to the given file instead of STDOUT
 ```
 

docs/learn/beginner/00-app-anatomy.md

@@ -187,7 +187,7 @@ Note that `sdk.Msg`s are bundled in [transactions](../advanced/01-transactions.m
 
 When a valid block of transactions is received by the full-node, CometBFT relays each one to the application via [`DeliverTx`](https://docs.cometbft.com/v0.37/spec/abci/abci++_app_requirements#specifics-of-responsedelivertx). Then, the application handles the transaction:
 
-1. Upon receiving the transaction, the application first unmarshalls it from `[]byte`.
+1. Upon receiving the transaction, the application first unmarshals it from `[]byte`.
 2. Then, it verifies a few things about the transaction like [fee payment and signatures](./04-gas-fees.md#antehandler) before extracting the `Msg`(s) contained in the transaction.
 3. `sdk.Msg`s are encoded using Protobuf [`Any`s](#register-codec). By analyzing each `Any`'s `type_url`, baseapp's `msgServiceRouter` routes the `sdk.Msg` to the corresponding module's `Msg` service.
 4. If the message is successfully processed, the state is updated.