From 3b9ec008999973469aeab4bbdbcb44ff4886b8b8 Mon Sep 17 00:00:00 2001
From: shubh7791 <103331736+shubh7791@users.noreply.github.com>
Date: Mon, 28 Oct 2024 21:39:46 +0530
Subject: [PATCH] Fix typo: MsgChannelCloseConfim to MsgChannelCloseConfirm
 (#1509)

Co-authored-by: Justin Tieri <37750742+jtieri@users.noreply.github.com>
---
 docs/chain_implementation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/chain_implementation.md b/docs/chain_implementation.md
index ba0121c6d..cf33e9417 100644
--- a/docs/chain_implementation.md
+++ b/docs/chain_implementation.md
@@ -108,7 +108,7 @@ For Comet BFT chains, the IBC messages are parsed in the `CosmosChainProcessor`
 
 - For client IBC messages (e.g. MsgCreateClient, MsgUpdateClient, MsgUpgradeClient, MsgSubmitMisbehaviour), message should be parsed into `provider.ClientState`.
 - For connection handshake IBC messages (e.g. MsgConnectionOpenInit, MsgConnectionOpenTry, MsgConnectionOpenAck, MsgConnectionOpenConfirm), message should be parsed into `provider.ConnectionInfo`
-- For channel handshake IBC messages (e.g. MsgChannelOpenInit, MsgChannelOpenTry, MsgChannelOpenAck, MsgChannelOpenConfirm, MsgChannelCloseInit, MsgChannelCloseConfim), message should be parsed into `provider.ChannelInfo`
+- For channel handshake IBC messages (e.g. MsgChannelOpenInit, MsgChannelOpenTry, MsgChannelOpenAck, MsgChannelOpenConfirm, MsgChannelCloseInit, MsgChannelCloseConfirm), message should be parsed into `provider.ChannelInfo`
 - For packet-flow IBC messages (e.g. MsgTransfer, MsgRecvPacket, MsgAcknowledgement), message should be parsed into `provider.PacketInfo`
 
 #### Message Handlers