From 1dc640364469f262a5c4c35599af9fc352f23c8a Mon Sep 17 00:00:00 2001
From: Skylar Ray <137945430+sky-coderay@users.noreply.github.com>
Date: Wed, 27 Nov 2024 19:20:31 +0200
Subject: [PATCH] Update STATE-COMPATIBILITY.md

---
 STATE-COMPATIBILITY.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/STATE-COMPATIBILITY.md b/STATE-COMPATIBILITY.md
index a68d813be2..2092ec4cde 100644
--- a/STATE-COMPATIBILITY.md
+++ b/STATE-COMPATIBILITY.md
@@ -55,7 +55,7 @@ To avoid these problems, let's now examine how these hashes work.
 
 **Note:** The following explanation is simplified for clarity.
 
-An app hash is a hash of hashes of every store's Merkle root that is returned by ABCI's `Commit()` from Cosmos-SDK to CometBFT.
+An app hash is a hash of hashes of every store's Merkel root that is returned by ABCI's `Commit()` from Cosmos-SDK to CometBFT.
 Cosmos-SDK [takes an app hash of the application state](https://github.com/cosmos/cosmos-sdk/blob/v0.47.6/store/rootmulti/store.go#L468), and propagates it to CometBFT which, in turn, compares it to the app hash of the rest of the network.
 Then, CometBFT ensures that the app hash of the local node matches the app hash of the network. 
 
@@ -209,4 +209,4 @@ to predict when the multi-threaded state can be updated.
 
 ### Hardware Errors
 
-This is out of the developer's control but is mentioned for completeness.
\ No newline at end of file
+This is out of the developer's control but is mentioned for completeness.