docs: remove stale timing language from B20 activation callouts

Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

Author: roethke

docs/base-chain/specs/upgrades/beryl/b20.mdx

@@ -8,7 +8,7 @@ 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>
-B20 activation on mainnet has been delayed — a revised date will be announced shortly. The Activation Registry can take up to ~1 hour to be fully enabled. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy.
+B20 activation on mainnet has been delayed — a revised date will be announced shortly. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy.
 </Warning>
 
 B20 supports two variants:

docs/get-started/launch-b20-token.mdx

@@ -25,7 +25,7 @@ You need **Base's Foundry build** (`base-forge`, `base-cast`, [`base-anvil`](htt
 ## Verify the Activation Registry is enabled
 
 <Warning>
-**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet has been delayed — a revised date will be announced shortly. After activation, the Activation Registry can take up to ~1 hour to be fully enabled. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding:
+**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet has been delayed — a revised date will be announced shortly. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding:
 </Warning>
 
 ```bash Terminal theme={null}