docs(wallet-security): normalize structure and wording

docs/pages/wallet-security/account-abstraction.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Account Abstraction Wallets | Security Alliance"
-description: "ERC-4337 Account Abstraction wallets: social recovery, gas sponsorship, batch transactions, and customizable security policies. Eliminate single points of failure like seed phrase loss."
+description: "ERC-4337 Account Abstraction wallets: social recovery, gas sponsorship, batch transactions, and customizable security policies"
 tags:
   - Engineer/Developer
   - Security Specialist
@@ -10,6 +10,8 @@ contributors:
     users: [pinalikefruit]
   - role: reviewed
     users: [Coinspect]
+  - role: fact-checked
+    users: []
 ---
 
 import { TagList, AttributionList, ContributeFooter } from '../../../components'
@@ -19,6 +21,9 @@ import { TagList, AttributionList, ContributeFooter } from '../../../components'
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
+> 🔑 **Key Takeaway**: Account abstraction adds programmable controls and recovery options—and new attack surfaces.
+> Threat-model guardians, modules, and session keys before relying on them.
+
 ## User Profile
 
 Advanced users, developers, and organizations interested in programmable security, customizable transaction rules, and
@@ -85,6 +90,15 @@ new one without having to move all assets to a new wallet address.
 recovery action. This method allows guardians to produce a valid signature through a distributed computation using their
 individual shares, without ever reconstructing a single master key on any device.
 
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [Using EIP-7702](/wallet-security/signing-and-verification/verifying-7702): the delegation path that brings this to
+  existing EOAs
+- [Secure Multisig Best Practices](/wallet-security/secure-multisig-best-practices): the established alternative to
+  guardian-based recovery
+- [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337): the specification behind UserOperations and bundlers
+
 ---
 
 <ContributeFooter />

docs/pages/wallet-security/cold-vs-hot-wallet.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Cold Vs Hot Wallet | Security Alliance"
-description: "Compare cold vs hot wallets: security trade-offs, use cases, and risk profiles. Hardware wallets, paper wallets, and air-gapped devices vs browser extensions and mobile wallets."
+description: "Compare cold vs hot wallets: security trade-offs, use cases, and risk profiles. Hardware wallets, paper wallets. The primary distinction between wallet"
 tags:
   - Engineer/Developer
   - Security Specialist
@@ -10,6 +10,8 @@ contributors:
     users: [pinalikefruit]
   - role: reviewed
     users: [Coinspect, patrickalphac]
+  - role: fact-checked
+    users: []
 ---
 
 import { TagList, AttributionList, ContributeFooter } from '../../../components'
@@ -19,6 +21,9 @@ import { TagList, AttributionList, ContributeFooter } from '../../../components'
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
+> 🔑 **Key Takeaway**: Hot wallets maximize convenience and online exposure; cold wallets reduce remote attack surface
+> at the cost of operational friction. Match fund tier to exposure.
+
 The primary distinction between wallet types is their connectivity to the internet. This factor dictates their security
 threat model, risk profile, and ideal use cases.
 
@@ -91,6 +96,15 @@ Regardless of the type, non-custodial wallets place the full burden of security
 - **Supply Chain Attacks**: Be cautious of both software and hardware integrity. Always download wallet software from
 official sources and purchase hardware wallets directly from the manufacturer to avoid receiving a tampered device.
 
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [For Beginners & Small Balances](/wallet-security/for-beginners-and-small-balances): a hot-wallet-first setup done
+  safely
+- [For Intermediates & Medium Balances](/wallet-security/intermediates-and-medium-funds): adding cold storage as
+  balances grow
+- [Seed Phrase Management](/wallet-security/seed-phrase-management): the backup practices both wallet types depend on
+
 ---
 
 <ContributeFooter />

docs/pages/wallet-security/custodial-vs-non-custodial.mdx

@@ -10,6 +10,8 @@ contributors:
     users: [pinalikefruit]
   - role: reviewed
     users: [Coinspect]
+  - role: fact-checked
+    users: []
 ---
 
 import { TagList, AttributionList, ContributeFooter } from '../../../components'
