From 8286252ed7f74c1ba486434a02ca1df953cf12e8 Mon Sep 17 00:00:00 2001 From: Maks Date: Tue, 17 Dec 2024 04:11:25 +0100 Subject: [PATCH] Update interop.md --- docs/src/specs/zk_chains/interop.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/specs/zk_chains/interop.md b/docs/src/specs/zk_chains/interop.md index 947742909b8d..170d223ae5a0 100644 --- a/docs/src/specs/zk_chains/interop.md +++ b/docs/src/specs/zk_chains/interop.md @@ -19,7 +19,7 @@ The interop process has 7 main steps, each with its substeps: 1. Starting the transaction on the sending chain - - The user/calls calls the Bridgehub contract. If they want to use a bridge they call + - The user/calls the Bridgehub contract. If they want to use a bridge they call `requestL2TransactionTwoBridges`, if they want to make a direct call they call `requestL2TransactionDirect` function. - The Bridgehub collects the base token fees necessary for the interop tx to be processed on the destination chain, @@ -39,7 +39,7 @@ The interop process has 7 main steps, each with its substeps: 6. Receiving the tx on the destination chain - On the destination chain the xL2 txs is verified. This means the merkle proof is checked agains the MessageRoot. - This shows the the xL2 txs was indeed sent. + This shows the xL2 txs was indeed sent. - After this the txs can be executed. The tx hash is stored in the L2Nullifier contract, so that the txs cannot be replayed. - The specified contract is called, with the calldata, and the message sender =