From 12630bfeff056519dbf3193c0832f1d1f41526f1 Mon Sep 17 00:00:00 2001
From: Skylar Ray <137945430+sky-coderay@users.noreply.github.com>
Date: Mon, 25 Nov 2024 23:20:49 +0200
Subject: [PATCH] Update withdrawals.md (#304)

---
 docs/docs/learn/withdrawals.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/learn/withdrawals.md b/docs/docs/learn/withdrawals.md
index 7b12670e..689911e4 100644
--- a/docs/docs/learn/withdrawals.md
+++ b/docs/docs/learn/withdrawals.md
@@ -38,6 +38,6 @@ For each observed event, the builder makes a corresponding `L2ToL1MessagePasserE
 
 The next step for a user is to obtain a proof of the withdrawal transaction.
 
-For compatability with the withdrawals process, Monomer uses the state root of its EVM sidecar state as the L2 state updated by the `op-proposer`. Monomer exposes the standard ethereum `GetProof` API endpoint for obtaining a merkle proof of withdrawal transactions registered in the EVM sidecar state.
+For compatibility with the withdrawals process, Monomer uses the state root of its EVM sidecar state as the L2 state updated by the `op-proposer`. Monomer exposes the standard ethereum `GetProof` API endpoint for obtaining a merkle proof of withdrawal transactions registered in the EVM sidecar state.
 
 With the withdrawal proof data, the user is now back to the L1 side of the OP Stack. The proof is submitted, and the withdrawal can be finalized after the rollup's challenge period.