@@ -19,6 +21,9 @@ import { TagList, AttributionList, ContributeFooter } from '../../../components'
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
+> 🔑 **Key Takeaway**: Custody is who holds the private keys. Custodial services trade self-sovereignty for recovery
+> convenience and counterparty risk; non-custodial flips that tradeoff.
+
 The distinction between custodial and non-custodial wallets centers on who controls the private keys. This control
 directly impacts ownership, security responsibility, and the ability to interact with the web3 ecosystem.
 
@@ -75,6 +80,13 @@ to undertake the responsibility of self-custody.
 | **Primary Risk**            | Counterparty Risk, Centralization          | User Error, Loss of Keys                    |
 | **Use Case**                | New Users, Trading on CEX, Convenience     | Full Control, dApp Use, Long-Term Storage   |
 
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [Cold vs. Hot Wallets](/wallet-security/cold-vs-hot-wallet): the other axis to decide alongside custody
+- [Seed Phrase Management](/wallet-security/seed-phrase-management): the responsibility that comes with self-custody
+- [Account Abstraction Wallets](/wallet-security/account-abstraction): recovery options without handing over the keys
+
 ---
 
 <ContributeFooter />

docs/pages/wallet-security/encumbered-wallets.mdx

@@ -1,6 +1,6 @@
 ---
 title: "TEE-based Encumbered Wallets | Security Alliance"
-description: "TEE-based encumbered wallets: implement cross-chain security policies using Trusted Execution Environments. Fine-grained permissions, time-bounded access, and compliance features for any blockchain."
+description: "TEE-based encumbered wallets: implement cross-chain security policies using Trusted Execution Environments. Fine-grained permissions, time-bounded access"
 tags:
   - Engineer/Developer
   - Security Specialist
@@ -10,7 +10,8 @@ contributors:
     users: [njelich]
   - role: reviewed
     users: [pinalikefruit]
-
+  - role: fact-checked
+    users: []
 ---
 
 import { TagList, AttributionList, ContributeFooter } from '../../../components'
@@ -20,6 +21,9 @@ import { TagList, AttributionList, ContributeFooter } from '../../../components'
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
+> 🔑 **Key Takeaway**: TEE and encumbrance-based wallets shift trust into hardware and policy constraints. Validate the
+> threat model and failure modes; they are not automatic trustlessness.
+
 ## User Profile
 
 Advanced users, developers, and organizations wanting to implement fine-grained security policies, that don't want to
