diff --git a/crates/relayer-types/src/core/ics04_channel/error.rs b/crates/relayer-types/src/core/ics04_channel/error.rs
index 8dea11e602..acdd9e8682 100644
--- a/crates/relayer-types/src/core/ics04_channel/error.rs
+++ b/crates/relayer-types/src/core/ics04_channel/error.rs
@@ -138,7 +138,7 @@ define_error! {
         InvalidVersionLengthConnection
             | _ | { "single version must be negotiated on connection before opening channel" },
 
-        ChannelFeatureNotSuportedByConnection
+        ChannelFeatureNotSupportedByConnection
             | _ | { "the channel ordering is not supported by connection" },
 
         ChannelNotFound
diff --git a/crates/relayer/src/supervisor.rs b/crates/relayer/src/supervisor.rs
index c994ac6585..431894c3b1 100644
--- a/crates/relayer/src/supervisor.rs
+++ b/crates/relayer/src/supervisor.rs
@@ -889,7 +889,7 @@ fn process_batch<Chain: ChainHandle>(
 /// The labels `chain_id` represents the chain sending the event, and `counterparty_chain_id` represents
 /// the chain receiving the event.
 /// So successfully sending a packet from chain A to chain B will result in first a SendPacket
-/// event with `chain_id = A` and `counterparty_chain_id = B` and then a WriteAcknowlegment
+/// event with `chain_id = A` and `counterparty_chain_id = B` and then a WriteAcknowledgment
 /// event with `chain_id = B` and `counterparty_chain_id = A`.
 fn send_telemetry<Src, Dst>(
     src: &Src,
diff --git a/tools/test-framework/src/docs/walkthroughs/ordered_channel.rs b/tools/test-framework/src/docs/walkthroughs/ordered_channel.rs
index 6f717d436e..173e5839cb 100644
--- a/tools/test-framework/src/docs/walkthroughs/ordered_channel.rs
+++ b/tools/test-framework/src/docs/walkthroughs/ordered_channel.rs
@@ -118,7 +118,7 @@
 //! ```
 //!
 //! The test is run by calling the `run_binary_channel_test` function, passing it
-//! a struct, `OrderdChannelTest`, upon which we implement the `TestOverrides`
+//! a struct, `OrderedChannelTest`, upon which we implement the `TestOverrides`
 //! trait in order to configure the behavior of the test. We define the
 //! `should_spawn_supervisor` function to have it return false in order to not
 //! automatically spawn a supervisor when the relayer is initialized; this is