From f675eb4122626344669a194cb18d97f8b40b5f45 Mon Sep 17 00:00:00 2001 From: Antonio Viggiano Date: Fri, 25 Oct 2024 07:57:13 -0300 Subject: [PATCH] fix: typo duplicated word (#243) Remove duplicate word # Description ## Linked Issues ## Additional context Co-authored-by: Antonio --- content/10.zk-stack/05.concepts/99.l1_l2_communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/10.zk-stack/05.concepts/99.l1_l2_communication.md b/content/10.zk-stack/05.concepts/99.l1_l2_communication.md index 3002ea0b..7ec7ce37 100644 --- a/content/10.zk-stack/05.concepts/99.l1_l2_communication.md +++ b/content/10.zk-stack/05.concepts/99.l1_l2_communication.md @@ -58,7 +58,7 @@ the Merkle tree’s root hash was included into the batch commitment also. ### Important system values Two `key` and `value` fields are enough for a lot of system-related use-cases, such as sending timestamp of the batch, -previous batch hash, etc. They were and are used +previous batch hash, etc. They were and are [used](https://github.com/code-423n4/2023-10-zksync/blob/ef99273a8fdb19f5912ca38ba46d6bd02071363d/code/system-contracts/contracts/SystemContext.sol#L438) to verify the correctness of the batch's timestamps and hashes. You can read more about block processing on [Batches and L2 blocks on ZKsync](/build/developer-reference/batches-and-l2-blocks).