Fix typos

.gitbook/bridge/ethereum.md

@@ -61,7 +61,7 @@ If you are not familiar with how Transactions (and Messages) work on Cosmos you
 
 When `MsgSendToEth` is called on the chain, some of the validators will pick up the transaction, batch multiple `MsgSendToEth` requests into one and: burn the assets being withdrawn on Injective, unlock these funds on the Peggy Smart Contract on Ethereum and send them to the respective address.
 
-There is a bridgeFee included in these transactions to incentivise Validators to pick up and process your withdrawal requests faster. The bridgeFee is in the asset the user wants to withdraw to Ethereum (if you withdraw INJ you have to pay the bridgeFee in INJ as well).
+There is a bridgeFee included in these transactions to incentivize Validators to pick up and process your withdrawal requests faster. The bridgeFee is in the asset the user wants to withdraw to Ethereum (if you withdraw INJ you have to pay the bridgeFee in INJ as well).
 
 Here is an example implementation that prepares the transaction, uses a privateKey to sign it and finally, broadcasts it to Injective:
 

.gitbook/building-dapps/configuring-nuxt.md

@@ -122,7 +122,7 @@ export default defineNuxtConfig({
 
   // We generate only sitemaps for the client side as we don't need a server
   // Note: there is a problem with sitemaps for Vite + Nuxt3
-  // as usually is that it takes to much time/memory to generate
+  // as usual is that it takes too much time/memory to generate
   // sitemaps and the build process can fail
   // on Github Actions/Netlify/Vercel/etc so we have to use another
   // strategy like generating them locally and pushing them to services like

.gitbook/contracts/injective-name-service.md

@@ -100,7 +100,7 @@ console.log(injectiveAddress)
 
 ### Reverse Resolution
 
-* Get primary name for injective address.
+* Get the primary name for injective address.
 
 ```ts
 import { getNetworkEndpoints, Network } from '@injectivelabs/networks'

.gitbook/core-modules/auction.md

@@ -1,6 +1,6 @@
 # Auction
 
-The `auction` module is heart of the `buy-back-and-burn` on chain mechanism, where 60% of the weekly trading fees are colleted and auctioned off to the highest INJ bidder where the submitted INJ of the highest bidder are burned in the process.
+The `auction` module is heart of the `buy-back-and-burn` on chain mechanism, where 60% of the weekly trading fees are collected and auctioned off to the highest INJ bidder where the submitted INJ of the highest bidder are burned in the process.
 
 ### MsgBid
 

.gitbook/core-modules/distribution.md

@@ -39,7 +39,7 @@ console.log(txHash);
 
 ### MsgWithdrawValidatorCommission
 
-This message is used to by the validator to withdraw the commission earned.
+This message is used by the validator to withdraw the commission earned.
 
 ```ts
 import {

.gitbook/core-modules/peggy.md

@@ -1,6 +1,6 @@
 # Peggy
 
-The `peggy` module is heart of the injective <> ethereum bridge, where deposited funds will be locked on the ethereum [peggy contract](https://etherscan.io/address/0xF955C57f9EA9Dc8781965FEaE0b6A2acE2BAD6f3#code) and minted on the Injective chain. Similarly withdrawal funds will be burned on the injective chain and unlocked on the ethereum peggy contract.
+The `peggy` module is the heart of the injective <> ethereum bridge, where deposited funds will be locked on the ethereum [peggy contract](https://etherscan.io/address/0xF955C57f9EA9Dc8781965FEaE0b6A2acE2BAD6f3#code) and minted on the Injective chain. Similarly withdrawal funds will be burned on the injective chain and unlocked on the ethereum peggy contract.
 
 ### MsgSendToEth
 

.gitbook/core-modules/wasm.md

@@ -1,6 +1,6 @@
 # Wasm
 
-The `wasm` module is heart of interacting with the wasm smart contracts deployed on the injective chain, here you can find a list of [smart contracts](https://explorer.injective.network/contracts/) that are deployed on the Injective chain.
+The `wasm` module is the heart of interacting with the wasm smart contracts deployed on the injective chain, here you can find a list of [smart contracts](https://explorer.injective.network/contracts/) that are deployed on the Injective chain.
 
 ### MsgExecuteContract (Transfer)
 

.gitbook/readme/application-concepts.md

@@ -6,7 +6,7 @@ In this section we are going to explain some application (Injective) specific co
 
 The Token Factory module on Injective which allows users and contracts to create new native tokens and swap native tokens with CW20 tokens using the Mint + Burn model. This is an important feature to have on chain because representing assets from different sources to a native bank denom is crucial to allow users to access the rest of the on-chain modules like exchange, auction, insurance funds, etc. The token factory denoms are in the following format `factory/{creator address}/{subdenom}`.
 
-Combined with the `CW20AdapterContract` which acts as an creator, we allow CW20 assets to be natively represented on Injective as Token Factory denoms. The way it works is that CW20 assets are held by the `CW20AdapterContract` and minted as a factory denom for the injective address and when we want to redeem them back to CW20, they are burned from the bank module and unlocked from the `CW20AdapterContract` back to the owner address.
+Combined with the `CW20AdapterContract` which acts as a creator, we allow CW20 assets to be natively represented on Injective as Token Factory denoms. The way it works is that CW20 assets are held by the `CW20AdapterContract` and minted as a factory denom for the injective address and when we want to redeem them back to CW20, they are burned from the bank module and unlocked from the `CW20AdapterContract` back to the owner address.
 
 Example on how to redeem a factory denom to CW20:
 

.gitbook/readme/denoms-(tokens)/README.md

@@ -17,7 +17,7 @@ Token is simply a denom on the Injective chain with some meta information. The m
 
 # Token Metadata
 
-Assets on Injective are represented as denoms. Denoms (and the amounts) are not human readable and this is why we need to have a way to "attach" token metadata information for a particular denom. This is achievable using the `@injectivelabs/token-metadata` package.
+Assets on Injective are represented as denoms. Denoms (and the amounts) are not humanly readable and this is why we need to have a way to "attach" token metadata information for a particular denom. This is achievable using the `@injectivelabs/token-metadata` package.
 
 Let's recap the types of denoms we have in the Getting Started section:
 

.gitbook/transactions/transactions-cosmos/ledger-through-keplr-wallet.md

@@ -4,7 +4,7 @@ On this page, we are going to have a look at the implementation for Injective wh
 
 As explained before, Injective uses a different derivation curve from the rest of the Cosmos chains which means that the users have to use the Ethereum app (for now) to interact with Injective. 
 
-The easiest way all of the edge cases covered and a full out-of-the-box solution for all of the supported wallets on Injective I suggest you have a look at the [MsgBroadcaster + WalletStrategy ](../msgbroadcaster.md#msgbroadcaster-+-wallet-strategy)abstraction. If you want to do your own implementation, let's go through the code example togeter. 
+The easiest way all of the edge cases covered and a full out-of-the-box solution for all of the supported wallets on Injective I suggest you have a look at the [MsgBroadcaster + WalletStrategy ](../msgbroadcaster.md#msgbroadcaster-+-wallet-strategy)abstraction. If you want to do your own implementation, let's go through the code example together. 
 
 ### Overview