@@ -168,6 +172,15 @@ solutions, as even root or physical access to the host system cannot compromise
 * Aublin, P.-L., Mahhouk, M., & Kapitza, R. (n.d.). Towards TEEs with Large Secure Memory and Integrity Protection
   Against HW Attacks [IIJ Innovation Institute, TU Braunschweig](https://www.ibr.cs.tu-bs.de/bib/xml/aublin2022scalableSGX.html)
 
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [Account Abstraction Wallets](/wallet-security/account-abstraction): the on-chain route to programmable policy
+- [Custodial vs. Non-Custodial Wallets](/wallet-security/custodial-vs-non-custodial): the trust model TEE custody sits
+  between
+- [Secure Multisig Best Practices](/wallet-security/secure-multisig-best-practices): distributing trust across signers
+  instead of hardware
+
 ---
 
 <ContributeFooter />

docs/pages/wallet-security/for-beginners-and-small-balances.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Wallets for Beginners & Small Balances | SEAL"
-description: "Hot wallet setup guide for beginners with small balances. Select browser extension, mobile, or desktop wallets. Evaluate open-source code and use Wallet Scrutiny for security assessment."
+description: "Hot wallet setup guide for beginners with small balances. Select browser extension, mobile, or desktop wallets. A user with foundational web3 knowledge"
 tags:
   - Engineer/Developer
   - Security Specialist
@@ -9,6 +9,8 @@ contributors:
     users: [pinalikefruit]
   - role: reviewed
     users: [Coinspect]
+  - role: fact-checked
+    users: []
 ---
 
 import { TagList, AttributionList, ContributeFooter } from '../../../components'
@@ -18,6 +20,9 @@ import { TagList, AttributionList, ContributeFooter } from '../../../components'
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
+> 🔑 **Key Takeaway**: Small balances still need unique secrets and phishing resistance. Start simple, but keep habits
+> that scale: unique seeds, careful signing, offline backups.
+
 ## User Profile
 
 A user with foundational web3 knowledge who is actively learning and interacting with dApps. The asset value is
@@ -60,6 +65,15 @@ on specific criteria such as transaction clarity, protection against known threa
 Using these tools can provide valuable data points to help you assess a wallet's security posture and make an informed
 decision.
 
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [Seed Phrase Management](/wallet-security/seed-phrase-management): the one habit worth getting right from day one
+- [Smart Contract Interaction Security](/wallet-security/smart-contract-interaction-security): approvals and signing
+  mistakes that cost beginners funds
+- [For Intermediates & Medium Balances](/wallet-security/intermediates-and-medium-funds): what to add as your balance
+  grows
+
 ---
 
 <ContributeFooter />

docs/pages/wallet-security/hardware-wallets.mdx

@@ -1 +1,37 @@
+---
+title: "Hardware Wallets | SEAL"
+description: "Stub page for hardware wallets under Wallet Security. Expand with practical custody and verification guidance. Placeholder page pending expert expansion of controls an..."
+tags:
+  - Engineer/Developer
+  - Security Specialist
+contributors:
+  - role: wrote
+    users: []
+  - role: reviewed
+    users: []
+  - role: fact-checked
+    users: []
+---
+
+import { TagList, AttributionList, ContributeFooter } from '../../../components'
+
 # Hardware Wallets
+
+<TagList tags={frontmatter.tags} />
+<AttributionList contributors={frontmatter.contributors} />
+
+> 🔑 **Key Takeaway**: This page is a placeholder until filled with dedicated guidance.
+
+Stub/in progress. Help contribute or expand this page. See the [Wallet Security overview](/wallet-security/overview)
+and related cold/hot, seed phrase, and signing pages for production guidance.
+
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [For Intermediates & Medium Balances](/wallet-security/intermediates-and-medium-funds): hardware wallet selection and
+  initial setup in practice
+- [Seed Phrase Management](/wallet-security/seed-phrase-management): protecting the backup the device generates
+
+---
+
+<ContributeFooter />

docs/pages/wallet-security/intermediates-and-medium-funds.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Wallets for Intermediates & Medium Funds | SEAL"
-description: "Hardware wallet guide for intermediate users with medium balances. Select devices with secure elements, verify supply chain integrity, configure PINs, and maintain backup devices."
+description: "Hardware wallet guide for intermediate users with medium balances. Select devices with secure elements, verify supply chain integrity, configure PINs"
 tags:
   - Engineer/Developer
   - Security Specialist
@@ -9,6 +9,8 @@ contributors:
     users: [pinalikefruit, isaac, geoffrey, louis, pablo, dickson, auditware]
   - role: reviewed
     users: [Coinspect, engn33r]
+  - role: fact-checked
+    users: []
 ---
 
 import { TagList, AttributionList, ContributeFooter } from '../../../components'
@@ -18,6 +20,9 @@ import { TagList, AttributionList, ContributeFooter } from '../../../components'
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
+> 🔑 **Key Takeaway**: As balances grow, add hardware isolation, better backup design, and stricter signing habits—do
+> not keep intermediate funds on the same hot path as everyday spending wallets.
+
 ## User Profile
 
 An intermediate user who is comfortable with web3 interactions and is now managing a significant, but not life-altering,
@@ -115,6 +120,15 @@ Maintain a backup hardware wallet to avoid needing to access your seed phrase if
 * Store backup securely
 * Monthly verification that backup device functions correctly
 
+## Further Reading
+
+- [Wallet Security overview](/wallet-security/overview): how the pages of this framework fit together
+- [Seed Phrase Management](/wallet-security/seed-phrase-management): backup design for the devices set up here
+- [Signing & Verification](/wallet-security/signing-and-verification/signing-verification): the stricter signing habits
+  this tier requires
+- [Secure Multisig Best Practices](/wallet-security/secure-multisig-best-practices): the next step once a single signer
+  is too much risk
+
 ---
 
 <ContributeFooter />