Next steps and logs reference

Author: bradleycamacho

pages/interop/message-expiration.mdx

@@ -48,4 +48,10 @@ The process to reemit an expired message:
     *   `_target`: Target contract or wallet address.
     *   `message`: Message payload to call target with.
 
-2.  [Relay the new message](/interop/message-passing) as normal.
+2.  [Relay the new message](C/interop/message-passing) as normal.
+
+## Next steps
+
+*   [Build a revolutionary app](/app-developers/get-started) that uses multiple blockchains within the Superchain
+*   Learn how to [pass messages between blockchains](/interop/tutorials/message-passing)
+*   Deploy a [SuperchainERC20](/interop/tutorials/deploy-superchain-erc20) to the Superchain

pages/interop/reading-logs.mdx

@@ -27,6 +27,10 @@ This enables developers to:
 *   Build cross-chain applications that react to events happening across the Superchain.
 *   Create novel applications that leverage data from multiple chains.
 
+<callout>
+The destination chain must execute initiating message or event within the [expiry window of 7 days](interop/message-expiration).
+</callout>
+
 ## Why use `CrossL2Inbox`?
 
 *   **Reference existing logs**: Allows contracts to verify and use logs that were already emitted, without requiring those logs to have been sent as cross-chain messages.