Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Typographical and Inconsistency Errors in Documentation #1792

Merged
merged 3 commits into from
Nov 18, 2024
Merged

Fix Typographical and Inconsistency Errors in Documentation #1792

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b6942dc
Typo Update docker-images.md
voronor Nov 14, 2024
43f9aef
Typo Update ethereum-fallback.md
voronor Nov 14, 2024
7faef48
Typo Update network-upgrade-process.md
voronor Nov 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion how-to-guides/docker-images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion how-to-guides/ethereum-fallback.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion how-to-guides/network-upgrade-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading