Updated explainer

pages/stack/interop/_meta.json

@@ -1,10 +1,10 @@
 {
     "explainer": "Interop explainer",
-    "architecture": "Architecture",
+    "predeploy": "Interop predeploys",
     "devnet": "Interop devnet",
     "supersim": "Supersim Multichain Development Environment",
-    "cross-chain-message": "Anatomy of cross-chain message",
     "message-passing": "Interop message passing",
     "op-supervisor": "OP Supervisor",
-    "assets": "Assets"
+    "assets": "Assets",
+    "security": "Cross-chain security"
 }

pages/stack/interop/architecture.mdx

@@ -44,7 +44,7 @@ graph LR
 ```
 
 OP-Supervisor holds a database of all the log events of all the chains in the interoperability cluster.
-Every event can potentially initiate a cross domain message, and it is the job of OP-Supervisor to validate that the log event really happened on the source chain.
+Every event can potentially initiate a cross-domain message, and it's the job of OP-Supervisor to validate that the log event really happened on the source chain.
 Additionally, OP-Supervisor reads information from L1's consensus layer to determine the transaction safety of L2 blocks.
 
 ## How messages get from one chain to the other
@@ -72,13 +72,13 @@ sequenceDiagram
     note over dst-geth: Executing Message
 ```
 
-Cross domain messages require two transactions.
+Cross-domain messages require two transactions.
 The first transaction creates an *initiating message* on the source chain.
 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 inteoperates 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.