Fix Typographical and Inconsistency Errors in Documentation (#1792)

* Typo Update docker-images.md The phrase "the your" corrected to "your". * Typo Update ethereum-fallback.md The word "fallback" is used inconsistently. In some places, it is written as "fallback" and in others as "fall back" (two words). Fixed. * Typo Update network-upgrade-process.md Corrected has signaled to have signaled
celestiaorg · Nov 18, 2024 · 7e3f620 · 7e3f620
1 parent 4b55bf3
commit 7e3f620
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/how-to-guides/docker-images.md b/how-to-guides/docker-images.md
@@ -256,7 +256,7 @@ Congratulations! You now have a node running with persistent storage.
 
 ## Troubleshooting
 
-For security purposes Celestia expects to interact with the your node's
+For security purposes Celestia expects to interact with your node's
 keys in a read-only manner. This is enforced using linux style permissions
 on the filesystem. Windows NTFS does not support these types of permissions.
 As a result the recommended path for Windows users to mount a persisted

diff --git a/how-to-guides/ethereum-fallback.md b/how-to-guides/ethereum-fallback.md
@@ -11,7 +11,7 @@ prev:
 # Ethereum fallback
 
 Ethereum fallback is a mechanism
-that enables Ethereum L2s (or L3s) to “fall back” to using Ethereum
+that enables Ethereum L2s (or L3s) to “fallback” to using Ethereum
 calldata for data availability in the event of downtime on Celestia
 Mainnet Beta. This feature is currently supported by Celestia integrations
 with:

diff --git a/how-to-guides/network-upgrade-process.md b/how-to-guides/network-upgrade-process.md
@@ -13,7 +13,7 @@ As of the Lemongrass upgrade in September 2024, Celestia has implemented [CIP-10
 1. **Pre-programmed height**: Used for the Lemongrass network upgrade (v2)
 2. **In-protocol signaling**: Used for all subsequent upgrades (v3+)
 
-Under the in-protocol signaling mechanism, validators submit messages to signal their readiness and preference for the next version. The upgrade activates automatically once a quorum of 5/6 of validators has signaled for the same version.
+Under the in-protocol signaling mechanism, validators submit messages to signal their readiness and preference for the next version. The upgrade activates automatically once a quorum of 5/6 of validators have signaled for the same version.
 
 ## Upgrade process