Tighten browser hardening guide

Author: DicksonWu654

docs/pages/guides/endpoint-security/web-browser-hardening.mdx

@@ -30,9 +30,6 @@ For most Web3 teams, browser hardening is less about obscure settings and more a
 practical baseline is to separate wallet activity from normal browsing, minimize extension risk, keep site permissions
 tight, and make origin-checking part of the operating procedure before you connect a wallet or approve a request.
 
-This page focuses on desktop browser use for Web3 work. It complements endpoint hardening, account security, and wallet
-security, but it does not replace them.
-
 ## For Individuals
 
 These steps apply to anyone using a browser to access dapps, exchanges, admin consoles, registrars, dashboards, or
@@ -117,19 +114,6 @@ Focus on the settings that meaningfully reduce attack surface:
 - **Authentication:** use passkeys or hardware security keys for email, SSO, source control, cloud, and other accounts
   that can be used to pivot into Web3 operations
 
-## For Team Members
-
-These guidelines apply to staff working in a shared organizational environment.
-
-Team members should:
-
-- Follow the approved browser and profile model for wallet work instead of improvising per person
-- Keep personal browsing, work browsing, and wallet operations separate
-- Report unexpected wallet prompts, extension changes, browser warnings, or redirected login flows
-- Avoid syncing privileged profiles to unmanaged devices without explicit approval
-- Keep browser protections enabled and do not bypass warnings just to complete a task faster
-- Escalate suspicious domains, signing prompts, or new dapps before using them with a work wallet
-
 ## For Admins
 
 These settings and practices apply to administrators managing browsers for engineers, operators, finance, treasury, or