fix: typo duplicated word (#243)

Remove duplicate word

<!--

Thank you for contributing to the ZKsync Docs!

Before submitting the PR, please make sure you do the following:

- Update your PR title to follow [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/)
- Read the [Contributing
Guide](https://github.com/matter-labs/zksync-docs/blob/main/CONTRIBUTING.md).
- Understand our [Code of
Conduct](https://github.com/matter-labs/zksync-docs/blob/main/CODE_OF_CONDUCT.md)
- Please delete any unused parts of the template when submitting your PR

-->

# Description

<!-- Please describe what are the changes and what they are solving for
in this PR. -->

## Linked Issues

<!-- If you have any issues this PR is related to, link them here. -->
<!--
Check out
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
on how to automate linking a GitHub Issue to a PR.
-->

## Additional context

Co-authored-by: Antonio <[email protected]>

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).