Fix typos in multiple files

app/genesis.go

@@ -5,7 +5,7 @@ import (
 )
 
 // GenesisState The genesis state of the blockchain is represented here as a map of raw json
-// messages key'd by a identifier string.
+// messages key'd by an identifier string.
 // The identifier is used to determine which module genesis information belongs
 // to so it may be appropriately routed during init chain.
 // Within this application default genesis information is retrieved from

cosmwasm/contracts/v010/dist/README.md

@@ -34,7 +34,7 @@ you can customize.
 
 ## Create a Repo
 
-After generating, you have a initialized local git repo, but no commits, and no
+After generating, you have an initialized local git repo, but no commits, and no
 remote. Go to a server (eg. github) and create a new upstream repo (called
 `YOUR-GIT-URL` below). Then run the following:
 
@@ -50,7 +50,7 @@ git push -u origin master
 ## CI Support
 
 We have templates for both github actions and Circle CI in the generated
-project, so you can get up an running with CI right away. One note is that the
+project, so you can get up a running with CI right away. One note is that the
 CI runs all `cargo` commands with `--locked` to ensure it uses the exact same
 versions as you have locally. This also means you must have an up-to-date
 `Cargo.lock` file, which is not auto-generated.

cosmwasm/contracts/v010/erc20/Developing.md

@@ -109,7 +109,7 @@ docker run --rm -v "$(pwd)":/code \
   cosmwasm/rust-optimizer:0.9.0
 ```
 
-We must mount the contract code to `/code`. You can use a absolute path instead
+We must mount the contract code to `/code`. You can use an absolute path instead
 of `$(pwd)` if you don't want to `cd` to the directory first. The other two
 volumes are nice for speedup. Mounting `/code/target` in particular is useful
 to avoid docker overwriting your local dev files with root permissions.

cosmwasm/contracts/v010/escrow/Developing.md

@@ -109,7 +109,7 @@ docker run --rm -v "$(pwd)":/code \
   cosmwasm/rust-optimizer:0.8.0
 ```
 
-We must mount the contract code to `/code`. You can use a absolute path instead
+We must mount the contract code to `/code`. You can use an absolute path instead
 of `$(pwd)` if you don't want to `cd` to the directory first. The other two
 volumes are nice for speedup. Mounting `/code/target` in particular is useful
 to avoid docker overwriting your local dev files with root permissions.

cosmwasm/contracts/v010/gov/README.md

@@ -34,7 +34,7 @@ you can customize.
 
 ## Create a Repo
 
-After generating, you have a initialized local git repo, but no commits, and no
+After generating, you have an initialized local git repo, but no commits, and no
 remote. Go to a server (eg. github) and create a new upstream repo (called
 `YOUR-GIT-URL` below). Then run the following:
 
@@ -50,7 +50,7 @@ git push -u origin master
 ## CI Support
 
 We have templates for both github actions and Circle CI in the generated
-project, so you can get up an running with CI right away. One note is that the
+project, so you can get up a running with CI right away. One note is that the
 CI runs all `cargo` commands with `--locked` to ensure it uses the exact same
 versions as you have locally. This also means you must have an up-to-date
 `Cargo.lock` file, which is not auto-generated.

cosmwasm/contracts/v010/mint/README.md

@@ -34,7 +34,7 @@ you can customize.
 
 ## Create a Repo
 
-After generating, you have a initialized local git repo, but no commits, and no
+After generating, you have an initialized local git repo, but no commits, and no
 remote. Go to a server (eg. github) and create a new upstream repo (called
 `YOUR-GIT-URL` below). Then run the following:
 
@@ -50,7 +50,7 @@ git push -u origin master
 ## CI Support
 
 We have templates for both github actions and Circle CI in the generated
-project, so you can get up an running with CI right away. One note is that the
+project, so you can get up a running with CI right away. One note is that the
 CI runs all `cargo` commands with `--locked` to ensure it uses the exact same
 versions as you have locally. This also means you must have an up-to-date
 `Cargo.lock` file, which is not auto-generated.

cosmwasm/contracts/v010/reflect/README.md

@@ -34,7 +34,7 @@ you can customize.
 
 ## Create a Repo
 
-After generating, you have a initialized local git repo, but no commits, and no
+After generating, you have an initialized local git repo, but no commits, and no
 remote. Go to a server (eg. github) and create a new upstream repo (called
 `YOUR-GIT-URL` below). Then run the following:
 
@@ -50,7 +50,7 @@ git push -u origin master
 ## CI Support
 
 We have templates for both github actions and Circle CI in the generated
-project, so you can get up an running with CI right away. One note is that the
+project, so you can get up a running with CI right away. One note is that the
 CI runs all `cargo` commands with `--locked` to ensure it uses the exact same
 versions as you have locally. This also means you must have an up-to-date
 `Cargo.lock` file, which is not auto-generated.