Merge pull request #2146 from omahs/patch-1

Fix typos

Author: chipshort

docs/ERROR_HANDLING.md

@@ -64,7 +64,7 @@ case would. This has two major implications:
 1. Application specific errors (especially those which can be triggered by
    untrusted users) should create contract errors and no panics. This ensures
    that error acknowledgements are written and relayer transactions don't fail.
-2. Using panics allow the contract developer to make the transaction fail
+2. Using panics allows the contract developer to make the transaction fail
    without writing an acknowledgement. This can be handy e.g. for allowlisting
    relayer addresses.
 

docs/MESSAGE_TYPES.md

@@ -17,7 +17,7 @@ Rust types as well as `cosmwasm_std` types and how they are encoded in JSON.
 | u128/i128           | number                                    | `340282366920938463463374607431768211455, -2766523308300312711084346401884294402` | Supported in Rust. Other implementations do not support the full range. This used to be serialized as a string in serde-json-wasm. See [Dev Note #4: u128/i128 serialization][dev-note-4]. If you have any code relying on that serialization, switch to `Uint128` / `Int128`. |
 | usize/isize         | number                                    | `123456`                                                                          | 🚫 Don't use this type because it has a different size in unit tests (64 bit) and Wasm (32 bit). Also it tends to issue float instructions such that the contracts cannot be uploaded.                                                                                         |
 | String              | string                                    | `"foo"`                                                                           |
-| &str                | string                                    | `"foo"`                                                                           | 🚫 Unsuppored since message types must be owned (DeserializeOwned)                                                                                                                                                                                                             |
+| &str                | string                                    | `"foo"`                                                                           | 🚫 Unsupported since message types must be owned (DeserializeOwned)                                                                                                                                                                                                            |
 | Option\<T\>         | `null` or JSON type of `T`                | `null`, `{"foo":12}`                                                              |                                                                                                                                                                                                                                                                                |
 | Vec\<T\>            | array of JSON type of `T`                 | `["one", "two", "three"]` (Vec\<String\>), `[true, false]` (Vec\<bool\>)          |
 | Vec\<u8\>           | array of numbers from 0 to 255            | `[187, 61, 11, 250]`                                                              | ⚠️ Discouraged as this encoding is not as compact as it can be. See `Binary`.                                                                                                                                                                                                  |

docs/PINNING.md

@@ -35,7 +35,7 @@ The VM does not persist pinned memory entries. I.e. you need to call `Pin` every
 time you start the process. This is implemented in [`InitializePinnedCodes` in
 wasmd][initializepinnedcodes].
 
-At the chain level pinning and unpinning is done via governance proposals. See
+At the chain level pinning and unpinning are done via governance proposals. See
 `MsgPinCodes`/`MsgUnpinCodes` in wasmd.
 
 When contracts are migrated from one code to another, there is no automatic

docs/STORAGE_KEYS.md

@@ -64,7 +64,7 @@ good reason to preserve the single component version.
 
 ## 2023 updates
 
-With the deprecation if cosmwasm-storage and the adoption of the system in
+With the deprecation of cosmwasm-storage and the adoption of the system in
 cw-storage-plus, it is time to do a few changes to the Length-prefixed keys
 standard, without breaking existing users.