diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx
index eca60a93a..f103c9355 100644
--- a/docs/base-chain/specs/upgrades/beryl/b20.mdx
+++ b/docs/base-chain/specs/upgrades/beryl/b20.mdx
@@ -7,9 +7,9 @@ B20 is the Base ecosystem's own version of [ERC-20](https://eips.ethereum.org/EI
 
 To deploy your first B20 token, see the [Launch a B20 Token](/get-started/launch-b20-token) quickstart.
 
-<Warning>
-[Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy.
-</Warning>
+<Note>
+The B20 Activation Registry is enabled on mainnet. [Verify activation status](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before deploying to other networks.
+</Note>
 
 B20 supports two variants:
 
diff --git a/docs/get-started/launch-b20-token.mdx b/docs/get-started/launch-b20-token.mdx
index c0f61578a..fad7bb49b 100644
--- a/docs/get-started/launch-b20-token.mdx
+++ b/docs/get-started/launch-b20-token.mdx
@@ -24,9 +24,9 @@ You need **Base's Foundry build** (`base-forge`, `base-cast`, [`base-anvil`](htt
 
 ## Verify the Activation Registry is enabled
 
-<Warning>
-Attempting to deploy before the Activation Registry is enabled will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding:
-</Warning>
+<Note>
+The B20 Activation Registry is enabled on mainnet. Run the check below to confirm the variant you plan to deploy returns `true` before proceeding:
+</Note>
 
 ```bash Terminal theme={null}
 REG=0x8453000000000000000000000000000000000001  # Activation Registry precompile