Apply suggestions from code review

Co-authored-by: Blessing Krofegha <bkrofegha@gmail.com>

Author: qbzzt

pages/stack/interop/superchain-weth.mdx

@@ -12,15 +12,15 @@ import { InteropCallout } from '@/components/WipCallout'
 
 # Interoperable ETH
 
-InteroperableETH is implemented using three contracts:
+InteroperableETH enables seamless ETH transfers across Superchain blockchains. It is implemented using three key contracts:
 
-*   [`SuperchainWETH`](https://github.com/ethereum-optimism/optimism/blob/develop/contracts-bedrock/src/L2/SuperchainWETH.sol) is the bridge that lets you move ETH from one Superchain blockchain to another.
-*   [`ETHLiquidity`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/ETHLiquidity.sol), which serves as a liquidity provider for ETH transfers.
-    It is used by `SuperchainWETH` as a liquidity repository to be able to provide ETH on the destination chain when transferring.
-*   [`L2ToL2CrossDomainMessenger`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/L2ToL2CrossDomainMessenger.sol) is used to [pass messages between different chains](./message-passing).
+*   [`SuperchainWETH`](https://github.com/ethereum-optimism/optimism/blob/develop/contracts-bedrock/src/L2/SuperchainWETH.sol): A bridge contract that facilitates ETH transfers between Superchain blockchains.
+*   [`ETHLiquidity`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/ETHLiquidity.sol): A liquidity provider for ETH transfers. 
+`SuperchainWETH` uses this contract as a liquidity repository to ensure ETH availability on the destination chain.
+*   [`L2ToL2CrossDomainMessenger`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/L2ToL2CrossDomainMessenger.sol): A messaging contract that [facilitates cross-chain communication](/message-passing).
 
-InteroperableETH works by depositing ETH on the source chain's `ETHLiquidity` and withdrawing an equivalent amount on the destination chain.
-This approach addresses issues such as liquidity fragmentation and poor user experiences caused by asset wrapping or reliance on liquidity pools.
+InteroperableETH deposits ETH into the `ETHLiquidity` contract on the source chain and withdraws an equivalent amount on the destination chain. 
+This mechanism improves capital efficiency and eliminates liquidity fragmentation and poor user experiences caused by asset wrapping or reliance on liquidity pools.
 
 ## Features and benefits
 
@@ -74,33 +74,39 @@ sequenceDiagram
 1.  The user (or a contract operating on a user's behalf) calls `SuperchainWETH.sendETH` with a destination address and a chainId.
     This call should have an attached amount of ETH.
 
-2.  `SuperchainWETH` sends the amount of ETH to `ETHLiquidity`, removing it from circulation on the source chain.
+2.  `SuperchainWETH` transfers the specified ETH amount to `ETHLiquidity`, removing it from circulation on the source chain.
 
-3.  `SuperchainWETH` on the source chain sends a [`relayETH`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/SuperchainWETH.sol#L125-L145) call to the `SuperchainWETH` on the destination chain using [`L2ToL2CrossDomainMessenger`](./message-passing).
+3.  `SuperchainWETH` on the source chain sends a [`relayETH`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/SuperchainWETH.sol#L125-L145) message to `SuperchainWETH` on the destination chain using the [`L2ToL2CrossDomainMessenger`](/message-passing).
 
 #### Executing message
 
-4.  Some offchain entity submits a transaction with the executing message.
-    Any address can submit such a transaction, but it has to have ETH on the destination chain to do so.
-    We expect that usually this will be a relayer rather than the user because the user won't have ETH on the destination chain yet.
+4.  An off-chain entity submits a transaction to execute the message.
+    Any address can submit this transaction, but it must have ETH on the destination chain.
+    Typically, a relayer submits the transaction, since the user does not yet have ETH on the destination chain.
 
-5.  `L2ToL2CrossDomainMessenger` on the destination chain calls `SuperchainWETH` with the source of the ETH, the destination address, and the amount.
+5.  `L2ToL2CrossDomainMessenger` on the destination chain calls `SuperchainWETH` with the following details:
 
-    `SuperchainWETH` runs several sanity checks:
+*   Source of the ETH
+*   Destination address
+*   Amount of ETH
 
-    *   The `relayETH` call has to come directly from `L2ToL2CrossDomainMessenger`.
-    *   The interop message has to have been sent by `SuperchainWETH`
+    `SuperchainWETH` performs several sanity checks:
 
-6.  `SuperchainWETH` withdraws the requested amount of ETH from `ETHLiquidity`.
-    It is the only contract allowed to withdraw from `ETHLiquidity`, which adds to the ETH in circulation on the destination chain.
+    *   The `relayETH` call must originate from `L2ToL2CrossDomainMessenger`.
+    *   The interop message must have been sent by `SuperchainWETH`
 
-7.  `SuperchainWETH` uses [`SafeSend`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/universal/SafeSend.sol) to send the ETH.
-    This means that even if the destination is a smart contract, its custom logic does not get called, [in contrast to normal ETH transfers](https://docs.base.org/base-learn/docs/address-and-payable/#receiving-ether-with-payable-addresses).
+6.  `SuperchainWETH` withdraws the specified amount of ETH from `ETHLiquidity`.
+    Only `SuperchainWETH` can withdraw from `ETHLiquidity`, ensuring that the ETH is correctly reintroduced into circulation on the destination chain.
+
+7.  `SuperchainWETH` uses [`SafeSend`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/universal/SafeSend.sol) to send ETH.
+    This ensures that even if the destination is a smart contract, its custom logic is not executed.
+This behavior differs from [standard ETH transfers](https://docs.base.org/base-learn/docs/address-and-payable/#receiving-ether-with-payable-addresses), where smart contracts can trigger custom logic upon receiving ETH.
 
 ## L1 Treasury
 
-Every ETH in circulation on the Superchain (all the ETH except for those held by `ETHLiquidity`) needs to be backed by ETH held on L1.
-This is done using a lockbox contract on L1 that holds all the ETH ever bridged to [chains in the Superchain interop cluster](explainer#superchain-interop-cluster) and not yet withdrawn.
+Every ETH in circulation on the Superchain—excluding ETH held by `ETHLiquidity`—must be backed by ETH on L1.
+
+This is enforced by a lockbox contract on L1, which holds all ETH bridged to [Superchain interop cluster chains](https://github.com/ethereum-optimism/docs/pull/1297/explainer#superchain-interop-cluster) that has not yet been withdrawn.
 New ETH can only be minted on L2 when it is locked on L1, and it is burned on L2 before it can be released from the lockbox.
 
 Here is an example of how this works.