Typos

AbstractSDK · Jan 27, 2025 · 867e6b1 · 867e6b1
1 parent 9ad311b
commit 867e6b1
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/src/integrations/cw-multi-test.md b/docs/src/integrations/cw-multi-test.md
@@ -40,7 +40,7 @@ This environment mocks the actual on-chain execution exactly.
 
 > - This environment uses the actual functions of your contract **without** having to compile them into WASM. When you are calling `upload` with this environment, no wasm files are included in the test environment. This allows for better debugging of your contract code.
 >
-> - You will need to have implemented the `wrapper` function for interacting the the `Mock` environment. This function will allow you to "connect" your contract endpoints to your `Contract` struct. [See the dedicated page for more details](../contracts/interfaces.md#creating-an-interface).
+> - You will need to have implemented the `wrapper` function for interacting with the `Mock` environment. This function will allow you to "connect" your contract endpoints to your `Contract` struct. [See the dedicated page for more details](../contracts/interfaces.md#creating-an-interface).
 >
 > - **_NOTE:_** Keep in mind that `cw-multi-test` is based solely in rust and that a lot of actual blockchain modules are not mocked in the environment. The main cosmos modules are there (Bank, Staking), but some very useful ones (tokenfactory, ibc) as well as Stargate messages are not supported by the environment.
 

diff --git a/docs/src/interchain/integrations/mock.md b/docs/src/interchain/integrations/mock.md
@@ -55,7 +55,7 @@ You can also add mocks manually to the `interchain` object, after instantiation:
 
 All interchain environments are centered around the `await_single_packet` function. In the `Mock` case, this function is responsible for relaying the packets between the different chains. Using the exact same interface as with other environments, it takes care of all packet relaying procedures.
 
-This function will relay a packets successfully from the receiving chain back the the source chain. Here is what the full cycle looks like:
+This function will relay a packets successfully from the receiving chain back to the source chain. Here is what the full cycle looks like:
 
 1. <span style="color:purple">⬤</span> On the `source chain`, it queries the packet data associated with the packet channel and sequence.
 2. <span style="color:red">⬤</span> On the `destination chain`, it triggers a receive transaction for that packet.