feat: add CI for codespell (#255)

* feat: add CI for codespell

* feat: fix spells

* feat: add excluded files

* feat: fix typos

Author: mattverse

.github/workflows/codespell.yml

@@ -0,0 +1,28 @@
+name: Spell Check
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  spellcheck:
+    name: Run codespell
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Install codespell
+        run: pip install codespell
+
+      - name: Run codespell
+        run: codespell --skip="yarn.lock,package-lock.json,node_modules,build"

docs/beaker/README.md

@@ -225,10 +225,10 @@ To create the contract entrypoint for migration, first, define `MigrateMsg` in `
 pub struct MigrateMsg {}
 ```
 
-With MigrateMsg defined we need to update `contract.rs`. First update the import from `crate::msg` to include `MigrateMsg`:
+With MigrateMsg defined we need to update `contract.rs`. First update the import from `create::msg` to include `MigrateMsg`:
 
 ```rust
-use crate::msg::{CountResponse, ExecuteMsg, InstantiateMsg, QueryMsg, MigrateMsg};
+use create::msg::{CountResponse, ExecuteMsg, InstantiateMsg, QueryMsg, MigrateMsg};
 ```
 
 ```rust
@@ -340,7 +340,7 @@ await contract.counter.signer(account.test1).execute({ increment: {} });
 await contract.counter.query({ get_count: {} });
 ```
 
-You can find avaialable methods for the aforementioned instances here:
+You can find available methods for the aforementioned instances here:
 
 - [Account](console/classes//Account.md#methods-1)
 - [Contract](./console/classes//Contract.md#methods-1)

docs/beaker/commands/beaker_wasm.md

@@ -218,7 +218,7 @@ Arguments:
 
 * ` <contract-name>`Name of the contract to instantiate
 
-* `-l/--label <label>`: Label for the instantiated contract for selcting migration target (default: `default`)
+* `-l/--label <label>`: Label for the instantiated contract for selecting migration target (default: `default`)
 
 * `-r/--raw <raw>`: Raw json string to use as instantiate msg
 

docs/beaker/commands/beaker_wasm_proposal.md

@@ -26,7 +26,7 @@ Arguments:
 
 * `--title <title>`: Proposal title (default: ``)
 
-* `--description <description>`: Proposal decsription (default: ``)
+* `--description <description>`: Proposal description (default: ``)
 
 * `--deposit <deposit>`: Proposal deposit to activate voting
 

docs/beaker/config/global.md

@@ -21,7 +21,7 @@
 * **`gas_adjustment`** : f64  
 
    > 
-   > Adjusting `gas_limit` from simulated gas as a safety factor to make sure gas_limit is enought for the tx.  
+   > Adjusting `gas_limit` from simulated gas as a safety factor to make sure gas_limit is enough for the tx.  
    > When user doesn't specify `gas_limit`, `gas_limit = simulated_gas * gas_adjustment`,  
    > while `simulated_gas` is simulated gas consumption for the tx.  
    > 

docs/beaker/config/workspace.md

@@ -29,7 +29,7 @@
     * **`branch`** : String  
 
        > 
-       > Brance of the repo to be used as template  
+       > Branch of the repo to be used as template  
        > 
       
       

docs/cosmwasm/cw-orch.md

@@ -20,7 +20,7 @@ let count = counter.get_count()?;
 assert_eq!(count.count, 1);
 ```
 
-In this quick-start guide, we will review the necessary steps in order to integrate [`cw-orch`](https://github.com/AbstractSDK/cw-orchestrator) into a simple contract crate. [We review integration of rust-workspaces (multiple contracts) at the end of this page](#integration-in-a-workspace).
+In this quick-start guide, we will review the necessary steps in order to integrate [`cw-orch`](https://github.com/AbstractSDK/cw-orchestrator) into a simple contract create. [We review integration of rust-workspaces (multiple contracts) at the end of this page](#integration-in-a-workspace).
 
 > **NOTE**: *Quicker than the quick start*
 >
@@ -40,7 +40,7 @@ In this quick-start guide, we will review the necessary steps in order to integr
   - [Using the integration](#using-the-integration)
 - [Integration in a workspace](#integration-in-a-workspace)
   - [Handling dependencies and features](#handling-dependencies-and-features)
-  - [Creating an interface crate](#creating-an-interface-crate)
+  - [Creating an interface create](#creating-an-interface-create)
   - [Integrating single contracts](#integrating-single-contracts)
 - [More examples and scripts](#more-examples-and-scripts)
 
@@ -93,7 +93,7 @@ Then, inside that `interface.rs` file, you can define the interface for your con
 ```rust
 use cw_orch::{interface, prelude::*};
 
-use crate::msg::{ExecuteMsg, InstantiateMsg, MigrateMsg, QueryMsg};
+use create::msg::{ExecuteMsg, InstantiateMsg, MigrateMsg, QueryMsg};
 
 pub const CONTRACT_ID: &str = "counter_contract";
 
@@ -111,11 +111,11 @@ impl<Chain: CwEnv> Uploadable for CounterContract<Chain> {
     fn wrapper(&self) -> Box<dyn MockContract<Empty>> {
         Box::new(
             ContractWrapper::new_with_empty(
-                crate::contract::execute,
-                crate::contract::instantiate,
-                crate::contract::query,
+                create::contract::execute,
+                create::contract::instantiate,
+                create::contract::query,
             )
-            .with_migrate(crate::contract::migrate),
+            .with_migrate(create::contract::migrate),
         )
     }
 }
@@ -128,7 +128,7 @@ Learn more about the content of the interface creation specifics in the [`cw-orc
 >
 >    ```rust
 >    #[cfg(feature = "interface")]
->    pub use crate::interface::CounterContract;
+>    pub use create::interface::CounterContract;
 >    ```
 
 ### Interaction helpers
@@ -176,14 +176,14 @@ Find out more about the interaction helpers in the [`cw-orch` documentation](htt
 >
 >    ```rust
 >    #[cfg(feature = "interface")]
->    pub use crate::msg::{ExecuteMsgFns as CounterExecuteMsgFns, QueryMsgFns as CounterQueryMsgFns};
+>    pub use create::msg::{ExecuteMsgFns as CounterExecuteMsgFns, QueryMsgFns as CounterQueryMsgFns};
 >    ```
 
 ### Using the integration
 
 Now that all the setup is done, you can use your contract in tests, integration-tests or scripts.
 
-Start by importing your crate, with the `interface` feature enabled. Depending on your use-case this will be in `[dependencies]` or `[dev-dependencies]`:
+Start by importing your create, with the `interface` feature enabled. Depending on your use-case this will be in `[dependencies]` or `[dev-dependencies]`:
 
 ```toml
 counter-contract = { path = "../counter-contract", features = ["interface"] }
@@ -244,9 +244,9 @@ Refer above to [Adding `cw-orch` to your `Cargo.toml` file](#adding-cw-orch-to-y
 
 For instance, for the `cw20_base` contract, you need to execute those 2 steps on the `cw20-base` contract (where the `QueryMsg` are defined) as well as on the `cw20` package (where the `ExecuteMsg` are defined).
 
-### Creating an interface crate
+### Creating an interface create
 
-When using a workspace, we advise you to create a new crate inside your workspace for defining your contract's interfaces. In order to do that, use:
+When using a workspace, we advise you to create a new create inside your workspace for defining your contract's interfaces. In order to do that, use:
 
 ```shell
 cargo new interface --lib
@@ -260,7 +260,7 @@ Add the interface package to your workspace `Cargo.toml` file
 members = ["packages/*", "contracts/*", "interface"]
 ```
 
-Inside this `interface` crate, we advise to integrate all your contracts 1 by 1 in separate files. Here is the structure of the `cw-plus` integration for reference:
+Inside this `interface` create, we advise to integrate all your contracts 1 by 1 in separate files. Here is the structure of the `cw-plus` integration for reference:
 
 ```path
 interface (interface collection)

docs/cosmwasm/javascript.md

@@ -32,7 +32,7 @@ Create a new index.ts file
 touch index.ts
 ```
 
-The class CosmWasmClient is exported from the CosmJS package @cosmjs/cosmwasm-stargate. Learn more in the [offical docs](https://cosmwasm.github.io/CosmWasmJS/clients/reading/CosmWasmClient.html).
+The class CosmWasmClient is exported from the CosmJS package @cosmjs/cosmwasm-stargate. Learn more in the [official docs](https://cosmwasm.github.io/CosmWasmJS/clients/reading/CosmWasmClient.html).
 
 ```javascript=
 import { CosmWasmClient } from "cosmwasm";

docs/cosmwasm/local/submit-wasm-proposal.md

@@ -42,7 +42,7 @@ CONTRACT=cw20_base
 ```
 
 ## Define proposal ID
-We cannot really do this progamatically. Proposal `1` will come out after submitting it for the first time on a new chain. You can always update this manually when testing multiple times on the same state.
+We cannot really do this programmatically. Proposal `1` will come out after submitting it for the first time on a new chain. You can always update this manually when testing multiple times on the same state.
 
 ```
 PROPOSAL=1

docs/cosmwasm/testnet/cosmwasm-beaker.md

@@ -41,7 +41,7 @@ beaker wasm new counter
 ```
 
 ### Deploy contract on permisionless network
-The testnet is permisionless by default in order to allow developers to easyly deploy contracts. 
+The testnet is permisionless by default in order to allow developers to easily deploy contracts. 
 
 ```sh
 beaker wasm deploy counter --signer-account test1 --network testnet --no-wasm-opt --raw '{ "count": 0 }' --label 'My first Beaker Contract'
@@ -53,7 +53,7 @@ Note how we added `--network testnet` to tell beaker to deploy to the testnet Os
 In this example we are using `osmo1nyphwl8p5yx6fxzevjwqunsfqpcxukmtk8t60m` which is the address from the beaker test1 account as seen in the [config.rs](https://github.com/osmosis-labs/beaker/blob/main/packages/cli/src/framework/config.rs) file. 
 
 :::warning
-Please note that account test1 is publicaly available as documented [here](https://github.com/osmosis-labs/beaker/blob/main/docs/config/global.md) and only used for development purposes. Beaker will support local keyring in about 1-2 weeks. 
+Please note that account test1 is publicly available as documented [here](https://github.com/osmosis-labs/beaker/blob/main/docs/config/global.md) and only used for development purposes. Beaker will support local keyring in about 1-2 weeks. 
 :::
 
 ```
@@ -149,7 +149,7 @@ Run the following command to vote from beaker
 beaker wasm proposal vote --option yes counter --signer-account test1 --network testnet
 ```
 
-Even though the testnet is configured as permisionless, it's important to undertanding the voting process. We need validators to vote  for your proposal in order to reach the quorum. We created a simple utility in our faucet that will allow you to request a validator with enough voting power to vote for your proposal as well. 
+Even though the testnet is configured as permisionless, it's important to understanding the voting process. We need validators to vote  for your proposal in order to reach the quorum. We created a simple utility in our faucet that will allow you to request a validator with enough voting power to vote for your proposal as well. 
 
 Please visit: