Merge pull request #2208 from leopardracer/main

Fix typos in documentation

Author: chipshort

INTEGRATION.md

@@ -6,14 +6,14 @@ If you want to use Wasm in your own app, here is how you can get this working
 quickly and easily. 
 First start with this [article](https://medium.com/cosmwasm/cosmwasm-for-ctos-iv-native-integrations-713140bf75fc) 
 in the "CosmWasm for CTOs" series that gives you a high level view. 
-Then check to make sure you fit the pre-requisites,
+Then check to make sure you fit the prerequisites,
 then integrate the `x/wasm` module as described below, and finally, you
 can add custom messages and queries to your custom Go/SDK modules, exposing
 them to any chain-specific contract.
 
 ## Prerequisites
 
-The pre-requisites of integrating `x/wasm` into your custom app is to be using 
+The prerequisites of integrating `x/wasm` into your custom app are to be using 
 a compatible version of the Cosmos SDK, and to accept some limits to the
 hardware it runs on.
 

scripts/contrib/prometheus/README.md

@@ -40,7 +40,7 @@ Note the `format` parameter in the request for the endpoint:
 # port 9090 is used by wasmd already
 docker run -it -v $(pwd)/scripts/contrib/prometheus:/prometheus  -p9091:9090  prom/prometheus --config.file=/prometheus/prometheus.yaml
 ```
-* Open [console](http://localhost:9091) and find `wasm_`service metrics
+* Open [console](http://localhost:9091) and find `wasm_` service metrics
 
 ## Run Grafana
 

x/wasm/Governance.md

@@ -6,7 +6,7 @@ a high-level, technical introduction meant to provide context before
 looking into the code, or constructing proposals. 
 
 ## Proposal Types
-We have added 15 new wasm specific proposal messages that cover the contract's live cycle and authorization:
+We have added 15 new wasm specific proposal messages that cover the contract's lifecycle and authorization:
 
 * `MsgStoreCode` - upload a wasm binary
 * `MsgInstantiateContract` - instantiate a wasm contract