diff --git a/pages/stack/interop/architecture.mdx b/pages/stack/interop/architecture.mdx
index c068cdf61..c7ce7da45 100644
--- a/pages/stack/interop/architecture.mdx
+++ b/pages/stack/interop/architecture.mdx
@@ -78,7 +78,7 @@ The second transaction creates an *executing message* on the destination chain.
 This executing message could result in a contract function being executed on the destination chain.
 
 The initiating message is simply a log event.
-Any log event on any chain that inteoperates with the destination can initiate a cross domain message.
+Any log event on any chain that interoperates with the destination can initiate a cross domain message.
 
 The transaction that receives the message on the destination chain calls a contract called [`CrossL2Inbox`](https://specs.optimism.io/interop/predeploys.html#crossl2inbox).
 This call can be at the top level, directly from the externally owned account, or come through a smart contract.
diff --git a/pages/stack/interop/cross-chain-message.mdx b/pages/stack/interop/cross-chain-message.mdx
index bd201b6e5..509c618f0 100644
--- a/pages/stack/interop/cross-chain-message.mdx
+++ b/pages/stack/interop/cross-chain-message.mdx
@@ -27,7 +27,7 @@ To send a cross-chain message on the Superchain using [Superchain interoperabili
 
 <Image src="/img/op-stack/protocol/cross-chain-message.png" alt="Anatomy of Cross-Chain Message with Interop" width={700} height={500} />
 
-In the example above, `Ox123` sends 1 OP from OP Mainnet to Base, but this applies to any asset using the SuperchainERC20 token standard.
+In the example above, `0x123` sends 1 OP from OP Mainnet to Base, but this applies to any asset using the SuperchainERC20 token standard.
 
 ## Next steps