Skip to content

spelling issues #1284

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

Merged
merged 2 commits into from
Jan 24, 2025
Merged

spelling issues #1284

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
42e5649
Update public-devnets.mdx
reject-i Jan 24, 2025
59d4d43
Update devnet.mdx
reject-i Jan 24, 2025
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 pages/stack/interop/tools/devnet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ import { Callout, Tabs, Steps } from 'nextra/components'
# Interop devnet (coming soon)

<Callout>
Interop devnet is currently in active development and may experience periods of instability, including potential outages, as the networks is regularly updated and improved. Developers should expect some level of unreliability when interacting with the devnet. The devnet is intended for testing and development purposes only, and should not be relied upon for mission-critical applications.
Interop devnet is currently in active development and may experience periods of instability, including potential outages, as the networks are regularly updated and improved. Developers should expect some level of unreliability when interacting with the devnet. The devnet is intended for testing and development purposes only, and should not be relied upon for mission-critical applications.
</Callout>

{/*
Expand Down
2 changes: 1 addition & 1 deletion pages/stack/public-devnets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Features must be included on an alphanet before they can be deployed on a betane

Alphanets decouple feature development and testing from hardfork scheduling, allowing teams to test and iterate on features well in advance of their release on mainnet.

They're designed to stay fresh: Each one is deployed monthly and replaced, so they won't be useable as long-term networks.
They're designed to stay fresh: Each one is deployed monthly and replaced, so they won't be usable as long-term networks.
Each alphanet is launched from genesis, meaning that new features are encoded in genesis rather than undergoing a network upgrade from a preexisting version.
The alphanet is then tested, with an emphasis on acceptance testing for new features followed by fault injection testing and performance / load testing.
After five weeks, the alphanet is spun down and a new alphanet takes its place, with whatever new features have been developed in that time.
Expand Down