From 789c2682bcb70751eb88ef85da159d01422dc6a2 Mon Sep 17 00:00:00 2001
From: leopardracer <136604165+leopardracer@users.noreply.github.com>
Date: Fri, 18 Apr 2025 10:21:00 +0300
Subject: [PATCH] Update updating-keystore.mdx

---
 docs/pages/updating-keystore.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/pages/updating-keystore.mdx b/docs/pages/updating-keystore.mdx
index 9f00fd5..3701ea1 100644
--- a/docs/pages/updating-keystore.mdx
+++ b/docs/pages/updating-keystore.mdx
@@ -71,7 +71,7 @@ Once we have the state root for the master chain, we just need to prove storage
 
 ### Syncing via Deposits and Withdrawals
 
-Deposits and withdrawals are the canonical method for sending messages between chains. That makes them extemely resilient: the whole ecosystem builds on top of withdrawals and deposits with the expectaction that they will succeed for the lifetime of the chains. Rollup teams ensure that their bridge contracts continue to function through each hard fork.
+Deposits and withdrawals are the canonical method for sending messages between chains. That makes them extremely resilient: the whole ecosystem builds on top of withdrawals and deposits with the expectaction that they will succeed for the lifetime of the chains. Rollup teams ensure that their bridge contracts continue to function through each hard fork.
 
 The downsides of deposits and withdrawals are that they require a transaction to be sent on a separate chain from the one the user is interacting with, and that these transactions have significant costs on L1.