Standardize practical guides and correct staking guidance

[HDauven]

Summary

• give the migration, BSC bridge, DuskEVM bridge, and staking guides a concise shared structure: at-a-glance facts, prerequisites, exact steps, verification, and recovery guidance
• clarify that ERC20/BEP20 migration requires approval and execution, document LUX rounding, and make the BSC bridge fee, minimum useful amount, and memo risk explicit
• align the DuskEVM testnet bridge guide with the current three-action withdrawal flow and the status labels introduced by Migrate DuskEVM bridge to current contracts and SDK web-wallet#947
• correct staking documentation across user and operator pages: activation varies between roughly one and two epochs, active-stake top-ups use the 90/10 split, and hard consensus penalties can burn stake
• replace remaining "native DUSK" labels with explicit Dusk mainnet terminology

Why

The practical guides had accumulated repeated prose while still leaving important transaction boundaries and failure cases implicit. Some staking pages also described activation as a fixed 4,320-block delay and slashing as soft-only, neither of which matches the current protocol implementation.

The revised pages optimize for a user completing or verifying a task while preserving the distinctions that affect funds and operator risk.

Validation

Claims were cross-checked against the current dusk-migration contract, Web Wallet migration and bridge implementations, bridge-replayer, Rusk, and the pinned Rusk contracts revision.

• npm run build (59 pages; all internal links valid)
• git diff --check
• repository-wide stale-claim scan for the replaced activation, slashing, migration-title, and "native DUSK" wording
• desktop and 390 px Chromium visual checks of all four primary guides

Notes

The DuskEVM guide describes the interface being prepared in dusk-network/web-wallet#947, so that guide should ship with or after the corresponding Web Wallet change.