From 9cc124d82e598c48c3138dca60d1cd9bcfb15dee Mon Sep 17 00:00:00 2001
From: xiaolou86 <20718693+xiaolou86@users.noreply.github.com>
Date: Mon, 16 Oct 2023 11:52:18 +0800
Subject: [PATCH] docs: fix typos

---
 IBC.md                          | 4 ++--
 MIGRATING.md                    | 4 ++--
 docs/simulate_riffle_shuffle.py | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/IBC.md b/IBC.md
index fcefc92ffe..fa07f2ad26 100644
--- a/IBC.md
+++ b/IBC.md
@@ -71,7 +71,7 @@ This particular contract above accepts
 and sends those to a remote chain, as well as receiving the tokens back and
 releasing the original cw20 token to a new owner. It does not (yet) allow
 minting coins originating from the remote chain. I recommend opening up the
-source code for that contract and refering to it when you want a concrete
+source code for that contract and referring to it when you want a concrete
 example for anything discussed below.
 
 In order to enable IBC communication, a contract must expose the following 6
@@ -168,7 +168,7 @@ pub fn ibc_channel_connect(
 ```
 
 At this point, it is expected that the contract updates its internal state and
-may return `CosmosMsg` in the `Reponse` to interact with other contracts, just
+may return `CosmosMsg` in the `Response` to interact with other contracts, just
 like in `execute`. In particular, you will most likely want to store the local
 channel_id (`channel.endpoint.channel_id`) in the contract's storage, so it
 knows what open channels it has (and can expose those via queries or maintain
diff --git a/MIGRATING.md b/MIGRATING.md
index d06877b406..343e5e8aff 100644
--- a/MIGRATING.md
+++ b/MIGRATING.md
@@ -1044,7 +1044,7 @@ arbitrary ones.
   because it did not set the address for one withdraw only but for all following
   withdrawls. Since withdrawls are [triggered by different
   events][distribution docs] such as validators changing their commission rate,
-  an address that was set for a one-time withdrawl would be used for future
+  an address that was set for a one-time withdrawal would be used for future
   withdrawls not considered by the contract author.
 
   If the contract never set a withdraw address other than the contract itself
@@ -1055,7 +1055,7 @@ arbitrary ones.
 
   1. `SetWithdrawAddress { address: recipient }` to temporarily change the
      recipient
-  2. `WithdrawDelegatorReward { validator }` to do a manual withdrawl from the
+  2. `WithdrawDelegatorReward { validator }` to do a manual withdrawal from the
      given validator
   3. `SetWithdrawAddress { address: env.contract.address.into() }` to change it
      back for all future withdrawls
diff --git a/docs/simulate_riffle_shuffle.py b/docs/simulate_riffle_shuffle.py
index c6a33c1355..3c9227374a 100644
--- a/docs/simulate_riffle_shuffle.py
+++ b/docs/simulate_riffle_shuffle.py
@@ -1,6 +1,6 @@
 import functools
 
-# Create a funtion that executed f recusively n times, i.e. f**n
+# Create a function that executed f recusively n times, i.e. f**n
 def power(f, n):
     functions = [f for _ in range(n)]
     def compose2(f, g):