diff --git a/.github/ISSUE_TEMPLATE/content-request.yml b/.github/ISSUE_TEMPLATE/content-request.yml
index 4ecf9602..7437f35b 100644
--- a/.github/ISSUE_TEMPLATE/content-request.yml
+++ b/.github/ISSUE_TEMPLATE/content-request.yml
@@ -32,7 +32,7 @@ body:
     id: suggested_content
     attributes:
       label: "What content are you suggesting for?"
-      description: "Be as specific as possible (e.g., new framework about X, new page on Y framework, update section Z in [framework] to include, etc.)"
+      description: "Be as specific as possible (e.g., new framework about X, a new page in framework Y, or an update to section Z in [framework])."
       placeholder: "Describe what new or updated content you are requesting."
     validations:
       required: true
@@ -40,7 +40,7 @@ body:
   - type: textarea
     id: why_needed
     attributes:
-      label: "Why do you think this update or modification is needed"
+      label: "Why do you think this update or modification is needed?"
       description: "If it is not self-explanatory, or relatively clear, add a few sentences explaining why it is needed."
       placeholder: "Add reasoning or context here."
     validations:
diff --git a/.github/ISSUE_TEMPLATE/non-content-request.yml b/.github/ISSUE_TEMPLATE/non-content-request.yml
index 93a3b05f..981246ef 100644
--- a/.github/ISSUE_TEMPLATE/non-content-request.yml
+++ b/.github/ISSUE_TEMPLATE/non-content-request.yml
@@ -1,5 +1,5 @@
 name: Non Content Request
-description: Strategy, tech, or other non-content related issues and ideas.
+description: Strategy, tech, or other non-content-related issues and ideas.
 body:
   - type: markdown
     attributes:
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 93802ea8..07e5fe88 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -5,9 +5,9 @@ Thank you for contributing to the Security Frameworks! Before you open a PR, mak
 - [ ] Describe your changes, substitute this text with the information
 - [ ] If you are touching an existing piece of content, tag current contributors from the attribution list
 - [ ] If there is a steward for that framework, ask the steward to review it
-- [ ] If you're modifying the general outline, make sure to update it in the `vocs.config.tsx` adding the `dev: true` parameter
+- [ ] If you're modifying the general outline, make sure to update it in the `vocs.config.ts` adding the `dev: true` parameter
 - [ ] If you need feedback for your content from the wider community, share the PR in our Discord
-- [ ] Review changes to ensure there are no typos, see instructions below
+- [ ] Review changes to ensure there are no typos; see instructions below.
 
 <!--
 ℹ️ Checking for typos locally
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index c4e4982d..549e87bb 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -125,7 +125,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 069c1f51..ba9b7127 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -43,7 +43,7 @@ approved, they will be merged into the **main branch** for publication on the st
 ## Ways to contribute
 
 There are several ways to contribute, depending on your preference and the scope of your changes.
-First, check existing PRs or branches to make sure your work has not been previously ****submitted**.**
+First, check existing PRs or branches to make sure your work has not been previously submitted.
 
 ### 1. Quick edits
 
@@ -64,7 +64,7 @@ deployment through the automated preview and make any final adjustments.
 5. **Notify reviewers** by tagging a steward or maintainer, requesting reviews directly in your PR.
 6. Additionally, you can paste your PR and/or potential associated issues to the `framework-contribs` Discord channel.
 7. Once reviewed and approved, your changes will be merged into `develop`.
-8. Don't forget to add yourself to the YAML header of the file you're modifying, given that is the way we provide
+8. Don't forget to add yourself to the YAML header of the file you're modifying, since that is how we provide
 attribution. You should also create your profile inside the contributors list, at `docs/config/contributors.json`.
 9. Periodically, reviewed content from `develop` is merged into `main` for the stable site.
 
@@ -91,7 +91,7 @@ The easiest way to get started is using our pre-configured devcontainer with VSC
 ### Option B: DevContainer CLI Only (No VSCode Required)
 
 Since you won't require extensions for the initiative to work, you can just create a devcontainer using the CLI and
-access it through whatever mean you think suits you best.
+access it through whatever means you think suits you best.
 
 **Using DevContainer CLI (Recommended):**
 
@@ -268,7 +268,7 @@ This helps track contributions and ensures proper attribution.
 
 For a complete frontmatter example, see the [template file](/docs/pages/config/template.mdx).
 
-### 3. Sidebar / Navigation
+### 2. Sidebar / Navigation
 
 Because of how we handle the `.org` and `.dev` domains in different branches, when contributing **new pages** you must
 also **update `vocs.config.tsx`** so that the page appears in the site’s sidebar. For content still in review, remember
@@ -373,8 +373,8 @@ Pages with minimal content which need more work to cover the topic need to inclu
 
 ## Anything else?
 
-This page is also open for contributions! Suggest improvements to our style and guidelines in the github repo.
+This page is also open for contributions! Suggest improvements to our style and guidelines in the GitHub repo.
 
 ## About this page
 
