Fix lint in browser hardening guide

Author: DicksonWu654

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

@@ -32,6 +32,7 @@ tight, and make origin-checking part of the operating procedure before you conne
 
 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
@@ -116,8 +117,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.
@@ -130,6 +129,7 @@ Team members should:
 - 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
@@ -159,6 +159,7 @@ other privileged users.
 - Keep exception handling narrow and explicit; do not let a "temporary" site permission or extension become permanent
 - If a team depends on a small set of critical dapps, internal guidance should define the approved domains and expected
   connect/sign flow for each one
+
 ## Web3-Specific Operational Rules
 
 Browser hardening matters in Web3 because the browser is often the access path to a wallet, not just a place to read
@@ -174,6 +175,7 @@ Use these operating rules consistently:
 6. Do not store seed phrases or private keys in browser-based secret storage.
 7. Treat "urgent" dapp prompts, fake support chats, and recovery requests as likely phishing attempts.
 8. If a prompt is confusing, stop and verify with another team member before signing.
+
 ## Related Guides
 
 - [GitHub Security](/guides/account-management/github)
@@ -187,5 +189,6 @@ Use these operating rules consistently:
 - [W3C WebAuthn Level 3](https://www.w3.org/TR/webauthn-3/)
 - [NCSC: Managing Web Browser Security](https://www.ncsc.gov.uk/collection/device-security-guidance/policies-and-settings/managing-web-browser-security)
 - [MetaMask: What Is a Secret Recovery Phrase, and How to Secure Your Wallet](https://support.metamask.io/start/what-is-a-secret-recovery-phrase-and-how-to-keep-your-crypto-wallet-secure/)
+
 </TagProvider>
 <ContributeFooter />

wordlist.txt

@@ -337,3 +337,4 @@ rootfs
 GitHub
 GitLab
 GoDaddy
+NCSC