diff --git a/app-developers/reference/tokens/compatible-tokens.mdx b/app-developers/reference/tokens/compatible-tokens.mdx
index 8cd3ed934..c33c0c123 100644
--- a/app-developers/reference/tokens/compatible-tokens.mdx
+++ b/app-developers/reference/tokens/compatible-tokens.mdx
@@ -89,7 +89,11 @@ CCT is a token standard used to send, receive, and compose tokens across chains
 
 ### OFT
 
-OFT is a token standard used to send, receive, and compose tokens across chains LayerZero supports. More information will be added about how OFTs can benefit from Superchain interop at a later date. 
+OFT is a token standard used to send, receive, and compose tokens across chains LayerZero supports.
+
+<Info>
+  Integration documentation for OFTs with Superchain interop is currently being developed. Check back for updates or refer to [LayerZero's OFT documentation](https://docs.layerzero.network/v2/developers/evm/oft/quickstart) for current implementation details.
+</Info>
 
 *   **Security:** Variable due to weakest-link scenario based on allowlisted verification mechanisms.
 *   **Latency:** 1-block latency within the Superchain. Outside the Superchain, latency is variable based on allowlisted verification (DVN) mechanism.
@@ -100,7 +104,11 @@ OFT is a token standard used to send, receive, and compose tokens across chains
 
 ### NTT
 
-NTT is a token standard used to send, receive, and compose tokens across chains Wormhole supports. More information will be added about how NTTs can benefit from Superchain interop at a later date. 
+NTT is a token standard used to send, receive, and compose tokens across chains Wormhole supports.
+
+<Info>
+  Integration documentation for NTTs with Superchain interop is currently being developed. Check back for updates or refer to [Wormhole's NTT documentation](https://docs.wormhole.com/wormhole/native-token-transfers) for current implementation details.
+</Info>
 
 *   **Security:** Variable due to weakest-link scenario based on allowlisted verification mechanisms.
 *   **Latency:** 1-block latency within the Superchain. Outside the Superchain, latency is variable based on allowlisted verification (transceiver) mechanism.
diff --git a/index.mdx b/index.mdx
index 07d99c0d6..5048b426b 100644
--- a/index.mdx
+++ b/index.mdx
@@ -16,14 +16,14 @@ mode: "wide"
 ## Components 
 
 The OP Stack is an open-source, modular, Ethereum Layer 2 rollup stack.
-Before you deploy, it is important to understand how the key components and how they come together to create your blockchain.
+Before you deploy, it is important to understand the key components and how they come together to create your blockchain.
 
-- **L1 Smart contracts**: A set of smart contracts to be deployed on Ethereum to bridge between the L1 and L2 domains and manage aspects of the rollup. 
-- **Sequencer**: A single privileged node that accept and derive user transactions on the network to construct the blockchain. 
-- **Batcher**: A sequencer service that publishes L2 transactions onto Ethereum. 
+- **L1 Smart contracts**: A set of smart contracts to be deployed on Ethereum to bridge between the L1 and L2 domains and manage aspects of the rollup.
+- **Sequencer**: A single privileged node that accepts and derives user transactions on the network to construct the blockchain.
+- **Batcher**: A sequencer service that publishes L2 transactions onto Ethereum.
 Using Ethereum as a data availability layer, the OP Stack inherits Ethereum's security properties by allowing any node to derive the state of the L2 blockchain from L1.
 - **Proposer**: A service responsible for publishing the L2 state root to Ethereum which enables user withdrawals of assets.
-- **Challenger**: The challenger enforces network security by disputing invalid state roots that have been posted to Ethereum. 
+- **Challenger**: The challenger enforces network security by disputing invalid state roots that have been posted to Ethereum.
 
 ## Deployment 
 
@@ -34,7 +34,7 @@ The following section will walk you through the sequence of steps a chain operat
     Using a CLI tool called [op-deployer](/chain-operators/tools/op-deployer) you will configure your chain and then deploy the smart contracts on Ethereum.
   </Step>
   <Step title="Validate your deployment">
-    After deploying the L1 smart contracts you will use [op-validator](/chain-operators/tools/op-validator) to verify that your deployment configurations what you expect.
+    After deploying the L1 smart contracts you will use [op-validator](/chain-operators/tools/op-validator) to verify that your deployment configurations match what you expect.
   </Step>
   <Step title="Chain genesis creation">
     After deploying the L1 smart contracts, you will use [op-deployer](/chain-operators/tools/op-deployer) to generate two files necessary to run nodes on the L2 network:
@@ -61,4 +61,4 @@ The following section will walk you through the sequence of steps a chain operat
 ## Next Steps
 
 Of course there is a lot more work to do ensure you're operating a highly available chain.
-Take a look at some of the [chain operator best practices](/chain-operators/guides/management/best-practices) to get an idea of some of the things you'll need to keep in mind.
\ No newline at end of file
+Take a look at some of the [chain operator best practices](/chain-operators/guides/management/best-practices) to get an idea of some of the things you'll need to keep in mind.