diff --git a/pages/stack/interop/tools/devnet.mdx b/pages/stack/interop/tools/devnet.mdx index c82960893..ef9da26ce 100644 --- a/pages/stack/interop/tools/devnet.mdx +++ b/pages/stack/interop/tools/devnet.mdx @@ -9,7 +9,7 @@ import { Callout, Tabs, Steps } from 'nextra/components' # Interop devnet (coming soon) - 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. {/* diff --git a/pages/stack/public-devnets.mdx b/pages/stack/public-devnets.mdx index e1e6847e1..5e2cc8733 100644 --- a/pages/stack/public-devnets.mdx +++ b/pages/stack/public-devnets.mdx @@ -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.