diff --git a/pages/builders/chain-operators/architecture.mdx b/pages/builders/chain-operators/architecture.mdx
index bfbdd50d1..60f2d2528 100644
--- a/pages/builders/chain-operators/architecture.mdx
+++ b/pages/builders/chain-operators/architecture.mdx
@@ -160,11 +160,11 @@ In addition to the core protocol components, the following offchain services are
### op-conductor
-The [op-conductor](/tools/op-conductor) RPC can act as a leader-aware rpc proxy for op-batcher (proxies the necessary op-geth / op-node RPC methods if the node is the leader).
+The [op-conductor](/builders/chain-operators/tools/op-conductor) RPC can act as a leader-aware rpc proxy for op-batcher (proxies the necessary op-geth / op-node RPC methods if the node is the leader).
### op-challenger
-The [op-challenger](/tools/op-challenger) verifies the correctness of the L2 state by challenging invalid state transitions. This ensures the network's security and validity.
+The [op-challenger](/builders/chain-operators/tools/op-challenger) verifies the correctness of the L2 state by challenging invalid state transitions. This ensures the network's security and validity.
### Ethereum L1 nodes
diff --git a/pages/stack/interop.mdx b/pages/stack/interop.mdx
index 0fa84217b..0e1dbef04 100644
--- a/pages/stack/interop.mdx
+++ b/pages/stack/interop.mdx
@@ -13,22 +13,21 @@ Documentation covering Cross Chain Message, Explainer, Message Passing, Op Super
-
-
-
-
+
-
+
-
+
+
+
diff --git a/pages/stack/interop/explainer.mdx b/pages/stack/interop/explainer.mdx
index 3dc143a2f..777f4d560 100644
--- a/pages/stack/interop/explainer.mdx
+++ b/pages/stack/interop/explainer.mdx
@@ -104,7 +104,7 @@ The call to `CrossL2Inbox`, also known as the *executing message*, needs to [ide
`CrossL2Inbox` can either [validate the message exists](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L171-L185), or [call a contract if the message exists](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L171-L185).
-[For more information, see the cross-chain messages anatomy page](./cross-chain-message).
+[For more information, see the cross-chain messages anatomy page](#how-messages-get-from-one-chain-to-the-other).
## Block safety levels
@@ -211,7 +211,7 @@ flowchart LR
A <--> C <--> E <--> B <--> D <--> A
```
-Each blockchain in the Superchain interop cluster shares the same security model to mitigate the weakest-link scenario. As outlined in the [Standard Rollup Charter](superchain/blockspace-charter), these chains share the same L1 `ProxyAdmin` Owner. Any changes to the Superchain interop cluster must follow the standard Protocol Upgrade vote procedure—the established governance process for Superchain modifications.
+Each blockchain in the Superchain interop cluster shares the same security model to mitigate the weakest-link scenario. As outlined in the [Standard Rollup Charter](/superchain/blockspace-charter), these chains share the same L1 `ProxyAdmin` Owner. Any changes to the Superchain interop cluster must follow the standard Protocol Upgrade vote procedure—the established governance process for Superchain modifications.
{/*
## Interop assets
@@ -227,6 +227,6 @@ This means ETH and ERC-20s can seamlessly and securely move across L2s, and inte
## Next steps
* Watch this video that gives an [overview of OP Stack interoperability](https://www.youtube.com/watch?v=FKc5RgjtGes).
-* Learn more about the [predeploys that have been added to the OP Stack to enable interoperability](stack/interop/predeploy).
-* Use [Supersim](stack/interop/tools/supersim), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
+* Learn more about the [predeploys that have been added to the OP Stack to enable interoperability](/stack/interop/predeploy).
+* Use [Supersim](/stack/interop/tools/supersim), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
* For more info about how OP Stack interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html).
diff --git a/pages/stack/interop/message-passing.mdx b/pages/stack/interop/message-passing.mdx
index af661135b..8bcd46889 100644
--- a/pages/stack/interop/message-passing.mdx
+++ b/pages/stack/interop/message-passing.mdx
@@ -61,6 +61,6 @@ For a practical example, see our [cross-chain ping pong tutorial](https://supers
## Next steps
-* Read about the [anatomy of a cross-chain message](/stack/interop/cross-chain-message)
+* Read about the [anatomy of a cross-chain message](/stack/interop/explainer#how-messages-get-from-one-chain-to-the-other)
* Try [Supersim](supersim) for testing cross-chain messages locally
* Learn about [manually relaying messages](https://supersim.pages.dev/guides/interop/viem?#viem-to-send-and-relay-interop-messages)
diff --git a/pages/stack/interop/op-supervisor.mdx b/pages/stack/interop/op-supervisor.mdx
index b130e13ed..3defbd5e8 100644
--- a/pages/stack/interop/op-supervisor.mdx
+++ b/pages/stack/interop/op-supervisor.mdx
@@ -68,5 +68,5 @@ Benefits:
## Next steps
-* Want to learn more? Read our guide on the anatomy of a [cross-chain message](/stack/interop/cross-chain-message) or check out this [interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes).
+* Want to learn more? Read our guide on the anatomy of a [cross-chain message](/stack/interop/explainer#how-messages-get-from-one-chain-to-the-other) or check out this [interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes).
* For more info about how OP Stack interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html).
diff --git a/pages/stack/interop/tools.mdx b/pages/stack/interop/tools.mdx
new file mode 100644
index 000000000..38bfbb531
--- /dev/null
+++ b/pages/stack/interop/tools.mdx
@@ -0,0 +1,18 @@
+---
+title: Assets
+description: Documentation covering Interop devnet, Supersim in the Interop section of the OP Stack ecosystem.
+lang: en-US
+---
+
+import { Card, Cards } from 'nextra/components'
+
+# Interop
+
+Documentation covering Interop devnet, Supersim in the Interop section of the OP Stack ecosystem.
+
+
+
+
+
+
+
diff --git a/pages/stack/interop/tools/devnet.mdx b/pages/stack/interop/tools/devnet.mdx
index 17c19a74b..c82960893 100644
--- a/pages/stack/interop/tools/devnet.mdx
+++ b/pages/stack/interop/tools/devnet.mdx
@@ -1,12 +1,12 @@
---
-title: Interop Devnet - Coming Soon
+title: Interop Devnet (coming soon)
lang: en-US
description: Details on the public interoperability devnets.
---
import { Callout, Tabs, Steps } from 'nextra/components'
-# Interop Devnet - Coming Soon
+# Interop devnet (coming soon)
Interop devnet is currently in active development and may experience periods of instability, including potential outages, as the networks is regularly updated and improved. Developers should expect some level of unreliability when interacting with the devnet. The devnet is intended for testing and development purposes only, and should not be relied upon for mission-critical applications.
@@ -62,7 +62,7 @@ NOTE: The current Interop devnet has been deprecated. This page will be updated
## Next steps
-* Want to start with local development? Use [Supersim](/stack/interop/supersim), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
-* Read about [interop message passing](/stack/interop/cross-chain-message) to see how you can implement it yourself on this devnet.
+* Want to start with local development? Use [Supersim](/stack/interop/tools/supersim), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
+* Read about [Interop message passing](/stack/interop/explainer#how-messages-get-from-one-chain-to-the-other) to see how you can implement it yourself on this devnet.
*/}