-Originally inspired by the [Ethereum Protocol Fellows](https://github.com/eth-protocol-fellows/protocol-studies)
+Originally inspired by the [Ethereum Protocol Fellows](https://github.com/eth-protocol-fellows/protocol-studies).
diff --git a/README.md b/README.md
index c47f4457..255540ab 100644
--- a/README.md
+++ b/README.md
@@ -71,7 +71,7 @@ Both versions are continuously updated, but only `main` reflects finalized, comm
 
 ## Contributing
 
-The Security Framework is an open and collaborative initiative. Whether you are part of the Security Alliance or not,
+The Security Frameworks are an open and collaborative initiative. Whether you are part of the Security Alliance or not,
 we welcome your contributions! Help us build the documentation and improve security in the ecosystem. If you'd like
 to join our effort, feel free to fix typos, contribute new sections, or propose enhancements.
 
diff --git a/components/shared/tagColors.ts b/components/shared/tagColors.ts
index d94b5126..7e6b2c67 100644
--- a/components/shared/tagColors.ts
+++ b/components/shared/tagColors.ts
@@ -8,7 +8,7 @@ export const TAG_COLORS: Record<string, string> = {
   'Community & Marketing': '#5B2371', 
   'HR': '#285AD2',                  
   'Engineer/Developer': '#B2439F',  
-  'Devops': '#5C234A',                 
+  'DevOps': '#5C234A',
   'SRE': '#2E51BA',                    
   'SEAL/Initiative': '#4339db',
   'Cloud': '#0873B5',
@@ -26,6 +26,7 @@ export const TAG_COLORS: Record<string, string> = {
   'Business Tools': '#3ebbc9',
   'Communication Platforms': '#bf9504',
   'DevOps Accounts': '#f43e7c',
+  'Devops': '#c094e6',
 }
 
 /**
@@ -44,4 +45,4 @@ export function getTagColor(tag: string): string {
  */
 export function getTagId(tag: string): string {
   return tag.toLowerCase().replace(/[^a-z0-9]/g, '-')
-}
\ No newline at end of file
+}
diff --git a/docs/pages/certs/contributions.mdx b/docs/pages/certs/contributions.mdx
index 232ddc2e..a24d8f9a 100644
--- a/docs/pages/certs/contributions.mdx
+++ b/docs/pages/certs/contributions.mdx
@@ -21,7 +21,7 @@ due to the nature of Certifications, contributions are subject to more stringent
 by Isaac, the initiative lead, and the other Certifications maintainers.
 
 - If you have suggestions for improving existing Certifications, or ideas for a new Certification, please open an issue
-  in the frameworks repo with the `certifications` tag. We're welcome to feedback and ideas from the community!
+  in the frameworks repo with the `certifications` tag. We welcome feedback and ideas from the community!
 - If you're a protocol interested in having your project certified, you can reach out to us through our [protocol
   interest form](https://securityalliance.typeform.com/CertsWaitlist).
 - If you're a security firm interested in becoming a SEAL-approved auditor, please reach out through our [interest form](https://securityalliance.typeform.com/CertsAuditor).
diff --git a/docs/pages/certs/overview.mdx b/docs/pages/certs/overview.mdx
index 50059948..36851592 100644
--- a/docs/pages/certs/overview.mdx
+++ b/docs/pages/certs/overview.mdx
@@ -18,18 +18,18 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter, Exp
 
 SEAL Certifications is a certification framework developed by SEAL to provide standardized guidelines and evaluation
 criteria for assessing the security of DeFi protocols. SEAL Certifications provides targeted modular certifications
-(e.g., [Incident Response](/certs/sfc-incident-response.mdx), [Treasury Ops](/certs/sfc-treasury-ops.mdx)) that can
+(e.g., [Incident Response](/certs/sfc-incident-response), [Treasury Ops](/certs/sfc-treasury-ops)) that can
 independently validate specific aspects of a protocol's security posture.
 
 Using SEAL Certifications will help ensure that protocols follow best practices for their security operations, and
-provides a standard set of criteria for comparing the security of different protocols.
+provide a standard set of criteria for comparing the security of different protocols.
 
 SEAL Certifications is fully open-source and freely available for any protocol to use.
 
 ## How it Works
 
-Unlike broad certifications like SOC 2 or ISO 27001, SEAL Certifications focus on specific areas based on the highest
-impact needs of protocols, based on what SEAL has observed throughout the industry and in interviews with pilot
+Unlike broad certifications like SOC 2 or ISO 27001, SEAL Certifications focus on the highest-impact needs of
+protocols, based on what SEAL has observed throughout the industry and in interviews with pilot
 protocols. Each certification focuses on a specific area of security and includes controls relevant to that area.
 Protocols can use certifications independently to evaluate their security posture through self-assessment, or they can
 pursue formal certification through a third-party audit by a SEAL-partnered auditor. After completing a certification
@@ -93,7 +93,7 @@ framework. Upon successful completion of a certified audit, protocols receive a
 Attestations are certificates issued on-chain through the [Ethereum Attestation Service
 (EAS)](https://ethereum.org/en/developers/docs/standards/tokens/eas/) by SEAL to protocols that successfully complete a
 certified audit. Attestations serve as verifiable proof that a protocol has met the requirements of a given SEAL
-Certifications certification.
+certification.
 
 Attestations do not indicate that a protocol is completely secure or free from issues. Blockchain security is always
 evolving and novel vulnerabilities arise regularly. Instead, attestations demonstrate that a protocol has implemented a
@@ -145,7 +145,7 @@ here: [Certified Protocols](/certs/certified-protocols.mdx). */}
 <summary>How can auditors become certified?</summary>
 
 SEAL works with a group of third-party auditing firms to provide certification audits. For more information on the
-process or now to become certified, see our [Certified Auditors](/certs/certified-partners.mdx) page.
+process or how to become certified, see our [Certified Auditors](/certs/certified-partners) page.
 
 </details>
 <details>
diff --git a/docs/pages/certs/sfc-dns-registrar.mdx b/docs/pages/certs/sfc-dns-registrar.mdx
index e1ff72dc..cf6b4a75 100644
--- a/docs/pages/certs/sfc-dns-registrar.mdx
+++ b/docs/pages/certs/sfc-dns-registrar.mdx
@@ -189,7 +189,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter, Cer
 
 # SFC - DNS Registrar
 
-The SEAL Framework Checklist (SFC) for DNS Registrar provides best practice for securely managing domain names and DNS configurations.
+The SEAL Framework Checklist (SFC) for DNS Registrar provides best practices for securely managing domain names and DNS configurations.
 
 For more details on certifications or self-assessments, refer to the [Certification Guidelines](/certs/certification-guidelines).
 
diff --git a/docs/pages/certs/sfc-incident-response.mdx b/docs/pages/certs/sfc-incident-response.mdx
index 2ba626e0..0948dc9c 100644
--- a/docs/pages/certs/sfc-incident-response.mdx
+++ b/docs/pages/certs/sfc-incident-response.mdx
@@ -199,7 +199,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter, Cer
 
 # SFC - Incident Response
 
-The SEAL Framework Checklist (SFC) for Incident Response provides structured guidelines to help remain prepared for
+The SEAL Framework Checklist (SFC) for Incident Response provides structured guidelines to help teams remain prepared for
 security incidents affecting blockchain protocols. It covers team structure, monitoring, alerting, and response
 procedures.
 
diff --git a/docs/pages/certs/sfc-workspace-security.mdx b/docs/pages/certs/sfc-workspace-security.mdx
index f1304d0a..b70fcfef 100644
--- a/docs/pages/certs/sfc-workspace-security.mdx
+++ b/docs/pages/certs/sfc-workspace-security.mdx
@@ -33,7 +33,7 @@ cert:
       - Scoped to devices and accounts with access to sensitive systems or data
       - Device inventory tracks make/model, owner, OS version, encryption status,
         and EDR/MDM enrollment
-      - Account inventory covers organizational accounts (eg. email, cloud, social media)
+      - Account inventory covers organizational accounts (e.g., email, cloud, social media)
         with defined ownership
       - Updated as devices/accounts are provisioned or decommissioned
     title: Asset Inventory
diff --git a/docs/pages/community-management/overview.mdx b/docs/pages/community-management/overview.mdx
index 06983914..b0479081 100644
--- a/docs/pages/community-management/overview.mdx
+++ b/docs/pages/community-management/overview.mdx
@@ -20,7 +20,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Communities might be the key of many Web3 projects, but they also represent a significant security challenge. From
+Communities might be key to many Web3 projects, but they also represent a significant security challenge. From
 casual users to top-level executives, everyone within an organization can be targeted by social engineering tactics
 across platforms like Telegram, Discord, X (formerly Twitter), Google, and more. When a community channel is
 compromised—whether by phishing, fraudulent links, or account takeovers—it can quickly become a vehicle for wider
@@ -39,7 +39,7 @@ platform-specific recommendations in more depth.
 - Secure the email account linked to your community platforms with a unique password and 2FA.
 - Always enable 2FA. Prefer hardware-based tokens (e.g., Yubikey) or mobile authenticator apps over SMS-based methods,
   which are vulnerable to SIM-swapping.
-- If you use an authenticator app like Authy, 1Password, or Aegis to generate time-based one-time passwords (TOTP).
+- If you use an authenticator app like Authy, 1Password, or Aegis to generate time-based one-time passwords (TOTP),
   Ensure that the secret keys are stored encrypted and protected with robust security measures.
 - Configure your app to require a password, PIN, or biometric authentication (e.g., fingerprint or face recognition) to
   unlock access to the tokens. This prevents unauthorized access and ensures the tokens remain secure even if someone
diff --git a/docs/pages/community-management/twitter.mdx b/docs/pages/community-management/twitter.mdx
index ecd76c46..b70608d6 100644
--- a/docs/pages/community-management/twitter.mdx
+++ b/docs/pages/community-management/twitter.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Twitter/X Security | Security Alliance"
-description: "Protect your X (Twitter) account from SIM swapping: remove your phone number, enable 2FA with authenticator app or security key, and enable password reset protection."
+description: "Protect your X (Twitter) account from SIM swapping: remove your phone number, enable 2FA with an authenticator app or security key, and enable password reset protection."
 tags:
   - Community & Marketing
 contributors:
diff --git a/docs/pages/config/template.mdx b/docs/pages/config/template.mdx
index b86bdae4..5c23e8c6 100644
--- a/docs/pages/config/template.mdx
+++ b/docs/pages/config/template.mdx
@@ -29,9 +29,11 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Key Takeaway prompt: Without removing or modifying anything in the document, just after the heading, describe in a
-succint way (no more than 40 words), all the key points or tl;dr so that anyone can get a good grasp of the contents
+succinct way (no more than 40 words), all the key points or tl;dr so that anyone can get a good grasp of the contents
 just by reading it. Don't add unnecessary sentences that sound like conclusions, like "By ensuring this..." "Doing all
-these...", "Having these security practinces...". Use the following format > 🔑 **Key Takeaway**:
+these...", "Having these security practices...". Use the following format:
+
+> 🔑 **Key Takeaway**:
 
 [Context / Problem statement. In this first part, we introduce the topic, in no more than a few paragraphs. For example
 for Threat Modeling inside Operational Security Framework: "Effective security requires understanding **what you're
diff --git a/docs/pages/config/using-contributors.mdx b/docs/pages/config/using-contributors.mdx
index 36143cf8..1d0dfa9a 100644
--- a/docs/pages/config/using-contributors.mdx
+++ b/docs/pages/config/using-contributors.mdx
@@ -48,7 +48,7 @@ This will display contributors in three sections: "Written by", "Reviewed by", a
 
 ## Contributors Database Location
 
-The contributors database is stored in `src/config/contributors.json`. Here's an example of what a contributor entry
+The contributors database is stored in `docs/pages/config/contributors.json`. Here's an example of what a contributor entry
 looks like:
 
 ```json
diff --git a/docs/pages/contribute/contributing.mdx b/docs/pages/contribute/contributing.mdx
index 43014148..7bc15781 100644
--- a/docs/pages/contribute/contributing.mdx
+++ b/docs/pages/contribute/contributing.mdx
@@ -4,7 +4,7 @@ description: "Contribute to SEAL Security Frameworks: fix typos, add new section
 ---
 
 {/*
-This file is a duplicate of the CONTRIBUTE.md at the root level.
+This file is a duplicate of the CONTRIBUTING.md at the root level.
 
 Both files contain the same content: the root-level file is there to be highlighted in the repository dashboard,
 while this copy is used to render the content on the website.
@@ -55,7 +55,7 @@ approved, they will be merged into the **main branch** for publication on the st
 ## Ways to contribute
 
 There are several ways to contribute, depending on your preference and the scope of your changes. First, check existing
-PRs or branches to make sure your work has not been previously ****submitted**.**
+PRs or branches to make sure your work has not been previously submitted.
 
 ### 1. Quick edits
 
@@ -71,7 +71,6 @@ All contributions should follow this workflow:
 2. **Follow the [`template.mdx`](https://github.com/security-alliance/frameworks/blob/develop/docs/pages/config/template.mdx)
 page** when creating or expanding content. It contains pre-defined components and structure required for consistency
 in MDX files.
-structure required for consistency in MDX files.
 3. **Make your changes** in MDX (typos, improvements, or new content) on your fork.
 4. **Open a Pull Request (PR) against the `develop` branch** of this repository. Once submitted, you can see the
 deployment through the automated preview and make any final adjustments.
@@ -94,7 +93,7 @@ Choose the development approach that works best for you:
 
 ### Option A: DevContainer with VSCode
 
-The easiest way to get started is using our pre-configured devcontainer with VSCode:
+The easiest way to get started is to use our pre-configured devcontainer with VSCode:
 
 1. **Prerequisites**: VSCode with [Dev Containers
 extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
@@ -105,7 +104,7 @@ extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.
 ### Option B: DevContainer CLI Only (No VSCode Required)
 
 Since you won't require extensions for the initiative to work, you can just create a devcontainer using the CLI and
-access it through whatever mean you think suits you best.
+access it through whatever means suit you best.
 
 **Using DevContainer CLI (Recommended):**
 
@@ -154,7 +153,7 @@ If you prefer to install dependencies locally on your machine:
     pnpm exec just serve
     ```
 
-5. Once the server is running, access the site at port ```5173```
+5. Once the server is running, access the site on port `5173`.
 
 **(Optional) Authenticate with GitHub CLI**: The GitHub CLI (`gh`) is already preinstalled in the devcontainer. You can
 authenticate by running `gh auth login` in the terminal, making it easy to interact with GitHub directly from your
@@ -321,7 +320,7 @@ This helps catch build or formatting issues early so reviewers see clean contrib
 Wiki pages follow standard MDX.
 
 The audience of this wiki is technical, and the content should reflect that. There are many guides on technical and
-documentation writing you can learn from, for example, you can check [this
+documentation writing you can learn from; for example, you can check [this
 lecture](https://www.youtube.com/watch?v=vtIzMaLkCaM) to get started.
 
 ### Writing guidelines
@@ -330,14 +329,12 @@ lecture](https://www.youtube.com/watch?v=vtIzMaLkCaM) to get started.
 - Use concise sentences and break down complex ideas with bullet points, tables, images, or block-quotes.
 - Always link your resources and verify them
 - Introduce acronyms and technical jargon before using them.
-- Web3 changes fast, write the content to be as future-proof as possible
+- Web3 changes fast; write the content to be as future-proof as possible.
 - Do **not** submit content entirely generated by AI; however, we recommend using it to fix grammar or phrasing
 - Consider tutorials or hands-on guides for practical steps.
 - Use visualizations (mermaid, diagrams, tables) to clarify concepts.
 - Add recommended reading or dependencies at the top of a page if relevant.
-- Focus on delivering credible, formal, technical content without unnecessary high-level introductions; use examples,
-
-comparisons, or anecdotes to clarify complex topics.
+- Focus on delivering credible, formal, technical content without unnecessary high-level introductions; use examples, comparisons, or anecdotes to clarify complex topics.
 
 - You can use mermaid diagrams for visualizations
 
@@ -389,7 +386,7 @@ Pages with minimal content which need more work to cover the topic need to inclu
 
 ## Anything else?
 
-This page is also open for contributions! Suggest improvements to our style and guidelines in the github repo.
+This page is also open for contributions! Suggest improvements to our style and guidelines in the GitHub repo.
 
 ## About this page
 
diff --git a/docs/pages/devsecops/code-signing.mdx b/docs/pages/devsecops/code-signing.mdx
index f835841a..53896464 100644
--- a/docs/pages/devsecops/code-signing.mdx
+++ b/docs/pages/devsecops/code-signing.mdx
@@ -4,7 +4,7 @@ description: "Verify code integrity with GPG-signed Pull Requests. Best practice
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -18,7 +18,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Code signing ensures that the code has not been tampered with, and verifies the identity of the developer. Here are some
-best practices that could be followed:
+best practices to follow:
 
 1. Ensure all Pull Requests (PRs) are signed with the user’s GPG key.
 2. Every PR must be reviewed by another core team member before being merged into the stable/main/master branch, with
diff --git a/docs/pages/devsecops/continuous-integration-continuous-deployment.mdx b/docs/pages/devsecops/continuous-integration-continuous-deployment.mdx
index db53174f..45395f7b 100644
--- a/docs/pages/devsecops/continuous-integration-continuous-deployment.mdx
+++ b/docs/pages/devsecops/continuous-integration-continuous-deployment.mdx
@@ -4,7 +4,7 @@ description: "Build secure CI/CD pipelines with GitHub Actions: unit tests, inte
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/devsecops/integrated-development-environments.mdx b/docs/pages/devsecops/integrated-development-environments.mdx
index 7b3d91a1..a35dd10d 100644
--- a/docs/pages/devsecops/integrated-development-environments.mdx
+++ b/docs/pages/devsecops/integrated-development-environments.mdx
@@ -4,7 +4,7 @@ description: "Secure your IDE with plugins from trusted sources only, restricted
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
diff --git a/docs/pages/devsecops/overview.mdx b/docs/pages/devsecops/overview.mdx
index 1739e722..e1634b8a 100644
--- a/docs/pages/devsecops/overview.mdx
+++ b/docs/pages/devsecops/overview.mdx
@@ -4,7 +4,7 @@ description: "DevSecOps Framework: Integrate security into your CI/CD pipelines
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 ---
 
@@ -20,13 +20,13 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 
 > 🔑 **Key Takeaway**: DevSecOps works when security is embedded from planning through delivery, automated checks stop unsafe changes before production, and sandboxed execution contains risk when untrusted code or tooling runs.
 
-Traditionally, rapid development and deployment is often prioritized at the expense of security considerations. This is
+Traditionally, rapid development and deployment are often prioritized at the expense of security considerations. This is
 generally speaking no different in web3, but it is important to take integrity, confidentiality, and availability into
 consideration too. To effectively address this without compromising on rapid development and deployment, it is essential
 to integrate security into the process, which is where devsecops comes into play. By implementing devsecops, projects
 can not only deploy faster, but also be more secure.
 
-When operating in a devsecops mindset, projects prioritizes automation and collaboration between the development,
+When operating in a devsecops mindset, projects prioritize automation and collaboration between the development,
 operations and security teams.
 
 Some of the key areas to consider are:
diff --git a/docs/pages/devsecops/repository-hardening.mdx b/docs/pages/devsecops/repository-hardening.mdx
index 6c268e98..39e25e1a 100644
--- a/docs/pages/devsecops/repository-hardening.mdx
+++ b/docs/pages/devsecops/repository-hardening.mdx
@@ -4,7 +4,7 @@ description: "Harden your GitHub repository with MFA, protected branches, signed
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
diff --git a/docs/pages/devsecops/security-testing.mdx b/docs/pages/devsecops/security-testing.mdx
index 9d1c869f..889c8e4b 100644
--- a/docs/pages/devsecops/security-testing.mdx
+++ b/docs/pages/devsecops/security-testing.mdx
@@ -4,7 +4,7 @@ description: "Identify vulnerabilities early with SAST, DAST, and IAST tools in
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/dprk-it-workers/general-information.mdx b/docs/pages/dprk-it-workers/general-information.mdx
index c660f981..eec93b43 100644
--- a/docs/pages/dprk-it-workers/general-information.mdx
+++ b/docs/pages/dprk-it-workers/general-information.mdx
@@ -59,7 +59,7 @@ scale](https://cloud.google.com/blog/topics/threat-intelligence/dprk-it-workers-
 
 1. Generating stable revenue for the North Korean regime through remote IT work.
 2. Building support networks for North Korean IT-related operations (mules and money laundering).
-3. Gaining access to Western companies technology, infrastructure, and identities (both personal and company, digital
+3. Gaining access to Western companies' technology, infrastructure, and identities (both personal and company, digital
     and physical).
 4. Exfiltrating company secrets (intentionally and unintentionally).
 5. Extortion (ransomware and blackmail).
diff --git a/docs/pages/dprk-it-workers/mitigating-dprk-it-workers.mdx b/docs/pages/dprk-it-workers/mitigating-dprk-it-workers.mdx
index 1a95dca5..a778a1d8 100644
--- a/docs/pages/dprk-it-workers/mitigating-dprk-it-workers.mdx
+++ b/docs/pages/dprk-it-workers/mitigating-dprk-it-workers.mdx
@@ -83,12 +83,12 @@ limit the effects of a DPRK IT Worker infiltration and what you should do after
     approaches.
 4. Monitor your logs for IP addresses, user sessions, and timestamped access. Monitor your remote contributors' actions
     for any sudden changes (identity changes) and potential secrets leaks through their private accounts. You can obtain
-    such information from Google, Slack or Github Workspaces, depending on your organization setup and tiers.
-5. **DO NOT allow hired contributors to use throwaway Github accounts for the work at your company!** It's part of the
+    such information from Google, Slack or GitHub Workspaces, depending on your organization setup and tiers.
+5. **DO NOT allow hired contributors to use throwaway GitHub accounts for the work at your company!** It's part of the
     DPRK IT Worker tactics to save their main accounts from being discovered.
 6. If your project allows, it may be beneficial to establish a public codebase on GitHub and have your remote workers
     make at least *some* public contributions related to your project. If all of your codebase is supposed to stay private,
-    at least list all of the contributors (CODEOWNERS) in a special repository created only for such purpose. Security
+    at least list all of the contributors (CODEOWNERS) in a special repository created specifically for that purpose. Security
     researchers like SEAL911 scan such public codebases and will notify you privately if they suspect DPRK IT Workers are
     contributing to your project.
 
@@ -101,7 +101,7 @@ limit the effects of a DPRK IT Worker infiltration and what you should do after
     immediately and aim to remove the DPRK IT Worker within the next few days at most. If your organization is properly
     siloed from insider threats, you shouldn't have much of an issue firing the worker almost immediately after
     conducting a post-mortem review.
-3. **Check if you did not hire more than one DPRK IT Worker. In the majority of cases, we find more DPRK IT Workers
+3. **Check whether you hired more than one DPRK IT Worker. In the majority of cases, we find more DPRK IT Workers
     within the same organization.** They do not always come as a recommendation from an already-discovered DPRK IT Worker;
     they simply already know how to abuse your hiring process.
 4. At the same time, **you should immediately cease any further payments to the DPRK IT Worker. It's illegal.** You can
@@ -113,7 +113,7 @@ limit the effects of a DPRK IT Worker infiltration and what you should do after
     but it can be of overall poor quality. **Pay extra attention to added dependencies or edited CI/CD files.**
 7. Review the permissions that these actors have or had in your organization. **Revoke them.**
 8. **Review all of the files and links previously provided by the DPRK IT Worker and who opened them.** The issue may
-    extend beyond your technical workers. Look back to see if you did not potentially run malware-infested code or give them
+    extend beyond your technical workers. Look back to see whether you potentially ran malware-infested code or give them
     remote desktop access to your or your developers' machines.
 9. Set up a final confirmation call after all access is revoked and you are certain your organization is safe from any
     insider threats. **Attempt to perform KYC under some pretense. Do not settle for document scans, as these are easily
diff --git a/docs/pages/dprk-it-workers/techniques-tactics-and-procedures.mdx b/docs/pages/dprk-it-workers/techniques-tactics-and-procedures.mdx
index 2e3250b5..e0230246 100644
--- a/docs/pages/dprk-it-workers/techniques-tactics-and-procedures.mdx
+++ b/docs/pages/dprk-it-workers/techniques-tactics-and-procedures.mdx
@@ -140,7 +140,7 @@ hiring a DPRK IT Worker.
                 and NFT-related avatars (especially Pengu and Doodles).
              3. **Having no avatar at all is also common.**
              4. Reference:
-                [Identifying Suspicious Github Accounts](https://www.ketman.org/identifying-suspicious-gh-accounts.html)
+                [Identifying Suspicious GitHub Accounts](https://www.ketman.org/identifying-suspicious-gh-accounts.html)
          7. **Social media links.**
              1. In many cases, there will be a Twitter link. It's always worth visiting.
                  1. Check the "Media" page for images uploaded by the account owner. **Can you find any
@@ -161,11 +161,11 @@ hiring a DPRK IT Worker.
                 dump of the GitHub account may be useful, but cherry-picking a few repositories from the profile is often
                 effective enough for a first pass.
                  1. Reference:
-                    [A counter example - Good looking IT Worker Github
+                    [A counter example - Good looking IT Worker GitHub
                     Profiles](https://x.com/blackbigswan/status/1873364567285449160)
          9. **Repositories.**
              1. "Copied repositories." DPRK IT workers will try to boost their credibility by pushing a clone
-                of a legitimate repository to their own account (Google: "How to fake Github history"). They will often
+                of a legitimate repository to their own account (Google: "How to fake GitHub history"). They will often
                 edit the `.git` config and insert their own account data. Usually, they won't remove all original
                 contributors but will insert themselves among them. **Use GitHub's search feature to find the original
                 repository by name, commit SHA, or a unique string extracted from within the repository. Compare the actual
@@ -176,7 +176,7 @@ hiring a DPRK IT Worker.
                 contribution like a PR or commit or just a spam Issue/Comment/PR. This is an often-utilized method for
                 highly popular repositories (e.g., OpenZeppelin, Paradigm) where core developers are reluctant to merge
                 spam PRs.
-                 1. Reference: [DPRK IT Workers faking Github Activity
+                 1. Reference: [DPRK IT Workers faking GitHub Activity
                 Badges](https://x.com/blackbigswan/status/1876953373187920054/photo/1)
      11. **Evaluating other immediately available data points:**
          1. **Full Name.**
@@ -216,7 +216,7 @@ hiring a DPRK IT Worker.
     DPRK IT Worker. We're focusing on using non-enterprise flags accessible to even the smallest of projects.
     The assumption is that your project has limited EDR/SIEM logging infrastructure (you should, however, consider
     implementing some monitoring infrastructure in the future).
-     1. If your organization has EDR/SIEM capability, Read:
+     1. If your organization has EDR/SIEM capability, read:
         [DTEX advisory on DPRK Insider Threat Kill
         Chain](https://www.dtexsystems.com/resources/i3-threat-advisory-inside-the-dprk/)
      2. Consider using GitHub Enterprise for your organization to have access to more detailed logs.
@@ -271,12 +271,12 @@ hiring a DPRK IT Worker.
         'small talk.' This isn't necessarily because of cultural differences (DPRK IT Workers are educated on Western
         culture and language as part of their job). It's often because of the sheer volume of remote gigs they handle
         and how confusing it can be. A DPRK IT Worker will prefer to always steer the conversation toward technical details.
-     10.**Review Workspace logs (IP addresses).** Check if the IP addresses used to log in to your infrastructure
+     10. **Review Workspace logs (IP addresses).** Check if the IP addresses used to log in to your infrastructure
         are coming from the same location as claimed by the worker. VPNs, proxies, or Russian ISPs are red flags, as
         are highly inconsistent IP ranges (a mix of the sources mentioned). Beware that DPRK IT Workers are known to
         utilize "Laptop Farms."
         Read: [North Korea Infiltrates U.S. Remote Jobs - With the Help of Everyday Americans](https://archive.ph/Mb68C)
-     11.**Payments.** North Koreans can organize a 'drop' bank account to receive wire transfers; however, their
+     11. **Payments.** North Koreans can organize a 'drop' bank account to receive wire transfers; however, their
         preferred method of receiving a salary will be through cryptocurrency, usually at a flat rate that they
         will not try to negotiate. In most cases, DPRK IT Workers will work at a discount to industry standards
         without complaining (25-50% discount). It may be the case that the worker's CEX account gets frozen, and they will
diff --git a/docs/pages/encryption/cloud-data-encryption.mdx b/docs/pages/encryption/cloud-data-encryption.mdx
index 1187f756..f4ac99b1 100644
--- a/docs/pages/encryption/cloud-data-encryption.mdx
+++ b/docs/pages/encryption/cloud-data-encryption.mdx
@@ -4,7 +4,7 @@ description: "Protect cloud data with AES-256 encryption at rest and TLS 1.2+ in
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - Cloud
 ---
 
@@ -18,7 +18,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-You should consider using the best practices below, in order to ensure that data stored in the cloud
+You should consider using the best practices below to ensure that data stored in the cloud
 is protected from unauthorized access:
 
 ## Best Practices
diff --git a/docs/pages/encryption/communication-encryption.mdx b/docs/pages/encryption/communication-encryption.mdx
index 7ae5cf3f..0c4a5915 100644
--- a/docs/pages/encryption/communication-encryption.mdx
+++ b/docs/pages/encryption/communication-encryption.mdx
@@ -43,7 +43,7 @@ popular messaging systems that offer end-to-end encryption and those that do not
 
 ## Messaging Systems Without Default End-to-End Encryption
 
-These messaging systems supposedly provides encryption for data in transit and at rest, but not end-to-end encryption
+These messaging systems supposedly provide encryption for data in transit and at rest, but not end-to-end encryption
 for messages.
 
 1. **Telegram**
diff --git a/docs/pages/encryption/database-encryption.mdx b/docs/pages/encryption/database-encryption.mdx
index f172ce9f..9ed5fb22 100644
--- a/docs/pages/encryption/database-encryption.mdx
+++ b/docs/pages/encryption/database-encryption.mdx
@@ -16,7 +16,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Often, databases contains information that should not be publicly available. In order to protect your database, you may
+Often, databases contain information that should not be publicly available. In order to protect your database, you may
 consider implementing the following best practices:
 
 ## Best Practices
diff --git a/docs/pages/encryption/encryption-in-transit.mdx b/docs/pages/encryption/encryption-in-transit.mdx
index e6676b6f..00592db4 100644
--- a/docs/pages/encryption/encryption-in-transit.mdx
+++ b/docs/pages/encryption/encryption-in-transit.mdx
@@ -16,7 +16,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Encryption in transit means how data is being encrypted while it flows across networks. This is important as you don't
+Encryption in transit refers to how data is encrypted while it flows across networks. This is important as you don't
 want anyone eavesdropping on your traffic, and by following best practices such as the ones below, you can reduce the
 risk of that:
 
diff --git a/docs/pages/encryption/file-encryption.mdx b/docs/pages/encryption/file-encryption.mdx
index 39288160..6f6a4a12 100644
--- a/docs/pages/encryption/file-encryption.mdx
+++ b/docs/pages/encryption/file-encryption.mdx
@@ -19,7 +19,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 File encryption protects sensitive information stored in files.
 
 Use strong encryption algorithms to encrypt sensitive files stored on local and network drives.
-There are multiple tools available for file encryption, use one that is regarded as trusted.
+There are multiple tools available for file encryption; use one that is regarded as trusted.
 
 ---
 
diff --git a/docs/pages/encryption/overview.mdx b/docs/pages/encryption/overview.mdx
index 3d08e5ba..eb7e0515 100644
--- a/docs/pages/encryption/overview.mdx
+++ b/docs/pages/encryption/overview.mdx
@@ -4,7 +4,7 @@ description: "Encryption Framework: Comprehensive guide covering cloud, communic
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - Cloud
 ---
 
diff --git a/docs/pages/encryption/volume-encryption.mdx b/docs/pages/encryption/volume-encryption.mdx
index 0f96ddca..2880465b 100644
--- a/docs/pages/encryption/volume-encryption.mdx
+++ b/docs/pages/encryption/volume-encryption.mdx
@@ -67,7 +67,6 @@ to specific volumes and ensures compliance with data protection regulations.
 
 By following these best practices and using reliable volume encryption technologies, organizations can significantly
 enhance the security of their data and protect against unauthorized access and data breaches.
-$$
 
 ---
 
diff --git a/docs/pages/external-security-reviews/overview.mdx b/docs/pages/external-security-reviews/overview.mdx
index 1257202d..bb54b193 100644
--- a/docs/pages/external-security-reviews/overview.mdx
+++ b/docs/pages/external-security-reviews/overview.mdx
@@ -4,7 +4,7 @@ description: "External Security Reviews: Security assessments to identify vulner
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
 contributors:
   - role: wrote
     users: [patrickalphac]
diff --git a/docs/pages/external-security-reviews/smart-contracts/manual-review.mdx b/docs/pages/external-security-reviews/smart-contracts/manual-review.mdx
index 20f416b2..14b1081e 100644
--- a/docs/pages/external-security-reviews/smart-contracts/manual-review.mdx
+++ b/docs/pages/external-security-reviews/smart-contracts/manual-review.mdx
@@ -28,7 +28,7 @@ possible things the process can comprise.
 ## Gather resources
 
 1. **Scope:**
-This can be a link to the code repository. e.g. Github, Gitlab link which consist of all the smart contracts required to
+This can be a link to the code repository. e.g. GitHub, GitLab link which consists of all the smart contracts required to
 be reviewed.
 
 2. **Commit hash:**
@@ -41,7 +41,7 @@ under review.
     - Specification defines the exact requirements, constraints, and behaviors the system must meet, including
     invariants that must always hold true.
         - Invariants are the properties of the system that should always hold. Invariants can be useful for checking the
-        expected behavior of the system when the certain actions or a transaction flow is executed. Invariants are
+        expected behavior of the system when certain actions or a transaction flow are executed. Invariants are
         useful in many testing approaches, including manual reviews, where a reviewer checks whether a specific
         property can be violated for a function under any sequence of function calls.
         - Get simplified math formulas if the protocol has any custom/fancy formulas implemented.
@@ -54,7 +54,7 @@ following types of tests can be useful for understanding and verifying the code:
     - [Integration Tests](/security-testing/integration-testing): Integration tests verify that your smart contracts
     work correctly with real external systems.
 
-## Smart contract higher overview
+## Smart contract high-level overview
 
 1. **Documentation and whitepaper walkthrough:**
 Go through the whitepaper and documentation to gain a better understanding of the project and to see how the proposed
@@ -69,7 +69,7 @@ protocol.
 
 4. **Create a diagram:**
 Based on the structural and functional understanding the high level diagram can be created if required.
-    - The diagram can be modified over a time as you get more understanding.
+    - The diagram can be modified over time as you get more understanding.
     - The diagram can grow more complex and detailed depending on the time.
     - There are many tools that can be used like Excalidraw, Miro, Lucidchart, Mermaid etc.
     - High level structural example of staking diagram:
@@ -113,14 +113,14 @@ tests. Test cases are important. They give you an understanding of how the setup
 place for users to start using the system’s entry points. They also give you time to test more offensive or edge-case
 scenarios (after verifying unit tests) instead of spending most of your time testing general scenarios.
 
-    - When math formulas or complex interconnected calls are involved, debugging the values of variables helps sometime
+    - When math formulas or complex interconnected calls are involved, debugging the values of variables helps sometimes
     to see how the state changes are happening e.g. what is the value of variable `x/totalStakedEth` before the specific
     internal/external call. or what it becomes after that call.
-    - Debugging can be done in many ways, depending on which framework you are using. Some examples are.
+    - Debugging can be done in many ways, depending on which framework you are using. Some examples include:
         - Foundry - native debugger, console logs in the contracts, Tenderly debugger, simbolik.
         - Hardhat - console logs in the contracts, debuggers like Hardhat-tracer, Tenderly debugger.
 
-2. **Choose least dependent contract to review one by one:**
+2. **Choose the least dependent contract to review first:**
 This can be done by looking into a diagram and current understanding of the smart contract functionality. For example
 in this case it's a Token contract that is least dependent (in fact the functionality from that contract is getting used
 in other contracts so other smart contracts are dependent on it).
@@ -135,7 +135,7 @@ in other contracts so other smart contracts are dependent on it).
         Standard](https://github.com/ComposableSecurity/SCSVS?tab=readme-ov-file#table-of-contents)
 
 4. **Maintain a list of invariants:**
-Maintain a list of invariants for every functions (Can be useful later for other tests/fuzzing/format verification).
+Maintain a list of invariants for every function (Can be useful later for other tests/fuzzing/format verification).
 
 5. **Offensively analyze the code:**
 Offensively analyze the code to identify logical issues, edge cases, and any conditions that could break invariants.
@@ -177,10 +177,10 @@ coverage reports for tests.
     }
     ```
 
-    In next example, because every value (`_amount`, `minRequired`) can go increase or decrease, the results can vary.
+    In next example, because every value (`_amount`, `minRequired`) can increase or decrease, the results can vary.
     If the result is used for some operations like decreasing the `drivingScore` in `burnFuelAndReduce()` for example.
 
-    E.g. depending on the amounts are same (as they were while filling the fuel) or increased or decreased, the value of
+    E.g. depending on whether the amounts are the same (as they were while filling the fuel) or increased or decreased, the value of
     `fuelReduction` will change and while subtracting it from the `drivingScore[msg.sender]` it needs to be handled
     accordingly. which also creates different paths.
 
@@ -280,7 +280,7 @@ like [Slither](https://github.com/crytic/slither), [Wake](https://github.com/Ack
 [Aderyn](https://github.com/Cyfrin/aderyn) etc.
 
 > There are other types of automated testing approaches, such as [Fuzz Testing](/security-testing/fuzz-testing) and
-> [formal verification](/security-testing/formal-verification), can also be helpful at different stages of the audit
+> [formal verification](/security-testing/formal-verification) can also be helpful at different stages of the audit
 > life-cycle, though they are less directly related to manual review.
 
 ## Report writing
@@ -327,7 +327,7 @@ it yields the expected output.
 For the updated functionality (depending on what has been changed), review the checklists to ensure that no
 vulnerabilities remain or have been introduced.
 
-6. **Check things/notes that needs to be revisited:**
+6. **Check things/notes that need to be revisited:**
 Check items or notes that need to be revisited from the manual review. Sometimes you may have observations noted, e.g.,
 Adding this fix to the code can create this problem.
 
diff --git a/docs/pages/external-security-reviews/smart-contracts/overview.mdx b/docs/pages/external-security-reviews/smart-contracts/overview.mdx
index 669a2f4f..7adaaeb6 100644
--- a/docs/pages/external-security-reviews/smart-contracts/overview.mdx
+++ b/docs/pages/external-security-reviews/smart-contracts/overview.mdx
@@ -4,7 +4,7 @@ description: "Smart contract audits: scoping, static analysis, manual review, an
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
 contributors:
   - role: wrote
     users: [patrickalphac]
diff --git a/docs/pages/external-security-reviews/smart-contracts/preparation.mdx b/docs/pages/external-security-reviews/smart-contracts/preparation.mdx
index 2d263bea..28b266ac 100644
--- a/docs/pages/external-security-reviews/smart-contracts/preparation.mdx
+++ b/docs/pages/external-security-reviews/smart-contracts/preparation.mdx
@@ -4,7 +4,7 @@ description: "Prepare for a smart contract audit: run Slither for static analysi
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
 contributors:
   - role: wrote
     users: [patrickalphac]
diff --git a/docs/pages/external-security-reviews/smart-contracts/vendor-selection.mdx b/docs/pages/external-security-reviews/smart-contracts/vendor-selection.mdx
index ef05b62c..692e6f17 100644
--- a/docs/pages/external-security-reviews/smart-contracts/vendor-selection.mdx
+++ b/docs/pages/external-security-reviews/smart-contracts/vendor-selection.mdx
@@ -100,7 +100,7 @@ issues to win a share of a prize pool.
 
 # Audit the Auditors
 
-As of today, the best review of the security reviewers that we have is the historical performance of security reviewers.
+As of today, the best way to evaluate security reviewers is their historical performance.
 One of the best ways to evaluate this is to review the historical performance of the security team.
 
 If you see codebases that they reviewed were hacked, this doesn't mean that the team is bad. There are two types of
diff --git a/docs/pages/front-end-web-app/common-vulnerabilities.mdx b/docs/pages/front-end-web-app/common-vulnerabilities.mdx
index e34574ed..f59f23c1 100644
--- a/docs/pages/front-end-web-app/common-vulnerabilities.mdx
+++ b/docs/pages/front-end-web-app/common-vulnerabilities.mdx
@@ -4,7 +4,7 @@ description: "Understand common web and mobile vulnerabilities: Account Takeover
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -23,7 +23,7 @@ some frequently encountered vulnerabilities:
 ## General Vulnerabilities
 
 - **Account Takeovers**: Having the administrator accounts for your services (DNS, Cloud, Domain Registrar, Email,
-Github, etc.) is likely to be devastating to your project, as a threat actor can then make malicious changes. To protect
+GitHub, etc.) is likely to be devastating to your project, as a threat actor can then make malicious changes. To protect
 against this, it is recommended to follow best practices with regards to account security and use hardware 2FA
 solutions to secure the accounts.
 
diff --git a/docs/pages/front-end-web-app/overview.mdx b/docs/pages/front-end-web-app/overview.mdx
index 0e3e0946..d3d2f130 100644
--- a/docs/pages/front-end-web-app/overview.mdx
+++ b/docs/pages/front-end-web-app/overview.mdx
@@ -4,7 +4,7 @@ description: "Front-End Security Framework: Secure your Web3 front-end against a
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -17,9 +17,9 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Often an overlooked area, but ensuring the security of your front-end web and potential mobile applications is crucial
+Although often overlooked, ensuring the security of your front-end web and potential mobile applications is crucial
 for protecting your users. If the front-end web application is compromised, it could have severe effects on your users
-as they for example could start interacting with a malicious contract instead of your official contract.
+as they could, for example, start interacting with a malicious contract instead of your official contract.
 
 ## Contents
 
diff --git a/docs/pages/front-end-web-app/security-tools-resources.mdx b/docs/pages/front-end-web-app/security-tools-resources.mdx
index cd863393..42716276 100644
--- a/docs/pages/front-end-web-app/security-tools-resources.mdx
+++ b/docs/pages/front-end-web-app/security-tools-resources.mdx
@@ -16,7 +16,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-There is a very large amount of security tools and resources available, and sometimes it can feel overwhelming.
+There are a very large number of security tools and resources available, and sometimes it can feel overwhelming.
 
 There is a wide range of security tools to test your web & mobile applications, such as OWASP ZAP or Burp Suite to scan
 your application for vulnerabilities, Snyk to check your dependencies, or MobSF for security analysis on Android/iOS
diff --git a/docs/pages/governance/compliance-regulatory-requirements.mdx b/docs/pages/governance/compliance-regulatory-requirements.mdx
index 57891611..e7b03186 100644
--- a/docs/pages/governance/compliance-regulatory-requirements.mdx
+++ b/docs/pages/governance/compliance-regulatory-requirements.mdx
@@ -4,7 +4,7 @@ description: "Navigate regulatory compliance: GDPR, MiCA, HIPAA, PCI DSS. Best p
 tags:
   - Operations & Strategy
   - Legal & Compliance
-  - Devops
+  - DevOps
   - HR
 ---
 
@@ -26,7 +26,7 @@ necessary compliance helps protect your project from potential legal penalties.
 Some examples of regulatory frameworks or standards for web3 are:
 
 - **GDPR (General Data Protection Regulation)**: Applies to organizations handling the personal data of EU citizens. It
-mandates strict data protection measures and grants individuals significant rights over their data, as soon on
+mandates strict data protection measures and grants individuals significant rights over their data, as seen on
 [https://gdpr.eu/](https://gdpr.eu/).
 - **MiCA**: Companies seeking to offer crypto services or assets within the EU are in scope. While this may seem
 daunting, there are different levels of compliance needed depending on the project, as can be seen on
diff --git a/docs/pages/governance/risk-management.mdx b/docs/pages/governance/risk-management.mdx
index 82cc6d05..aa2671e8 100644
--- a/docs/pages/governance/risk-management.mdx
+++ b/docs/pages/governance/risk-management.mdx
@@ -26,7 +26,7 @@ communicating risk findings and mitigation strategies to relevant people.
 
 1. Use established frameworks such as NIST, ISO 27001, or COBIT to help start your risk management efforts.
 2. Focus on the most critical risks first, using a risk matrix to prioritize based on likelihood and impact.
-3. Conduct regular risk assessments and reviews to keep up with the so very evolving threat landscape.
+3. Conduct regular risk assessments and reviews to keep up with the rapidly evolving threat landscape.
 4. Use lessons learned from past incidents and risk assessments to continuously improve your risk management practices.
 
 ---
diff --git a/docs/pages/guides/account-management/github.mdx b/docs/pages/guides/account-management/github.mdx
index 1d383209..58988cf7 100644
--- a/docs/pages/guides/account-management/github.mdx
+++ b/docs/pages/guides/account-management/github.mdx
@@ -107,7 +107,7 @@ protections:
     actions are used
   - [ ]  Fork pull request workflows > Run workflows from fork pull requests > **Off**
   - [ ]  Workflow permissions > **Read repository contents and packages permissions**
-    - [ ]  Allow Github Actions to create and approve pull requests > **Off**
+    - [ ]  Allow GitHub Actions to create and approve pull requests > **Off**
   - [ ]  Access > **Not accessible**
 
 #### Security Features
diff --git a/docs/pages/guides/account-management/twitter.mdx b/docs/pages/guides/account-management/twitter.mdx
index 9478b712..ce2acbd0 100644
--- a/docs/pages/guides/account-management/twitter.mdx
+++ b/docs/pages/guides/account-management/twitter.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Twitter/X Security | Security Alliance"
-description: "Protect your X (Twitter) account from SIM swapping: remove your phone number, enable 2FA with authenticator app or security key, and enable password reset protection."
+description: "Protect your X (Twitter) account from SIM swapping: remove your phone number, enable 2FA with an authenticator app or security key, and enable password reset protection."
 tags:
   - Community & Marketing
 contributors:
@@ -126,7 +126,7 @@ these on their own accounts.
 It is recommended to ensure the email you use does not match your public name, is publicly known, or is easily
 guessable.
 
-You can easily work around this by supplementing your email address with a "+" suffix - e.g.
+You can easily work around this by supplementing your email address with a "+" suffix, for example
 `myemailusername+randomcharacters@gmail.com` (works with Gmail and iCloud emails).
 
 ---
diff --git a/docs/pages/iam/access-management.mdx b/docs/pages/iam/access-management.mdx
index 3134329f..7c5e8ebf 100644
--- a/docs/pages/iam/access-management.mdx
+++ b/docs/pages/iam/access-management.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - HR
 ---
 
@@ -39,7 +39,7 @@ respond to unauthorized access attempts.
 ## Best Practices for Access Management
 
 1. Grant users the minimum access necessary to perform their job functions.
-2. Ensure that critical tasks require multiple users to perform, reducing the risk of misuse.
+2. Ensure that critical tasks require multiple users to perform them, reducing the risk of misuse.
 3. When possible, use automated tools to manage access provisioning and revocation based on user lifecycle events.
 
 ---
diff --git a/docs/pages/iam/role-based-access-control.mdx b/docs/pages/iam/role-based-access-control.mdx
index 1579852e..7c1bd9f7 100644
--- a/docs/pages/iam/role-based-access-control.mdx
+++ b/docs/pages/iam/role-based-access-control.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - HR
 ---
 
@@ -20,7 +20,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Role-Based Access Control (RBAC) is a method of regulating access to systems and data based on the roles assigned to
-individual users within an project. RBAC ensures that users have the minimum access necessary to perform their job
+individual users within a project. RBAC ensures that users have the minimum access necessary to perform their job
 functions, reducing the risk of unauthorized access.
 
 ## Key Principles of RBAC
diff --git a/docs/pages/iam/secure-authentication.mdx b/docs/pages/iam/secure-authentication.mdx
index 107491ce..b14b651b 100644
--- a/docs/pages/iam/secure-authentication.mdx
+++ b/docs/pages/iam/secure-authentication.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - HR
 ---
 
diff --git a/docs/pages/incident-management/communication-strategies.mdx b/docs/pages/incident-management/communication-strategies.mdx
index c52885f7..c5308c42 100644
--- a/docs/pages/incident-management/communication-strategies.mdx
+++ b/docs/pages/incident-management/communication-strategies.mdx
@@ -17,8 +17,8 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Communication during an incident can be very hard, as people are often scrambling to fix the issue at hand. Nonetheless,
-from aa team member, outsider or observer's point of view, communication is very important to be able to understand
-what's happening, and it also provide some time to reflect and think about what is going on. With that said, providing
+from a team member’s, outsider’s, or observer’s point of view, communication is very important to be able to understand
+what's happening, and it also provides some time to reflect and think about what is going on. With that said, providing
 information before confirming that it's accurate, can often be very negative and cause uncertainty. It is recommended to
 have a person designated for communication during an incident, and that updates are sent out on a fixed schedule, and
 it can often be that the update is that there is currently no new information available.
diff --git a/docs/pages/incident-management/incident-detection-and-response.mdx b/docs/pages/incident-management/incident-detection-and-response.mdx
index b1e1884b..be1f1289 100644
--- a/docs/pages/incident-management/incident-detection-and-response.mdx
+++ b/docs/pages/incident-management/incident-detection-and-response.mdx
@@ -16,7 +16,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-You don't want to be that project which has funds stolen, and then don't notice it for multiple days. Early detection
+You don't want to be the project that has funds stolen and then doesn't notice it for multiple days. Early detection
 and effective response to security incidents will help minimize damage.
 
 ## Key Components of Incident Detection
diff --git a/docs/pages/incident-management/lessons-learned.mdx b/docs/pages/incident-management/lessons-learned.mdx
index 32b908a4..e4bd8e90 100644
--- a/docs/pages/incident-management/lessons-learned.mdx
+++ b/docs/pages/incident-management/lessons-learned.mdx
@@ -4,7 +4,7 @@ description: "Conduct post-incident reviews to improve response capabilities. Do
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/incident-management/overview.mdx b/docs/pages/incident-management/overview.mdx
index 0bdf2218..f8a390b9 100644
--- a/docs/pages/incident-management/overview.mdx
+++ b/docs/pages/incident-management/overview.mdx
@@ -4,7 +4,7 @@ description: "Incident Management Framework: Prepare for, detect, respond to, an
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/incident-management/playbooks/decentralized-ir.mdx b/docs/pages/incident-management/playbooks/decentralized-ir.mdx
index 183f0db5..76d2863a 100644
--- a/docs/pages/incident-management/playbooks/decentralized-ir.mdx
+++ b/docs/pages/incident-management/playbooks/decentralized-ir.mdx
@@ -4,7 +4,7 @@ description: "Decentralized Incident Response Framework (DeIRF) for security tea
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/incident-management/playbooks/hacked-dprk.mdx b/docs/pages/incident-management/playbooks/hacked-dprk.mdx
index a8d36cf7..fd53970e 100644
--- a/docs/pages/incident-management/playbooks/hacked-dprk.mdx
+++ b/docs/pages/incident-management/playbooks/hacked-dprk.mdx
@@ -31,7 +31,7 @@ itself. In **2024**, North Korea stole an estimated **1.34 billion USD** from th
 **February of 2025**, North Korea stole **1.5 billion USD** from Bybit exchange.
 
 North Korea operates a few different hacking squads, one of which we believe is responsible for compromising your
-computer. Each squad has their own preferred methodology, but their end goal is all the same: **to steal your private
+computer. Each squad has their own preferred methodology, but their end goal is the same: **to steal your private
 keys and your login information**.
 
 If you have been infected by North Korean malware, you should assume your private keys, files, and online accounts have
diff --git a/docs/pages/incident-management/playbooks/hacked-drainer.mdx b/docs/pages/incident-management/playbooks/hacked-drainer.mdx
index a677fd01..9930c301 100644
--- a/docs/pages/incident-management/playbooks/hacked-drainer.mdx
+++ b/docs/pages/incident-management/playbooks/hacked-drainer.mdx
@@ -42,7 +42,7 @@ known to:
 - Request permission to upgrade your wallet to a 7702 wallet, which gives them full control
 - Request your private key or seed phrase directly, which gives them full control
 
-Depending which type of drainer you were impacted on, you might need to take different actions to recover control of
+Depending on which type of drainer affected you, you might need to take different actions to recover control of
 your wallet.
 
 ---
diff --git a/docs/pages/incident-management/playbooks/malware.mdx b/docs/pages/incident-management/playbooks/malware.mdx
index 4a3c9546..b542b1d9 100644
--- a/docs/pages/incident-management/playbooks/malware.mdx
+++ b/docs/pages/incident-management/playbooks/malware.mdx
@@ -102,13 +102,13 @@ This means that your online accounts are at risk, such as:
 
 ## Notify the authorities
 
-If the hackers have managed to steal any crypto or take over any accounts or caused other impact, you need to begin the
+If the hackers have managed to steal any crypto, take over any accounts, or cause other impact, you need to begin the
 slow process of involving the legal system.
 
 Collect the following information:
 
 - Any addresses (including the chain) or exchange accounts that have been stolen from
-- Any transactions that the theft occurred in (including the chain)
+- Any transactions through which the theft occurred (including the chain)
 - Any accounts that the hackers messaged you from
 - Any URLs that you visited or downloaded files from
 - Any other suspicious activity you observed
diff --git a/docs/pages/incident-management/playbooks/seal-911-war-room-guidelines.mdx b/docs/pages/incident-management/playbooks/seal-911-war-room-guidelines.mdx
index f115de34..d663a773 100644
--- a/docs/pages/incident-management/playbooks/seal-911-war-room-guidelines.mdx
+++ b/docs/pages/incident-management/playbooks/seal-911-war-room-guidelines.mdx
@@ -251,7 +251,7 @@ is being shared; be wary.
 | Tenderly Tx Explorer | Tx Analysis, Debugging | Some features require login. |
 | Tenderly Alerts | Monitoring | Monitor addresses, on-chain actions, etc. Requires login. |
 | MetaSleuth | Monitoring | Monitor fund movement. 50 address limit. Requires login (premium feature). |
-| Github / Gist | Code Sharing | Create a private repo or secret gists and share the link with War Room participants only. |
+| GitHub / Gist | Code Sharing | Create a private repo or secret gists and share the link with War Room participants only. |
 | CodeShare | Code Sharing | Sessions expire after 24 hours. |
 | HackMD | Code Sharing | Private notes become published after ~48 hours. Be very careful with sensitive information! |
 
diff --git a/docs/pages/infrastructure/asset-inventory.mdx b/docs/pages/infrastructure/asset-inventory.mdx
index 4d0c6d65..48a548d5 100644
--- a/docs/pages/infrastructure/asset-inventory.mdx
+++ b/docs/pages/infrastructure/asset-inventory.mdx
@@ -4,7 +4,7 @@ description: "Document all project assets: contracts, hardware, software, cloud
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/infrastructure/cloud.mdx b/docs/pages/infrastructure/cloud.mdx
index d651d8e9..bf6d436c 100644
--- a/docs/pages/infrastructure/cloud.mdx
+++ b/docs/pages/infrastructure/cloud.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
diff --git a/docs/pages/infrastructure/ddos-protection.mdx b/docs/pages/infrastructure/ddos-protection.mdx
index 6f0e9058..bee91d4f 100644
--- a/docs/pages/infrastructure/ddos-protection.mdx
+++ b/docs/pages/infrastructure/ddos-protection.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
diff --git a/docs/pages/infrastructure/network-security.mdx b/docs/pages/infrastructure/network-security.mdx
index 5a24ba3d..b7b33635 100644
--- a/docs/pages/infrastructure/network-security.mdx
+++ b/docs/pages/infrastructure/network-security.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
diff --git a/docs/pages/infrastructure/operating-system-security.mdx b/docs/pages/infrastructure/operating-system-security.mdx
index 929c5f1e..dacbe139 100644
--- a/docs/pages/infrastructure/operating-system-security.mdx
+++ b/docs/pages/infrastructure/operating-system-security.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/infrastructure/overview.mdx b/docs/pages/infrastructure/overview.mdx
index 2967a53d..1740e127 100644
--- a/docs/pages/infrastructure/overview.mdx
+++ b/docs/pages/infrastructure/overview.mdx
@@ -4,7 +4,7 @@ description: "Infrastructure Framework: Secure Web3 infrastructure including clo
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
@@ -26,9 +26,9 @@ Service) protection.
 
 When designing your architecture, it may be worth considering how many different providers you rely on. Are you going to
 use different providers for infrastructure, DDoS protection, domain registration, and DNS, or will you choose a
-provider that provides all of these? On one hand, putting all eggs in one basket means a failure on said service would
-cause downtime, however by using a single service and ensuring it’s following all best practices with regards to
-security measures means a lower risk surface.
+provider that provides all of these? On one hand, putting all your eggs in one basket means a failure of that service
+would cause downtime. On the other hand, using a single service and ensuring it follows all best practices with regard
+to security measures means a lower risk surface.
 
 ## Contents
 
diff --git a/docs/pages/intro/how-to-navigate-the-website.mdx b/docs/pages/intro/how-to-navigate-the-website.mdx
index 91a3bf24..5b4205e2 100644
--- a/docs/pages/intro/how-to-navigate-the-website.mdx
+++ b/docs/pages/intro/how-to-navigate-the-website.mdx
@@ -10,18 +10,18 @@ import { ContributeFooter, TagFilter, TagProvider } from '../../../components'
 # How to Navigate the Website
 
 Navigating the Security Frameworks by SEAL will be designed, in time, to be intuitive and
-user-friendly. We currently allow users to filter contents by role, but we're not quite there yet.
+user-friendly. We currently allow users to filter content by role, but we're not quite there yet.
 Any feedback on how to improve the usage of frameworks in the future is appreciated.
 
 ## Categories
 
 The content is organized into different categories, each focusing on a specific aspect of security.
-Currently, we are under the introduction section, but you can explore the broader category of
+Currently, we are in the Introduction section, but you can explore the broader category of
 "Frameworks" below. Each framework is categorized to help you find relevant information quickly.
 
 ## Filtering by Profile
 
-This is currently being implemented, and we're currently looking for volunteers and collaborators
+This is being implemented, and we're looking for volunteers and collaborators
 for this specific task. The main objective is to allow users to filter the content by profile
 to focus on information relevant to their role within the organization. This feature allows them to
 bypass unnecessary reading and concentrate on what matters most.
diff --git a/docs/pages/monitoring/guidelines.mdx b/docs/pages/monitoring/guidelines.mdx
index 44b29eae..32945934 100644
--- a/docs/pages/monitoring/guidelines.mdx
+++ b/docs/pages/monitoring/guidelines.mdx
@@ -16,7 +16,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Effective on-chain monitoring is complex, and involves setting up systems and processes to continuously observe
+Effective on-chain monitoring is complex and involves setting up systems and processes to continuously observe
 blockchain activities and detect any anomalies.
 
 ## Best Practices
diff --git a/docs/pages/monitoring/thresholds.mdx b/docs/pages/monitoring/thresholds.mdx
index 3a5d5f39..4b7493a7 100644
--- a/docs/pages/monitoring/thresholds.mdx
+++ b/docs/pages/monitoring/thresholds.mdx
@@ -47,11 +47,11 @@ percentages.
 
 ### Anomaly Detection
 
-It is hard, if not impossible, to predict every type of alert one should setup for their project. As such, implementing
+It is hard, if not impossible, to predict every type of alert one should set up for their project. As such, implementing
 an anomaly detection system can be of great value as it will monitor the project and its transactions in real time, and
 compare it to its previous behavior. If for example it is common that 4% of tokens change owner each day and there's a
-day with 20% of tokens changing owner in the past 10 minutes, then that could be detected as an anomaly cause for
-investigation.
+day with 20% of tokens changing owner in the past 10 minutes, then that could be detected as an anomaly and a cause
+for investigation.
 
 ---
 
diff --git a/docs/pages/multisig-for-protocols/backup-signing-and-infrastructure.mdx b/docs/pages/multisig-for-protocols/backup-signing-and-infrastructure.mdx
index 53a9a882..71fdd1bc 100644
--- a/docs/pages/multisig-for-protocols/backup-signing-and-infrastructure.mdx
+++ b/docs/pages/multisig-for-protocols/backup-signing-and-infrastructure.mdx
@@ -39,7 +39,7 @@ signing transactions with your team.
 **Eternal Safe - Decentralized fork of Safe\{Wallet\}**
 
 - GitHub: [https://github.com/eternalsafe/wallet](https://github.com/eternalsafe/wallet)
-- Hosted (IPFS): [https://eternalsafe.eth.limo](https://eternalsafe.eth.limo) (requires bring your own RPC)
+- Hosted (IPFS): [https://eternalsafe.eth.limo](https://eternalsafe.eth.limo) (requires you to bring your own RPC)
 - Local: Can be downloaded and run locally
 
 Note: Local/alternative UIs may not be actively maintained. Treat them as emergency options and perform extra
@@ -117,7 +117,7 @@ accessible during emergencies.
 #### Access Options
 
 - **GitHub**: [https://github.com/eternalsafe/wallet](https://github.com/eternalsafe/wallet)
-- **Hosted (IPFS)**: [https://eternalsafe.eth.limo](https://eternalsafe.eth.limo) (requires bring your own RPC)
+- **Hosted (IPFS)**: [https://eternalsafe.eth.limo](https://eternalsafe.eth.limo) (requires you to bring your own RPC)
 - **Local**: Can be downloaded and run locally
 
 #### Setup
diff --git a/docs/pages/multisig-for-protocols/communication-setup.mdx b/docs/pages/multisig-for-protocols/communication-setup.mdx
index d08d01b2..8ca32119 100644
--- a/docs/pages/multisig-for-protocols/communication-setup.mdx
+++ b/docs/pages/multisig-for-protocols/communication-setup.mdx
@@ -25,7 +25,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 
 ## Primary channel
 
-Set up dedicated communication channel for multisig operations:
+Set up a dedicated communication channel for multisig operations:
 
 - **Platform**: Signal recommended (end-to-end encryption)
 - **Membership**: Multisig signers + authorized management only
@@ -34,7 +34,7 @@ Set up dedicated communication channel for multisig operations:
 
 ## Backup channels
 
-Configure backup communication on different platform:
+Configure backup communication on a different platform:
 
 - **Platform**: Different from primary (if Signal primary, use Telegram/Discord/Slack)
 - **Same membership restrictions** as primary
diff --git a/docs/pages/multisig-for-protocols/joining-a-multisig.mdx b/docs/pages/multisig-for-protocols/joining-a-multisig.mdx
index 3d9d7df8..65788d99 100644
--- a/docs/pages/multisig-for-protocols/joining-a-multisig.mdx
+++ b/docs/pages/multisig-for-protocols/joining-a-multisig.mdx
@@ -32,11 +32,11 @@ multisig signers. Entity affiliations are acceptable - the goal is accountabilit
 ### Preparing and sharing address & Signature
 
 Sign the message like [@social_handle | name | entity] is looking to join [Multisig Name] X DAO multisig with address
-0x... with the private key you intend to use as a signer. One of the options is going using MyCrypto web UI:
+0x... with the private key you intend to use as a signer. One option is to use the MyCrypto web UI:
 
 1. Connect your wallet to [https://app.mycrypto.com/sign-message](https://app.mycrypto.com/sign-message)
 2. Enter the message, click "sign" and sign the message on the wallet.
-3. The sig field in the result json is the signature hash.
+3. The sig field in the result JSON is the signature hash.
 
 Share the message:
 
diff --git a/docs/pages/multisig-for-protocols/personal-security-opsec.mdx b/docs/pages/multisig-for-protocols/personal-security-opsec.mdx
index 9cd4c0a3..dea85d6a 100644
--- a/docs/pages/multisig-for-protocols/personal-security-opsec.mdx
+++ b/docs/pages/multisig-for-protocols/personal-security-opsec.mdx
@@ -60,7 +60,7 @@ linked to it.
 
 - Full disk encryption enabled (FileVault/BitLocker)
 - Automatic updates enabled on all devices
-- Screen lock after 5 minutes inactivity on computers, 30 seconds on mobile
+- Screen lock after 5 minutes of inactivity on computers, 30 seconds on mobile
 - Strong passcodes (6+ digits or alphanumeric on mobile)
 - Endpoint protection software on computers
 - No admin rights for daily use accounts (create separate admin account)
@@ -110,8 +110,8 @@ Use [DeFi DNS Whitelist](https://github.com/0xKoda/defi-dns-whitelist/tree/main)
 
 ### Basic requirements
 
-**Signal with verified safety number verification** for multisig communications: You MUST check the codes with the
-person you are interacting to « verify » them.
+**Signal with verified safety numbers** for multisig communications: You MUST check the codes with the
+person you are interacting with to verify them.
 How? Click on any chat > Contact name > View Safety Number > Call on another communication channel to verify them >
 Click at the bottom "Mark as Verified".
 If the account connects on a new device these codes will change & you will receive a security notification.
diff --git a/docs/pages/multisig-for-protocols/registration-and-documentation.mdx b/docs/pages/multisig-for-protocols/registration-and-documentation.mdx
index 6cbd0167..813006c1 100644
--- a/docs/pages/multisig-for-protocols/registration-and-documentation.mdx
+++ b/docs/pages/multisig-for-protocols/registration-and-documentation.mdx
@@ -27,7 +27,7 @@ and required documentation.
 
 ## Protocol Documentation
 
-Fill out the registration template and send as a PDF to protocol security team. They will create a dedicated section in
+Fill out the registration template and send as a PDF to the protocol security team. They will create a dedicated section in
 protocol docs for your multisig with the registration information.
 
 ## Registration Template
diff --git a/docs/pages/multisig-for-protocols/use-case-specific-requirements.mdx b/docs/pages/multisig-for-protocols/use-case-specific-requirements.mdx
index f9f78d6b..2b728c56 100644
--- a/docs/pages/multisig-for-protocols/use-case-specific-requirements.mdx
+++ b/docs/pages/multisig-for-protocols/use-case-specific-requirements.mdx
@@ -39,7 +39,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 ### Wallet Segregation
 
 - Very high value assets must be distributed amongst separate wallets to prevent potential loss of all assets
-- At least 3 equally funded cold wallets is recommended
+- At least 3 equally funded cold wallets are recommended
 - Segregated wallets should be managed by different multi-sigs
 - Seldom used wallets should have increased time-lock periods
 - Any activity on seldom used wallets should trigger alerts to the entire team
diff --git a/docs/pages/opsec/appendices/case-studies.mdx b/docs/pages/opsec/appendices/case-studies.mdx
index d9849eaa..1c2eaf74 100644
--- a/docs/pages/opsec/appendices/case-studies.mdx
+++ b/docs/pages/opsec/appendices/case-studies.mdx
@@ -4,7 +4,7 @@ description: "Real-world OpSec case studies: private key compromise in DeFi, Dis
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/appendices/glossary.mdx b/docs/pages/opsec/appendices/glossary.mdx
index ed639b6d..525db1a9 100644
--- a/docs/pages/opsec/appendices/glossary.mdx
+++ b/docs/pages/opsec/appendices/glossary.mdx
@@ -4,7 +4,7 @@ description: "Security glossary: definitions for access control, authentication,
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/appendices/overview.mdx b/docs/pages/opsec/appendices/overview.mdx
index 72d09237..95990da8 100644
--- a/docs/pages/opsec/appendices/overview.mdx
+++ b/docs/pages/opsec/appendices/overview.mdx
@@ -4,7 +4,7 @@ description: "OpSec appendices: policy templates, case studies, tabletop exercis
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/appendices/policies.mdx b/docs/pages/opsec/appendices/policies.mdx
index 43cdcb78..af46c187 100644
--- a/docs/pages/opsec/appendices/policies.mdx
+++ b/docs/pages/opsec/appendices/policies.mdx
@@ -4,7 +4,7 @@ description: "Security policy templates: Information Security Policy, Access Con
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
@@ -380,7 +380,7 @@ This procedure outlines the steps for generating and securing cryptographic keys
 - [ ] Physical access controls are in place
 - [ ] Environmental controls are implemented
 - [ ] Equipment is protected from theft or damage
-- [ ] Media is securely handled and disposed
+- [ ] Media is securely handled and disposed of
 - [ ] Physical security incidents are monitored
 
 ## Incident Response
diff --git a/docs/pages/opsec/continuous-improvement-metrics.mdx b/docs/pages/opsec/continuous-improvement-metrics.mdx
index c2213e72..e147e0ca 100644
--- a/docs/pages/opsec/continuous-improvement-metrics.mdx
+++ b/docs/pages/opsec/continuous-improvement-metrics.mdx
@@ -4,7 +4,7 @@ description: "Measure security effectiveness with KPIs: Time to Detect, Time to
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/control-domains/organizational.mdx b/docs/pages/opsec/control-domains/organizational.mdx
index 4cf17512..8b19a001 100644
--- a/docs/pages/opsec/control-domains/organizational.mdx
+++ b/docs/pages/opsec/control-domains/organizational.mdx
@@ -4,7 +4,7 @@ description: "Organizational controls: regulatory compliance, supply chain secur
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/control-domains/overview.mdx b/docs/pages/opsec/control-domains/overview.mdx
index 3523d2bf..d465ca3c 100644
--- a/docs/pages/opsec/control-domains/overview.mdx
+++ b/docs/pages/opsec/control-domains/overview.mdx
@@ -4,7 +4,7 @@ description: "OpSec control domains: organizational policies, people and personn
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/control-domains/people.mdx b/docs/pages/opsec/control-domains/people.mdx
index 6cf2c47e..72f8160f 100644
--- a/docs/pages/opsec/control-domains/people.mdx
+++ b/docs/pages/opsec/control-domains/people.mdx
@@ -4,7 +4,7 @@ description: "People controls: defend against social engineering, mitigate insid
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/control-domains/physical-environmental.mdx b/docs/pages/opsec/control-domains/physical-environmental.mdx
index ea6bc9e5..9be335e6 100644
--- a/docs/pages/opsec/control-domains/physical-environmental.mdx
+++ b/docs/pages/opsec/control-domains/physical-environmental.mdx
@@ -4,7 +4,7 @@ description: "Physical security controls: secure workspaces, travel security, ta
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 
 ---
diff --git a/docs/pages/opsec/control-domains/technical.mdx b/docs/pages/opsec/control-domains/technical.mdx
index 9489b631..9d5ce1ef 100644
--- a/docs/pages/opsec/control-domains/technical.mdx
+++ b/docs/pages/opsec/control-domains/technical.mdx
@@ -4,7 +4,7 @@ description: "Technical controls: device hardening, network security, encrypted
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/google/overview.mdx b/docs/pages/opsec/google/overview.mdx
index 457863be..2ce9f388 100644
--- a/docs/pages/opsec/google/overview.mdx
+++ b/docs/pages/opsec/google/overview.mdx
@@ -60,8 +60,9 @@ These settings apply to your personal Google account. All team members and admin
   - [ ]  Security > Enhanced Safe Browsing > **Enabled**
 - [2-Step Verification](https://myaccount.google.com/signinoptions/two-step-verification):
   - Properly setting up two-factor authentication (2FA) is one of the most crucial steps you can take. Disable SMS 2FA
-  to avoid SIM swaps, and instead use an authenticator app or a hardware security key (preferred).
-  - [ ]  Enable any, but passkeys or authenticator recommended. You can also continue using **Google prompts**.
+    to avoid SIM swaps, and instead use an authenticator app or a hardware security key (preferred).
+  - [ ]  Enable any available method, but passkeys or an authenticator app are recommended. You can also continue
+    using **Google prompts**.
   - [ ]  Disable "Voice or text message" if enabled
   - [ ]  Remove any App passwords
   - [ ]  Store Backup Codes offline in a secure place
@@ -104,10 +105,10 @@ recovery more challenging.
 ### Best Practices & Ongoing Maintenance
 
 - [ ]  **Review Security Alerts:** Pay attention to any email or phone notifications from Google regarding unusual
-sign-ins or account changes.
+  sign-ins or account changes.
 - [ ]  **Perform a Security Checkup:** Regularly visit [Google's Security Checkup](https://myaccount.google.com/security-checkup)
-to identify potential issues and resolve them.
-- [ ]  **Consider** using identity **monitoring** apps like [Push Security](pushsecurity.com).
+  to identify potential issues and resolve them.
+- [ ]  **Consider** using identity **monitoring** apps like [Push Security](https://pushsecurity.com).
 
 ---
 
@@ -183,8 +184,8 @@ These settings and practices apply to Google Workspace administrators with eleva
 
 - **SPF & DMARC**
   - Follow these guides to confirm and/or set up SPF and DMARC:
-    - [https://support.google.com/a/answer/33786?hl=en&sjid=5876544508252018851-NC#spf-already-setup](https://support.google.com/a/answer/33786?hl=en&sjid=5876544508252018851-NC#spf-already-setup)
-    - [https://support.google.com/a/answer/2466580?hl=en#dmarc-step2](https://support.google.com/a/answer/2466580?hl=en#dmarc-step2)
+    - [Set up SPF](https://support.google.com/a/answer/33786?hl=en&sjid=5876544508252018851-NC#spf-already-setup)
+    - [Set up DMARC](https://support.google.com/a/answer/2466580?hl=en#dmarc-step2)
 
 #### Optional Enhancement
 
diff --git a/docs/pages/opsec/integration/overview.mdx b/docs/pages/opsec/integration/overview.mdx
index 6d734923..5fce2a76 100644
--- a/docs/pages/opsec/integration/overview.mdx
+++ b/docs/pages/opsec/integration/overview.mdx
@@ -4,7 +4,7 @@ description: "Integrate OpSec with DevSecOps, privacy frameworks, and governance
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/cloud-third-party/g-suite-security.mdx b/docs/pages/opsec/old/cloud-third-party/g-suite-security.mdx
index 88123758..a8a59cb8 100644
--- a/docs/pages/opsec/old/cloud-third-party/g-suite-security.mdx
+++ b/docs/pages/opsec/old/cloud-third-party/g-suite-security.mdx
@@ -3,7 +3,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - HR
 ---
 
diff --git a/docs/pages/opsec/old/cloud-third-party/overview.mdx b/docs/pages/opsec/old/cloud-third-party/overview.mdx
index 7a6d7575..f71b23f8 100644
--- a/docs/pages/opsec/old/cloud-third-party/overview.mdx
+++ b/docs/pages/opsec/old/cloud-third-party/overview.mdx
@@ -2,7 +2,7 @@
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/core-opsec-principles.mdx b/docs/pages/opsec/old/core-opsec-principles.mdx
index 90e0deac..f7182d12 100644
--- a/docs/pages/opsec/old/core-opsec-principles.mdx
+++ b/docs/pages/opsec/old/core-opsec-principles.mdx
@@ -2,7 +2,7 @@
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
@@ -33,7 +33,7 @@ organization's assets, operations, and reputation.
 > members with no single person having access to all keys, and sensitive incident response procedures are only shared
 > with the security team
 > - **Regular threat assessment**: The team conducts quarterly reviews of potential attack vectors, from smart contract
-> vulnerabilities to [social engineering] {/* TODO: link not found: ../awareness/social-engineering.md */} attempts
+> vulnerabilities to social engineering attempts
 > targeting team members
 
 ## Defense in Depth
diff --git a/docs/pages/opsec/old/data-protection/overview.mdx b/docs/pages/opsec/old/data-protection/overview.mdx
index 2fd7a3f8..662db3f8 100644
--- a/docs/pages/opsec/old/data-protection/overview.mdx
+++ b/docs/pages/opsec/old/data-protection/overview.mdx
@@ -2,7 +2,7 @@
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
   - Compliance
 ---
diff --git a/docs/pages/opsec/old/device-endpoint-security/overview.mdx b/docs/pages/opsec/old/device-endpoint-security/overview.mdx
index d408b8f3..23a2d7cf 100644
--- a/docs/pages/opsec/old/device-endpoint-security/overview.mdx
+++ b/docs/pages/opsec/old/device-endpoint-security/overview.mdx
@@ -2,7 +2,7 @@
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/device-endpoint-security/standard-operating-environment.mdx b/docs/pages/opsec/old/device-endpoint-security/standard-operating-environment.mdx
index 4ca80e80..9c104cb0 100644
--- a/docs/pages/opsec/old/device-endpoint-security/standard-operating-environment.mdx
+++ b/docs/pages/opsec/old/device-endpoint-security/standard-operating-environment.mdx
@@ -2,7 +2,7 @@
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/governance-program-management.mdx b/docs/pages/opsec/old/governance-program-management.mdx
index 59930c3d..837a9e9e 100644
--- a/docs/pages/opsec/old/governance-program-management.mdx
+++ b/docs/pages/opsec/old/governance-program-management.mdx
@@ -4,7 +4,7 @@ description: "Establish OpSec governance: define security policies, assign roles
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/incident-response-recovery.mdx b/docs/pages/opsec/old/incident-response-recovery.mdx
index 4fa9c25e..977c6a27 100644
--- a/docs/pages/opsec/old/incident-response-recovery.mdx
+++ b/docs/pages/opsec/old/incident-response-recovery.mdx
@@ -4,7 +4,7 @@ description: "Respond to device loss, account compromise, malware infections, pr
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
@@ -138,7 +138,7 @@ Removing the cause of the incident.
 1. **Root Cause Identification**: Determining how the incident occurred
 2. **Threat Removal**: Eliminating malware, vulnerabilities, or other causes
 3. **Verification**: Ensuring the threat has been completely removed
-4. **Enhanced Monitoring**: Implementing additional monitoring to detect reoccurrence
+4. **Enhanced Monitoring**: Implementing additional monitoring to detect recurrence
 
 ### Recovery
 
diff --git a/docs/pages/opsec/old/lifecycle/overview.mdx b/docs/pages/opsec/old/lifecycle/overview.mdx
index bb669fd6..71f82b80 100644
--- a/docs/pages/opsec/old/lifecycle/overview.mdx
+++ b/docs/pages/opsec/old/lifecycle/overview.mdx
@@ -4,7 +4,7 @@ description: "OpSec lifecycle: identify assets, model threats, assess vulnerabil
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/monitoring-detection.mdx b/docs/pages/opsec/old/monitoring-detection.mdx
index 16a1cb4f..70e8d313 100644
--- a/docs/pages/opsec/old/monitoring-detection.mdx
+++ b/docs/pages/opsec/old/monitoring-detection.mdx
@@ -4,7 +4,7 @@ description: "Implement security monitoring: centralized logging, SIEM systems,
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/network-communication/overview.mdx b/docs/pages/opsec/old/network-communication/overview.mdx
index 31929718..cc41adc6 100644
--- a/docs/pages/opsec/old/network-communication/overview.mdx
+++ b/docs/pages/opsec/old/network-communication/overview.mdx
@@ -2,7 +2,7 @@
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/network-communication/wireless-security.mdx b/docs/pages/opsec/old/network-communication/wireless-security.mdx
index f56528ec..c5e97593 100644
--- a/docs/pages/opsec/old/network-communication/wireless-security.mdx
+++ b/docs/pages/opsec/old/network-communication/wireless-security.mdx
@@ -33,7 +33,7 @@ and limit access to sensitive resources.
 1. Use strong, unique passwords for network access. Never use default passwords provided by the manufacturer.
 2. Consider implementing MAC address filtering to restrict network access to authorized devices only. Regularly update
 the list of allowed devices.
-3. Considering using enterprise-grade authentication methods, such as 802.1X with RADIUS, to authenticate users before
+3. Consider using enterprise-grade authentication methods, such as 802.1X with RADIUS, to authenticate users before
 granting network access.
 
 ### Monitoring and Intrusion Detection
diff --git a/docs/pages/opsec/old/overview.mdx b/docs/pages/opsec/old/overview.mdx
index ad124b8e..492974cb 100644
--- a/docs/pages/opsec/old/overview.mdx
+++ b/docs/pages/opsec/old/overview.mdx
@@ -2,7 +2,7 @@
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/opsec/old/risk-management-overview.mdx b/docs/pages/opsec/old/risk-management-overview.mdx
index 6bbc1662..e5dc0c70 100644
--- a/docs/pages/opsec/old/risk-management-overview.mdx
+++ b/docs/pages/opsec/old/risk-management-overview.mdx
@@ -4,7 +4,7 @@ description: "Prioritize security risks using NIST, ISO 31000, and FAIR framewor
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/opsec/old/risk-management/overview.mdx b/docs/pages/opsec/old/risk-management/overview.mdx
index 95338e97..88a3e499 100644
--- a/docs/pages/opsec/old/risk-management/overview.mdx
+++ b/docs/pages/opsec/old/risk-management/overview.mdx
@@ -4,7 +4,7 @@ description: "OpSec risk management: impact analysis, likelihood scoring, risk c
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/opsec/overview.mdx b/docs/pages/opsec/overview.mdx
index 0822c5ba..9d4c925b 100644
--- a/docs/pages/opsec/overview.mdx
+++ b/docs/pages/opsec/overview.mdx
@@ -4,7 +4,7 @@ description: "Operational Security Framework: Comprehensive OpSec for Web2 and W
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/opsec/principles/five-steps.mdx b/docs/pages/opsec/principles/five-steps.mdx
index 1c09867e..4f391e8a 100644
--- a/docs/pages/opsec/principles/five-steps.mdx
+++ b/docs/pages/opsec/principles/five-steps.mdx
@@ -65,9 +65,7 @@ Identify potential adversaries, their capabilities, and their interest in your c
 Analyze how your critical information might be exposed through vulnerabilities in your systems, processes, or personnel.
 
 > **🔗 Related Framework:** This connects with [Security Testing](/security-testing/overview) framework, including
-> [Static Application Security Testing]
-{/*TODO: link not found:/security-testing/static-application-security-testing*/} [Dynamic Application Security Testing]
-{/*TODO: link not found:../security-testing/dynamic-application-security-testing.md*/}, and vulnerability management practices.
+> Static Application Security Testing and Dynamic Application Security Testing, and vulnerability management practices.
 
 ### Implementation
 
diff --git a/docs/pages/opsec/principles/overview.mdx b/docs/pages/opsec/principles/overview.mdx
index 4ac6fe71..5748c1d5 100644
--- a/docs/pages/opsec/principles/overview.mdx
+++ b/docs/pages/opsec/principles/overview.mdx
@@ -4,7 +4,7 @@ description: "OpSec principles: defense in depth, least privilege, need-to-know
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/opsec/principles/principles.mdx b/docs/pages/opsec/principles/principles.mdx
index 22a63c57..750b699d 100644
--- a/docs/pages/opsec/principles/principles.mdx
+++ b/docs/pages/opsec/principles/principles.mdx
@@ -4,7 +4,7 @@ description: "Five core OpSec principles: defense in depth with layered security
 tags:
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/opsec/principles/web3-considerations.mdx b/docs/pages/opsec/principles/web3-considerations.mdx
index 768707f4..b8eb6a65 100644
--- a/docs/pages/opsec/principles/web3-considerations.mdx
+++ b/docs/pages/opsec/principles/web3-considerations.mdx
@@ -28,7 +28,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 > mitigate smart contract vulnerabilities, and navigate community-driven security challenges.
 
 In addition to traditional OpSec principles, Web3 environments require consideration of unique challenges. Many
-organizations claim to be backed only by descentralized technologies, but they later realize that part of their process
+organizations claim to be backed only by decentralized technologies, but they later realize that part of their process
 is dependant on technologies that are not.
 
 {/* > **🔗 Related Framework:** Explore the dedicated [Web3-Specific
diff --git a/docs/pages/opsec/travel/guide.mdx b/docs/pages/opsec/travel/guide.mdx
index 09f6a896..d4daf13b 100644
--- a/docs/pages/opsec/travel/guide.mdx
+++ b/docs/pages/opsec/travel/guide.mdx
@@ -6,7 +6,7 @@ tags:
   - Operations & Strategy
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
@@ -55,7 +55,7 @@ you have a backup of the data you’ll be traveling with, even letting know some
 emergency and how to identify you. This does not necessarily mean that if you’re reading this while traveling you cannot
 do anything from that list, only that it might be more challenging to execute depending on your context.
 2. **While traveling:** All the things you have to pay attention to or take care of while on the move. Is it necessary
-to connect to that conference’s WiFi? Have you checked if there is a camera that might be recording your keystrokes?
+to connect to that conference’s Wi-Fi? Have you checked if there is a camera that might be recording your keystrokes?
 Leaving your computer unattended or just running whatever software your hackathon teammate asks you to download in order
 for your promising project to win.
 3. **Returning home:** Not in the literal sense of it, but directed toward all the things you have to do after your
@@ -79,7 +79,7 @@ Even if you are already traveling, take 5 minutes to map out your risks. Identif
 (laptops, phones, hardware wallets, seed phrases, account access), **who might target them** (thieves, cybercriminals,
 border agents, etc.), and **how attacks might happen** (device theft, tampering, malware, coercion). For each threat,
 plan a mitigation. For example, if you're carrying a hardware wallet, a threat is pickpocketing – mitigation could be
-keeping it attached to yourself (just don't use ledger's necklace visibly) and securing it with a secure PIN/passphrase
+keeping it attached to yourself (just don't use Ledger's necklace visibly) and securing it with a secure PIN/passphrase
 (no patterns, not repeated across devices).
 
 This exercise keeps security measures proportionate to your situation.
@@ -87,7 +87,7 @@ This exercise keeps security measures proportionate to your situation.
 ### **Secure devices with encryption & updates**
 
 Enable full-disk encryption on all devices (laptops, phones, tablets) to protect data if lost or stolen. Most modern
-OSes have this by default (e.g. BitLocker for Windows, FileVault for MacOS, LUKS for Linux,or Android/iOS encryption –
+OSes have this by default (e.g. BitLocker for Windows, FileVault for MacOS, LUKS for Linux, or Android/iOS encryption –
 just ensure a strong password/PIN is set).
 
 Use popular devices like iPhones and Pixels. Install the latest OS and app updates since these patch security
@@ -284,7 +284,7 @@ Avoid plug-and-play charging stations at airports or malls. The risk of
 ["**juice jacking**"](https://www.cypherock.com/blogs/post-safe-vacation-tips-while-traveling-with-crypto?srsltid=AfmBOopuzAsUtNwqCqfUBteTEyH4MOTvIaRhoXoIUyNHH8Yv5XzILrSr#:~:text=Stay%20away%20from%20Public%20charger,stations),
 although small,
 is that a malicious charging kiosk or cable can inject malware or siphon data when you connect via USB. Depending on
-your profile risk, you might encounter technologies that mimic different kind of cables and accessories with the same
+your profile risk, you might encounter technologies that mimic different kinds of cables and accessories with the same
 purpose. These exist out of the box, and have been widely used by red-teamers and pentesters (re OMG cable).
 
 Stick to using your own charger plugged into a power outlet, or use a **USB data blocker** (a little adapter that
diff --git a/docs/pages/opsec/travel/overview.mdx b/docs/pages/opsec/travel/overview.mdx
index 11e19af5..61ceaaf7 100644
--- a/docs/pages/opsec/travel/overview.mdx
+++ b/docs/pages/opsec/travel/overview.mdx
@@ -6,7 +6,7 @@ tags:
   - Operations & Strategy
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/opsec/travel/tldr.mdx b/docs/pages/opsec/travel/tldr.mdx
index cf4cdff9..ada62c38 100644
--- a/docs/pages/opsec/travel/tldr.mdx
+++ b/docs/pages/opsec/travel/tldr.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Travel Security Quick Reference | Security Alliance"
-description: "Quick travel security checklist: full-disk encryption, backup 2FA codes, secure hardware wallets, avoid public WiFi, use VPNs, disable biometrics at borders, and scan devices upon return."
+description: "Quick travel security checklist: full-disk encryption, backup 2FA codes, secure hardware wallets, avoid public Wi-Fi, use VPNs, disable biometrics at borders, and scan devices upon return."
 tags:
   - Security Specialist
   - Operations & Strategy
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/privacy/financial-privacy-services.mdx b/docs/pages/privacy/financial-privacy-services.mdx
index 875b439b..0418066e 100644
--- a/docs/pages/privacy/financial-privacy-services.mdx
+++ b/docs/pages/privacy/financial-privacy-services.mdx
@@ -16,7 +16,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Maintaining financial privacy is often seen by an important thing for people inside the web3 ecosystem, and it can help
+Maintaining financial privacy is often seen as important for people in the Web3 ecosystem, and it can help
 prevent personal and financial information from unauthorized access and fraud.
 
 ## Tools for Financial Privacy
diff --git a/docs/pages/privacy/overview.mdx b/docs/pages/privacy/overview.mdx
index 9b7ed054..2b600ec5 100644
--- a/docs/pages/privacy/overview.mdx
+++ b/docs/pages/privacy/overview.mdx
@@ -4,7 +4,7 @@ description: "Privacy Framework: Protect personal and team information from unau
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -17,7 +17,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Privacy is a fundamental aspect of security. Protecting your personal and team's information from unauthorized access
+Privacy is a fundamental aspect of security. Protecting your personal information and your team's information from unauthorized access
 and exposure is crucial. This section provides guidelines and resources for maintaining privacy, managing your digital
 footprint, and utilizing privacy-focused tools and services.
 
diff --git a/docs/pages/privacy/secure-browsing.mdx b/docs/pages/privacy/secure-browsing.mdx
index 5f0385ed..9af81010 100644
--- a/docs/pages/privacy/secure-browsing.mdx
+++ b/docs/pages/privacy/secure-browsing.mdx
@@ -23,8 +23,8 @@ Secure browsing is essential to protect your privacy and personal information wh
 1. **Use HTTPS**
    - Always use HTTPS to ensure that your connection to websites is encrypted. Look for the padlock icon in the browser
    address bar.
-   - Most browser now enforce HTTPS by default, otherwise use browser extensions like HTTPS Everywhere to enforce HTTPS
-   connections.
+   - Most browsers now enforce HTTPS by default. Otherwise, use browser extensions like HTTPS Everywhere to enforce
+     HTTPS connections.
 
 2. **Avoid Public Wi-Fi**
    - Avoid using public Wi-Fi for sensitive activities. If you must use it, ensure you connect through a VPN to encrypt
diff --git a/docs/pages/privacy/vpn-services.mdx b/docs/pages/privacy/vpn-services.mdx
index 22fbdfb1..0f4c3905 100644
--- a/docs/pages/privacy/vpn-services.mdx
+++ b/docs/pages/privacy/vpn-services.mdx
@@ -17,7 +17,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Virtual Private Networks (VPNs) can help increase online privacy. They encrypt your internet traffic and hide your IP
-address, increases the protection of your data from eavesdroppers and provide you additional anonymity online.
+address, increasing the protection of your data from eavesdroppers and providing additional anonymity online.
 
 ## Choosing a VPN Service
 
diff --git a/docs/pages/safe-harbor/on-chain-adoption-guide.mdx b/docs/pages/safe-harbor/on-chain-adoption-guide.mdx
index d8049034..2c4c85d6 100644
--- a/docs/pages/safe-harbor/on-chain-adoption-guide.mdx
+++ b/docs/pages/safe-harbor/on-chain-adoption-guide.mdx
@@ -111,7 +111,7 @@ your own.
 **Manual Method:**
 
 1. Create your agreement: Call
-`AgreementFactory.create(AgreementDetails memory details, address chainValidator, address owner, bytes32 salt)`
+   `AgreementFactory.create(AgreementDetails memory details, address chainValidator, address owner, bytes32 salt)`
 2. Register it: Call `SafeHarborRegistry.adoptSafeHarbor(address agreementAddress)`
 
 ## V3 Contract Addresses
@@ -126,12 +126,11 @@ supported EVM chains.
 | **AgreementFactory** | `0xcf317fE605397bC3fae6DAD06331aE5154F277fF` | Factory for creating Agreement contracts |
 
 > **Note:** These addresses are the same on all supported EVM chains due to CREATE3 deployment.
-
-{/* separator */}
-
-> **Note:** The V3 contracts have been audited by [Cyfrin](https://www.cyfrin.io/). The smart contracts are bytecode
-> equivalent to the [hash](https://github.com/security-alliance/safe-harbor/tree/0b0abb8b627eff87e2f7b52bf8ec484cd6ce0e32)
-> of the audit. The audit can be found [at this link](https://github.com/security-alliance/safe-harbor/blob/main/documents/2026-01-13-cyfrin-safe-harbor-v2.0.pdf)
+> The V3 contracts have been audited by [Cyfrin](https://www.cyfrin.io/).
+> The smart contracts are bytecode equivalent to the
+> [audited hash](https://github.com/security-alliance/safe-harbor/tree/0b0abb8b627eff87e2f7b52bf8ec484cd6ce0e32).
+> The audit report is available in the
+> [Cyfrin audit PDF](https://github.com/security-alliance/safe-harbor/blob/main/documents/2026-01-13-cyfrin-safe-harbor-v2.0.pdf).
 
 ---
 
diff --git a/docs/pages/safe-harbor/overview.mdx b/docs/pages/safe-harbor/overview.mdx
index 123ce54d..9b11946e 100644
--- a/docs/pages/safe-harbor/overview.mdx
+++ b/docs/pages/safe-harbor/overview.mdx
@@ -76,7 +76,7 @@ By adopting Safe Harbor, protocols allow:
 
 ## Who's Adopted Safe Harbor
 
-> Safe Harbor is already protecting $68B+ in assets across leading DeFi protocols. Has been adopted by 20+ protocols.
+> Safe Harbor is already protecting $68B+ in assets across leading DeFi protocols. It has been adopted by 20+ protocols.
 > Current adopters include Uniswap, Aave, Pendle, PancakeSwap, Balancer, Silo Finance, Zksync, and more. See the
 > [full up-to-date list](https://safeharbor.securityalliance.org/).
 
@@ -167,7 +167,7 @@ recover funds in real time.
 <details>
 <summary>What are the risks?</summary>
 
-There is little to no risk. The status quo is the protocol is hacked and the hacker gets 100% of funds. But with Safe
+There is little to no risk. The status quo is that the protocol is hacked and the hacker gets 100% of the funds. But with Safe
 Harbor, we unlock the upside of whitehats stepping in and rescuing funds. So the worst case scenario is the status quo,
 while the best case scenario is all funds are rescued by the protocol.
 
diff --git a/docs/pages/safe-harbor/scope-terms.mdx b/docs/pages/safe-harbor/scope-terms.mdx
index 7e02d31e..c6f984f4 100644
--- a/docs/pages/safe-harbor/scope-terms.mdx
+++ b/docs/pages/safe-harbor/scope-terms.mdx
@@ -79,7 +79,7 @@ Defines how whitehats are rewarded for successful intervention.
 
 ### 4.1 Bounty Calculation
 
-As a FYI, the formula to determine the bounty payout to the whitehats is:
+FYI,, the formula to determine the bounty payout to the whitehats is:
 
 `bounty = min(bountyPercentage × recoveredAmount, bountyCapUSD)`
 
diff --git a/docs/pages/safe-harbor/self-adoption-guide.mdx b/docs/pages/safe-harbor/self-adoption-guide.mdx
index 989bdecf..2f092b4a 100644
--- a/docs/pages/safe-harbor/self-adoption-guide.mdx
+++ b/docs/pages/safe-harbor/self-adoption-guide.mdx
@@ -92,7 +92,7 @@ Add the following language to your TOS:
 > - the User acknowledges and agrees that Tokens may be lost, stolen, suffer diminished value, or become disabled or
 > frozen in connection with attempts at Eligible Funds Rescues, and assumes all the risk of the foregoing;
 > - the User acknowledges and agrees that payment of the Bounty as a deduction from User's Tokens to an Eligible
-> Whitehat may constitute a taxable disposition by the User of the deducted Tokens, and agrees to assume to all risk of
+> Whitehat may constitute a taxable disposition by the User of the deducted Tokens, and agrees to assume all risk of
 > such adverse tax treatment; and
 > - the User agrees to hold the other Protocol Community Members harmless from any loss, liability or other damages
 > suffered by the User in connection with attempted Eligible Funds Exploits under the Whitehat Agreement.
diff --git a/docs/pages/safe-harbor/whitehat.mdx b/docs/pages/safe-harbor/whitehat.mdx
index e811da2f..bc685588 100644
--- a/docs/pages/safe-harbor/whitehat.mdx
+++ b/docs/pages/safe-harbor/whitehat.mdx
@@ -22,7 +22,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 ## Why You Should Care
 
 {/* TODO: link not found (./key-terms.md#active-exploit)*/}
-Safe Harbor lets whitehats intervene during [active exploits] to help secure protocol funds. It does so by providing a
+Safe Harbor lets whitehats intervene during active exploits to help secure protocol funds. It does so by providing a
 legal framework that outlines what whitehats can and can't do, how they ought to operate, and protects abiding
 whitehats in the event of legal action taken by the protocol.
 
@@ -30,17 +30,17 @@ In addition to the legal protections, Safe Harbor also helps whitehats by giving
 
 1. What assets are owned by a protocol
 {/*TODO: link not found (./key-terms.md#asset-recovery-address)*/}
-2. What is the protocol's ([asset recovery address])
+2. What the protocol's asset recovery address is
 {/* TODO: (../security-contact.md) is this link this: /vulnerability-disclosure/security-contact ? */}
-3. Who the [security contact]
+3. Who the security contact is
 4. What KYC requirements (if any) protocols impose onto whitehats
 5. What bounty terms whitehats will be awarded under Safe Harbor
 
-This information is all neatly cataloged in the [Safe Harbor Registry]
+This information is all neatly cataloged in the Safe Harbor Registry
 {/*TODO: link not found (./key-terms.md#safe-harbor-registry)*/} - an on-chain registry cataloging all protocol
-adoptions and their adoption details. For more details, review the [Safe Harbor for Protocols]
+adoptions and their adoption details. For more details, review the Safe Harbor for Protocols
 {/*TODO: link not found (./protocol.md)*/} document.
-It has also been compiled by Skylock at the [Safe Harbor Database](skylock.xyz/safeharbor/database).
+It has also been compiled by Skylock at the [Safe Harbor Database](https://skylock.xyz/safeharbor/database).
 
 ## Whitehat Adoption
 
@@ -59,8 +59,7 @@ This includes transferring rescued funds to the protocol's "Asset Recovery Addre
 of the fund recovery. The whitehat may keep (or later receive) a reward, based on the terms of the agreement.
 
 Safe Harbor may also apply to generalized frontrunner / arbitrage bots. The rules of conduct enforced by Safe Harbor for
-[Prospective and Retrospective] {/*TODO: link not found (./key-terms.md#prospective--retrospective-whitehats)*/}
-whitehats differs in a few key areas.
+Prospective and Retrospective whitehats differ in a few key areas.
 
 ## In the Event of a Hack
 
@@ -84,18 +83,18 @@ in said rescue, free from OFAC sanctions and/or other connections to sanctioned
 - Are you fully aware of the risks associated with your actions, including but not limited to accidental loss of funds,
 claims and liabilities outside this agreement's scope, and the unclear extent of this agreement's enforceability?
 
-In the event that all the above applies, you may chose to take action to protect the protocol's assets. How you do this
+In the event that all the above applies, you may choose to take action to protect the protocol's assets. How you do this
 depends on the situation - perhaps offensively white-hat hacking a protocol with a proven exploit, or returning funds
-recovered by your MEV bot from an incident it frontran.
+recovered by your MEV bot from an incident it front-ran.
 
 ### Post-Intervention
 
 After the funds have been recovered, it is your responsibility to ensure their safe return to the owner protocol. We
-strongly recommend contacting [SEAL911](incident-management/seal-911-war-room-guidelines) immediately to advise on the
+strongly recommend contacting [SEAL911](/incident-management/playbooks/seal-911-war-room-guidelines) immediately to
+advise on the
 fund recovery process and to assist with KYC, protocol communications, and bounty collection. You must also contact the
-protocol's posted security contact and return all recovered funds to the protocol's [asset recovery address]
-{/*TODO: link not found (./key-terms.md#asset-recovery-address)*/} within 6 hours of the event, or 48 hours if
-reason is provided and the protocol has been made aware.
+protocol's posted security contact and return all recovered funds to the protocol's asset recovery address within 6
+hours of the event, or 48 hours if reason is provided and the protocol has been made aware.
 
 ---
 
diff --git a/docs/pages/secure-software-development/overview.mdx b/docs/pages/secure-software-development/overview.mdx
index 5ce7c588..2075e214 100644
--- a/docs/pages/secure-software-development/overview.mdx
+++ b/docs/pages/secure-software-development/overview.mdx
@@ -4,7 +4,7 @@ description: "Secure Software Development Framework: Integrate security througho
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
diff --git a/docs/pages/secure-software-development/secure-code-repositories-version-control.mdx b/docs/pages/secure-software-development/secure-code-repositories-version-control.mdx
index 783e5cc5..094ea767 100644
--- a/docs/pages/secure-software-development/secure-code-repositories-version-control.mdx
+++ b/docs/pages/secure-software-development/secure-code-repositories-version-control.mdx
@@ -4,7 +4,7 @@ description: "Secure code repositories: implement RBAC access controls, require
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
diff --git a/docs/pages/security-automation/compliance-checks.mdx b/docs/pages/security-automation/compliance-checks.mdx
index b1d857b8..6ea35cac 100644
--- a/docs/pages/security-automation/compliance-checks.mdx
+++ b/docs/pages/security-automation/compliance-checks.mdx
@@ -4,7 +4,7 @@ description: "Automate compliance monitoring with AWS Config, Azure Policy, Hash
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
@@ -47,7 +47,7 @@ compliance status of systems and applications.
 
 2. **Azure Policy**
    - A service that enables the creation, assignment, and management of policies to enforce organizational standards and
-   assess compliance at-scale.
+   assess compliance at scale.
    - Pros: Integrated with Azure services, supports custom policies.
    - Cons: Limited to Azure environments.
 
diff --git a/docs/pages/security-automation/infrastructure-as-code.mdx b/docs/pages/security-automation/infrastructure-as-code.mdx
index 06100387..c7ad13e9 100644
--- a/docs/pages/security-automation/infrastructure-as-code.mdx
+++ b/docs/pages/security-automation/infrastructure-as-code.mdx
@@ -4,7 +4,7 @@ description: "Secure your Infrastructure as Code (IaC) with Terraform, AWS Cloud
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
@@ -19,8 +19,8 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Infrastructure as Code (IaC) is the managing and provisioning computing infrastructure through machine-readable
-definition files, rather than manual  configuration or interactive configuration tools. Automating security within IaC
+Infrastructure as Code (IaC) is the management and provisioning of computing infrastructure through machine-readable
+definition files, rather than manual configuration or interactive configuration tools. Automating security within IaC
 helps ensure that infrastructure is configured securely and consistently.
 
 ## Benefits of Automating Security in IaC
diff --git a/docs/pages/security-automation/overview.mdx b/docs/pages/security-automation/overview.mdx
index a13452af..0445512b 100644
--- a/docs/pages/security-automation/overview.mdx
+++ b/docs/pages/security-automation/overview.mdx
@@ -4,7 +4,7 @@ description: "Security Automation Framework: Automate compliance checks, IaC sec
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - Cloud
   - SRE
 ---
diff --git a/docs/pages/security-automation/threat-detection-response.mdx b/docs/pages/security-automation/threat-detection-response.mdx
index 588c995f..40b1aa17 100644
--- a/docs/pages/security-automation/threat-detection-response.mdx
+++ b/docs/pages/security-automation/threat-detection-response.mdx
@@ -4,7 +4,7 @@ description: "Implement continuous threat detection and response using SIEM syst
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
   - SRE
 ---
 
diff --git a/docs/pages/security-testing/formal-verification.mdx b/docs/pages/security-testing/formal-verification.mdx
index e5aa2156..765ba8e8 100644
--- a/docs/pages/security-testing/formal-verification.mdx
+++ b/docs/pages/security-testing/formal-verification.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/security-testing/fuzz-testing.mdx b/docs/pages/security-testing/fuzz-testing.mdx
index 747a2816..2885dc83 100644
--- a/docs/pages/security-testing/fuzz-testing.mdx
+++ b/docs/pages/security-testing/fuzz-testing.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
@@ -23,7 +23,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Fuzz testing (or fuzzing) is when you supply random data to your system in an attempt to break it. Most of the time,
-hacks come from scenarios you didn't think about and write a test for. What if I told you that you could write one test
+hacks come from scenarios you didn't think about or write a test for. What if I told you that you could write one test
 that would check for almost every possible scenario?
 
 ## What is Fuzz Testing?
diff --git a/docs/pages/security-testing/integration-testing.mdx b/docs/pages/security-testing/integration-testing.mdx
index d6a0b3ba..2eea04d0 100644
--- a/docs/pages/security-testing/integration-testing.mdx
+++ b/docs/pages/security-testing/integration-testing.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
@@ -24,8 +24,8 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 
 While unit tests verify individual functions work in isolation (often with mocked dependencies), integration tests
 verify that your smart contracts work correctly with real external systems. In Web3, this primarily means testing with
-**fork tests** - running your contracts against real blockchain state. With out unit tests, we `mocked` working with
-external systems, integration tests however will actually work with those systems, by running as:
+**fork tests** - running your contracts against real blockchain state. In unit tests, we `mock` interactions with
+external systems; integration tests, however, actually work with those systems by running as:
 
 - Fork tests
 - Testnet Tests
diff --git a/docs/pages/security-testing/mutation-testing.mdx b/docs/pages/security-testing/mutation-testing.mdx
index 0da7ef61..b88452d8 100644
--- a/docs/pages/security-testing/mutation-testing.mdx
+++ b/docs/pages/security-testing/mutation-testing.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
@@ -137,7 +137,7 @@ before attempting mutation testing.
 ### 2. Achieving a 100% mutation score might not be feasible
 
 A 100% mutation score indicates that no mutants have survived the test. Fundamentally, it is the end goal, but can be
-sometimes infesable and unnecessary, especially as the codebase grows in size. Instead 100% should be strived for, and
+sometimes infeasible and unnecessary, especially as the codebase grows in size. Instead, 100% should be the target, and
 every survived mutant carefully examined to see if that mutation makes sense and if the test should cover it.
 
 ### 3. Consider using only a subset of the mutators available
diff --git a/docs/pages/security-testing/overview.mdx b/docs/pages/security-testing/overview.mdx
index 4b9234bc..1de3070b 100644
--- a/docs/pages/security-testing/overview.mdx
+++ b/docs/pages/security-testing/overview.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/security-testing/static-analysis.mdx b/docs/pages/security-testing/static-analysis.mdx
index 11507eae..d7706c3f 100644
--- a/docs/pages/security-testing/static-analysis.mdx
+++ b/docs/pages/security-testing/static-analysis.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
@@ -27,7 +27,7 @@ are many forms of static analysis, and compilers like solc rely on these techniq
 analysis can help identify potential vulnerabilities and code quality issues.
 
 Some static analysis tools are helpful for finding bugs too. Unlike dynamic testing (unit tests, fuzz tests, integration
-tests), these bug-finding-focused static analysis examines your code's structure, syntax, and patterns to identify
+tests), these bug-finding-focused static analysis tools examine your code's structure, syntax, and patterns to identify
 potential vulnerabilities and code quality issues. You can think of these static analysis as being an automated code
 reviewer that never gets tired and knows common vulnerability patterns.
 
diff --git a/docs/pages/security-testing/unit-testing.mdx b/docs/pages/security-testing/unit-testing.mdx
index 5215b1e7..0c89b27a 100644
--- a/docs/pages/security-testing/unit-testing.mdx
+++ b/docs/pages/security-testing/unit-testing.mdx
@@ -5,7 +5,7 @@ tags:
   - Engineer/Developer
   - Security Specialist
   - Operations & Strategy
-  - Devops
+  - DevOps
   - SRE
 contributors:
   - role: wrote
diff --git a/docs/pages/supply-chain/index.mdx b/docs/pages/supply-chain/index.mdx
index 1cdafcdc..5420e1c7 100644
--- a/docs/pages/supply-chain/index.mdx
+++ b/docs/pages/supply-chain/index.mdx
@@ -13,4 +13,4 @@ title: "Supply Chain"
 
 - [Supply Chain Security](/supply-chain/overview)
 - [Dependency Awareness](/supply-chain/dependency-awareness)
-- [Supply Chain Levels Software Artifacts](/supply-chain/supply-chain-levels-software-artifacts)
+- [Supply Chain Levels for Software Artifacts](/supply-chain/supply-chain-levels-software-artifacts)
diff --git a/docs/pages/supply-chain/overview.mdx b/docs/pages/supply-chain/overview.mdx
index a0ab2883..53e702be 100644
--- a/docs/pages/supply-chain/overview.mdx
+++ b/docs/pages/supply-chain/overview.mdx
@@ -4,7 +4,7 @@ description: "Supply Chain Security Framework: Secure all components, dependenci
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -19,7 +19,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 
 Supply chain security involves managing and securing all the components, dependencies, and processes involved in the
 development, deployment, and maintenance of software. In the context of blockchain and web3 projects, supply chain
-security could for example be parts of the web application stack, or external libraries used by the smart contract.
+security could, for example, include parts of the web application stack or external libraries used by the smart contract.
 
 ---
 
diff --git a/docs/pages/supply-chain/supply-chain-levels-software-artifacts.mdx b/docs/pages/supply-chain/supply-chain-levels-software-artifacts.mdx
index 1f46e7c0..1ae2885e 100644
--- a/docs/pages/supply-chain/supply-chain-levels-software-artifacts.mdx
+++ b/docs/pages/supply-chain/supply-chain-levels-software-artifacts.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Supply Chain Levels Software Artifacts | SEAL"
+title: "Supply Chain Levels for Software Artifacts | SEAL"
 description: "Prioritize security efforts with software artifact risk levels. Classify components as critical, high, moderate, or low risk and apply appropriate security controls to each level."
 tags:
   - Engineer/Developer
diff --git a/docs/pages/threat-modeling/create-maintain-threat-models.mdx b/docs/pages/threat-modeling/create-maintain-threat-models.mdx
index 8785d651..a93cad17 100644
--- a/docs/pages/threat-modeling/create-maintain-threat-models.mdx
+++ b/docs/pages/threat-modeling/create-maintain-threat-models.mdx
@@ -16,14 +16,14 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
 
-Creating and maintaining threat models help identify potential security risks and develop mitigation strategies to
+Creating and maintaining threat models helps identify potential security risks and develop mitigation strategies to
 protect the project.
 
 ## Steps to Create a Threat Model
 
 1. **Define the Scope**
    - Identify the contract, system, application, or component to be analyzed.
-   - Determine the boundaries and interfaces of the it.
+   - Determine the boundaries and interfaces of it.
 
 2. **Identify Assets**
    - List all critical assets that need protection, such as funds, data, credentials, and infrastructure components.
diff --git a/docs/pages/threat-modeling/identity-mitigate-threats.mdx b/docs/pages/threat-modeling/identity-mitigate-threats.mdx
index c581ad19..8937e017 100644
--- a/docs/pages/threat-modeling/identity-mitigate-threats.mdx
+++ b/docs/pages/threat-modeling/identity-mitigate-threats.mdx
@@ -4,7 +4,7 @@ description: "Identify threats using STRIDE, attack surface analysis, and advers
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -12,7 +12,7 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <TagProvider>
 <TagFilter />
 
-# Standard Operating Environment
+# Identify and Mitigate Threats
 
 <TagList tags={frontmatter.tags} />
 <AttributionList contributors={frontmatter.contributors} />
diff --git a/docs/pages/treasury-operations/enhanced-controls.mdx b/docs/pages/treasury-operations/enhanced-controls.mdx
index ccbe59ce..d7afefc1 100644
--- a/docs/pages/treasury-operations/enhanced-controls.mdx
+++ b/docs/pages/treasury-operations/enhanced-controls.mdx
@@ -45,7 +45,7 @@ recommended procedures.
 ## Access Security
 
 - Hardware security keys (FIDO2/WebAuthn) mandatory for all approvers
-  - Secure fallback: Each approver must register minimum 2 hardware keys stored in separate secure locations
+  - Secure fallback: Each approver must register a minimum of 2 hardware keys stored in separate secure locations
   - Key loss procedure: Temporary access via backup key + additional approver verification via multiple channels +
     mandatory key replacement within 48 hours
 - IP whitelisting with 24-hour change approval delay - if treasury software supports application-level IP whitelisting,
@@ -69,7 +69,7 @@ recommended procedures.
 
 ## MPC for Large Holdings
 
-For organizations managing >10% of total assets or >$10M equivalent in a single custodial account consider using MPC:
+For organizations managing >10% of total assets or >$10M equivalent in a single custodial account, consider using MPC:
 
 - Evaluate MPC (Multi-Party Computation) custody solutions that distribute key material across multiple parties
 - Consider threshold signature schemes (e.g., 3-of-5 or 5-of-9) where no single party controls sufficient key shares
diff --git a/docs/pages/treasury-operations/transaction-verification.mdx b/docs/pages/treasury-operations/transaction-verification.mdx
index e8c07f80..dd57143a 100644
--- a/docs/pages/treasury-operations/transaction-verification.mdx
+++ b/docs/pages/treasury-operations/transaction-verification.mdx
@@ -128,11 +128,11 @@ Request from sender:
 Since kidnapping and other forms of duress have been employed by criminals to steal cryptocurrency, organizations should
 prepare for this. Establish a duress word that indicates a transfer is not being made of your own free will. Once the
 duress word is mentioned during an exchange involving the transfer, law enforcement will be contacted and the
-transaction not processed. Procedures should be put in place with concrete run books for these situations. Safe words
-should not appear in run books or any digital format.
+transaction will not be processed. Procedures should be put in place with concrete runbooks for these situations. Safe words
+should not appear in runbooks or any digital format.
 **Anti-Social-Engineering Protocols:**
 
-Establish code phrase during initial verified meeting. Use this phrase to authenticate any address changes or unusual
+Establish a code phrase during the initial verified meeting. Use this phrase to authenticate any address changes or unusual
 requests. Example: "What was the name of the restaurant where we finalized the agreement?" Exchange secondary contact
 numbers for key personnel - if primary contact requests changes, call secondary to confirm. Maintain out-of-band
 verification: if request comes via email, confirm via phone.
@@ -150,7 +150,7 @@ counterparties will understand security delays.
 
 #### Pre-Transfer Video Verification (30 minutes prior to transfer)
 
-Require video call with minimum 2 _internal_ people present.
+Require a video call with a minimum of 2 _internal_ people present.
 
 **Liveness and identity verification** (prevents AI deepfakes):
 
diff --git a/docs/pages/vulnerability-disclosure/bug-bounties.mdx b/docs/pages/vulnerability-disclosure/bug-bounties.mdx
index 26e409e3..1e35b0c5 100644
--- a/docs/pages/vulnerability-disclosure/bug-bounties.mdx
+++ b/docs/pages/vulnerability-disclosure/bug-bounties.mdx
@@ -17,8 +17,8 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 <AttributionList contributors={frontmatter.contributors} />
 
 Bug bounty programs incentivize security researchers to identify and report vulnerabilities in your project. They
-augments a security team and audits by allowing external security researchers to disclose vulnerabilities in your
-project in a way that should be a good experience for the security researcher. Depending what the scope of the bug
+augment a security team and complement audits by allowing external security researchers to disclose vulnerabilities in your
+project in a way that should be a good experience for the security researcher. Depending on what the scope of the bug
 bounty program is, you may have a higher success rate having certain parts at different types of bug bounty as a service
 providers, as they generally have security researchers with different skill sets using their platforms.
 
diff --git a/docs/pages/vulnerability-disclosure/overview.mdx b/docs/pages/vulnerability-disclosure/overview.mdx
index 58706527..c0d432df 100644
--- a/docs/pages/vulnerability-disclosure/overview.mdx
+++ b/docs/pages/vulnerability-disclosure/overview.mdx
@@ -4,7 +4,7 @@ description: "Vulnerability Disclosure Framework: Responsible disclosure of iden
 tags:
   - Engineer/Developer
   - Security Specialist
-  - Devops
+  - DevOps
 ---
 
 import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
diff --git a/docs/pages/vulnerability-disclosure/security-contact.mdx b/docs/pages/vulnerability-disclosure/security-contact.mdx
index e31b2299..ffe71eb8 100644
--- a/docs/pages/vulnerability-disclosure/security-contact.mdx
+++ b/docs/pages/vulnerability-disclosure/security-contact.mdx
@@ -18,11 +18,11 @@ import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } fr
 
 Having a security contact provides a designated point of contact for security researchers to report vulnerabilities to.
 
-## SECURE.md File
+## SECURITY.md File
 
 ### Importance
 
-A SECURE.md file in your GitHub repository provides clear instructions on how to report security vulnerabilities.
+A SECURITY.md file in your GitHub repository provides clear instructions on how to report security vulnerabilities.
 
 ### Example Content
 
@@ -43,7 +43,7 @@ We appreciate your help in improving the security of our project.
 
 ### Importance
 
-Having a dedicated security email address (e.g., [security@projectname.TLD](security@projectname.TLD))
+Having a dedicated security email address (e.g., [security@projectname.TLD](mailto:security@projectname.TLD))
 ensures that vulnerability reports are directed to the appropriate team members.
 
 ### Setup
diff --git a/docs/pages/wallet-security/overview.mdx b/docs/pages/wallet-security/overview.mdx
index 41ced795..5c139735 100644
--- a/docs/pages/wallet-security/overview.mdx
+++ b/docs/pages/wallet-security/overview.mdx
@@ -44,7 +44,7 @@ transaction signing and verification.
   - [Verifying Standard Transactions (EOA)](/wallet-security/signing-and-verification/verifying-standard-transactions) -
   How to safely verify transactions from standard wallets.
   - [Multisig Signing Process](/wallet-security/signing-and-verification/secure-multisig-signing-process) - Detailed
-  guidefor secure multisig transaction signing.
+  guide for secure multisig transaction signing.
   - [Using EIP-7702](/wallet-security/signing-and-verification/verifying-7702) -  Enabling smart contract features for
   EOAs and mitigating new risks.
 - [Seed Phrase Management](/wallet-security/seed-phrase-management) - Best practices for securing your seed phrase.
diff --git a/utils/fetched-tags.json b/utils/fetched-tags.json
index dd4d6e4f..97f67dd8 100644
--- a/utils/fetched-tags.json
+++ b/utils/fetched-tags.json
@@ -7,6 +7,7 @@
     "Community & Marketing",
     "DAO",
     "DeFi",
+    "DevOps",
     "DevOps Accounts",
     "Devops",
     "Engineer/Developer",
@@ -168,18 +169,18 @@
     "/devsecops/code-signing": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/devsecops/continuous-integration-continuous-deployment": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/devsecops/integrated-development-environments": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/devsecops/isolation/capability-based-isolation": [
       "Engineer/Developer",
@@ -227,18 +228,18 @@
     "/devsecops/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/devsecops/repository-hardening": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/devsecops/security-testing": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/dprk-it-workers/case-studies": [
@@ -286,7 +287,7 @@
     "/encryption/cloud-data-encryption": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "Cloud"
     ],
     "/encryption/communication-encryption": [
@@ -320,7 +321,7 @@
     "/encryption/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "Cloud"
     ],
     "/encryption/partition-encryption": [
@@ -358,7 +359,7 @@
     "/external-security-reviews/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops"
+      "DevOps"
     ],
     "/external-security-reviews/security-policies-procedures": [
       "Security Specialist",
@@ -378,12 +379,12 @@
     "/external-security-reviews/smart-contracts/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops"
+      "DevOps"
     ],
     "/external-security-reviews/smart-contracts/preparation": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops"
+      "DevOps"
     ],
     "/external-security-reviews/smart-contracts/vendor-selection": [
       "Security Specialist",
@@ -392,7 +393,7 @@
     "/front-end-web-app/common-vulnerabilities": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/front-end-web-app/mobile-application-security": [
       "Engineer/Developer",
@@ -401,7 +402,7 @@
     "/front-end-web-app/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/front-end-web-app/security-tools-resources": [
       "Engineer/Developer",
@@ -414,7 +415,7 @@
     "/governance/compliance-regulatory-requirements": [
       "Operations & Strategy",
       "Legal & Compliance",
-      "Devops",
+      "DevOps",
       "HR"
     ],
     "/governance/overview": [
@@ -476,6 +477,10 @@
     "/guides/account-management/vercel": [
       "DevOps Accounts"
     ],
+    "/guides/endpoint-security/zoom-hardening": [
+      "Security Specialist",
+      "Operations & Strategy"
+    ],
     "/guides/overview": [
       "Security Specialist"
     ],
@@ -483,7 +488,7 @@
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "HR"
     ],
     "/iam/overview": [
@@ -495,14 +500,14 @@
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "HR"
     ],
     "/iam/secure-authentication": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "HR"
     ],
     "/incident-management/communication-strategies": [
@@ -516,19 +521,19 @@
     "/incident-management/lessons-learned": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/incident-management/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/incident-management/playbooks/decentralized-ir": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/incident-management/playbooks/hacked-dprk": [
@@ -558,14 +563,14 @@
     "/infrastructure/asset-inventory": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/infrastructure/cloud": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
@@ -573,7 +578,7 @@
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
@@ -607,7 +612,7 @@
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
@@ -615,13 +620,13 @@
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/infrastructure/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
@@ -717,7 +722,7 @@
     "/opsec/appendices/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/browser/overview": [
@@ -727,13 +732,13 @@
     "/opsec/continuous-improvement-metrics": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/control-domains/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/core-concepts/implementation-process": [
@@ -760,7 +765,7 @@
     "/opsec/integration/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/mfa/overview": [
@@ -770,7 +775,7 @@
     "/opsec/overview": [
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/passwords/overview": [
@@ -781,21 +786,21 @@
       "Security Specialist",
       "Operations & Strategy",
       "Engineer/Developer",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/travel/overview": [
       "Security Specialist",
       "Operations & Strategy",
       "Engineer/Developer",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/opsec/travel/tldr": [
       "Security Specialist",
       "Operations & Strategy",
       "Engineer/Developer",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/privacy/data-removal-services": [
@@ -817,7 +822,7 @@
     "/privacy/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/privacy/privacy-focused-operating-systems-tools": [
       "Engineer/Developer",
@@ -872,12 +877,12 @@
     "/secure-software-development/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/secure-software-development/secure-code-repositories-version-control": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/secure-software-development/secure-coding-standards-guidelines": [
       "Engineer/Developer",
@@ -890,77 +895,77 @@
     "/security-automation/compliance-checks": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
     "/security-automation/infrastructure-as-code": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
     "/security-automation/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "Cloud",
       "SRE"
     ],
     "/security-automation/threat-detection-response": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/formal-verification": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/fuzz-testing": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/integration-testing": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/mutation-testing": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/overview": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/static-analysis": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/security-testing/unit-testing": [
       "Engineer/Developer",
       "Security Specialist",
       "Operations & Strategy",
-      "Devops",
+      "DevOps",
       "SRE"
     ],
     "/supply-chain/dependency-awareness": [
@@ -970,7 +975,7 @@
     "/supply-chain/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/supply-chain/supply-chain-levels-software-artifacts": [
       "Engineer/Developer",
@@ -983,7 +988,7 @@
     "/threat-modeling/identity-mitigate-threats": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/threat-modeling/overview": [
       "Engineer/Developer",
@@ -1023,7 +1028,7 @@
     "/vulnerability-disclosure/overview": [
       "Engineer/Developer",
       "Security Specialist",
-      "Devops"
+      "DevOps"
     ],
     "/vulnerability-disclosure/security-contact": [
       "Engineer/Developer",
@@ -1095,6 +1100,10 @@
       "Engineer/Developer",
       "Security Specialist"
     ],
+    "/wallet-security/smart-contract-interaction-security": [
+      "Engineer/Developer",
+      "Security Specialist"
+    ],
     "/wallet-security/tools-and-resources": [
       "Engineer/Developer",
       "Security Specialist"
@@ -1138,6 +1147,7 @@
     "Treasury Operations": "treasury-operations",
     "Guides": "guides",
     "Account Management": "guides",
+    "Endpoint Security": "guides",
     "SEAL Certifications": "certs",
     "SEAL Certification Frameworks": "certs",
     "Contributing": "contribute"
diff --git a/wordlist.txt b/wordlist.txt
index 88e7f2d6..99ffd02d 100644
--- a/wordlist.txt
+++ b/wordlist.txt
@@ -58,7 +58,7 @@ DeIRF
 Dependabot
 Deseat
 dev
-Devops
+DevOps
 DevSecOps
 discoverable
 DIY
@@ -307,3 +307,6 @@ reauthentication
 CAIP
 unbonding
 unbond
+GitHub
+GitLab
+GoDaddy