docs: remove repetitive words

Signed-off-by: RiceChuan <[email protected]>
matter-labs · Dec 13, 2024 · 39a13e9 · 39a13e9
1 parent 3cffdb2
commit 39a13e9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/src/specs/data_availability/overview.md b/docs/src/specs/data_availability/overview.md
@@ -13,7 +13,7 @@ We also [compress](./compression.md) all the data that we send to L1, to reduce
 By posting all the data to L1, we can [reconstruct](./reconstruction.md) the state of the chain from the data on L1.
 This is a key security property of the rollup.
 
-The the chain chooses not to post this data, they become a validium. This makes transactions there much cheaper, but
+The chain chooses not to post this data, they become a validium. This makes transactions there much cheaper, but
 less secure. Because we use state diffs to post data, we can combine the rollup and validium features, by separating
 storage slots that need to post data from the ones that don't. This construction combines the benefits of rollups and
 validiums, and it is called a [zkPorter](./validium_zk_porter.md).
diff --git a/docs/src/specs/zk_chains/interop.md b/docs/src/specs/zk_chains/interop.md
@@ -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 =