From 1853e569b86fdef78dfcccfbc5a2410910061f6d Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 26 Jan 2024 17:43:45 +0200
Subject: [PATCH] chore: fixes by misspell-fixer (#5754)

Co-authored-by: crodriguezvega <crodriguezvega@users.noreply.github.com>
Co-authored-by: Carlos Rodriguez <carlos@interchain.io>
---
 docs/docs/01-ibc/03-apps/01-apps.md                          | 2 +-
 docs/versioned_docs/version-v8.0.x/01-ibc/03-apps/01-apps.md | 2 +-
 modules/apps/29-fee/keeper/relay_test.go                     | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/docs/01-ibc/03-apps/01-apps.md b/docs/docs/01-ibc/03-apps/01-apps.md
index 92a07e2de04..48ea8fc82c3 100644
--- a/docs/docs/01-ibc/03-apps/01-apps.md
+++ b/docs/docs/01-ibc/03-apps/01-apps.md
@@ -413,7 +413,7 @@ message Acknowledgement {
 
 After a module writes an acknowledgement, a relayer can relay back the acknowledgement to the sender module. The sender module can
 then process the acknowledgement using the `OnAcknowledgementPacket` callback. The contents of the
-acknowledgement is entirely upto the modules on the channel (just like the packet data); however, it
+acknowledgement is entirely up to the modules on the channel (just like the packet data); however, it
 may often contain information on whether the packet was successfully processed along
 with some additional data that could be useful for remediation if the packet processing failed.
 
diff --git a/docs/versioned_docs/version-v8.0.x/01-ibc/03-apps/01-apps.md b/docs/versioned_docs/version-v8.0.x/01-ibc/03-apps/01-apps.md
index 2e9fdf4bb90..fb5013149e0 100644
--- a/docs/versioned_docs/version-v8.0.x/01-ibc/03-apps/01-apps.md
+++ b/docs/versioned_docs/version-v8.0.x/01-ibc/03-apps/01-apps.md
@@ -413,7 +413,7 @@ message Acknowledgement {
 
 After a module writes an acknowledgement, a relayer can relay back the acknowledgement to the sender module. The sender module can
 then process the acknowledgement using the `OnAcknowledgementPacket` callback. The contents of the
-acknowledgement is entirely upto the modules on the channel (just like the packet data); however, it
+acknowledgement is entirely up to the modules on the channel (just like the packet data); however, it
 may often contain information on whether the packet was successfully processed along
 with some additional data that could be useful for remediation if the packet processing failed.
 
diff --git a/modules/apps/29-fee/keeper/relay_test.go b/modules/apps/29-fee/keeper/relay_test.go
index 23ae6cec9b9..8918b325f3b 100644
--- a/modules/apps/29-fee/keeper/relay_test.go
+++ b/modules/apps/29-fee/keeper/relay_test.go
@@ -67,8 +67,8 @@ func (suite *KeeperTestSuite) TestWriteAcknowledgementAsync() {
 				suite.Require().False(found)
 
 				expectedAck := types.NewIncentivizedAcknowledgement(suite.chainB.SenderAccount.GetAddress().String(), ack.Acknowledgement(), ack.Success())
-				commitedAck, _ := suite.chainB.GetSimApp().GetIBCKeeper().ChannelKeeper.GetPacketAcknowledgement(suite.chainB.GetContext(), packet.DestinationPort, packet.DestinationChannel, 1)
-				suite.Require().Equal(commitedAck, channeltypes.CommitAcknowledgement(expectedAck.Acknowledgement()))
+				committedAck, _ := suite.chainB.GetSimApp().GetIBCKeeper().ChannelKeeper.GetPacketAcknowledgement(suite.chainB.GetContext(), packet.DestinationPort, packet.DestinationChannel, 1)
+				suite.Require().Equal(committedAck, channeltypes.CommitAcknowledgement(expectedAck.Acknowledgement()))
 			} else {
 				suite.Require().Error(err)
 			}