fix: review update

Author: cdcabrera

CONTRIBUTING.md

@@ -25,7 +25,7 @@ your contribution is aligned with the project's goals.
 
 ##### Windows and repository symlinks
 
-Some paths in this repo are **symbolic links** so tools can reach shared skills without needing to host multiple versions of the same files. For example, `.agents/skills` and `.claude/skills` point at `guidelines/skills`. On **Windows**, Git may create **regular folders or files** instead of links, so these locations can look empty or broken.
+Some paths in this repo are **symbolic links** so tools can reach shared skills without needing to host multiple versions of the same files. For example, `.agents/skills` and `.claude/skills` point to `guidelines/skills`. On **Windows**, Git may create **regular folders or files** instead of links, so these locations can look empty or broken.
 
 **Before you clone the repository**
 
@@ -35,7 +35,7 @@ Some paths in this repo are **symbolic links** so tools can reach shared skills
 **If the repo is already on disk and the links are broken**
 
 Turning on Developer Mode or Git symlink settings **does not always fix** paths Git has already created as ordinary files.
-- Delete the broken `.agents/skills` and `.claude/skills` entries, or remove the entire folder/directory and **clone again**
+- Delete the broken `.agents/skills` and `.claude/skills` entries, or remove the entire folder/directory and **clone again**.
 - Then follow the **Before you clone the repository** steps above
 
 > If you are unsure of any steps, please verify them with your IT or system administrator before proceeding.
@@ -56,7 +56,7 @@ Our process follows the standard GitHub fork and pull request workflow.
 - Submit a pull request towards the main repository default branch
 
 ##### Main repository branches
-- The `main` branch currently represents both development and stable releases
+- The `main` branch currently represents both development and stable releases.
 
 > In the future, if there is an increase in contributions, we may consider implementing a `stable` branch.
 >    - `main` would be the default branch for development and feature work rebased from `stable` after release.
@@ -184,7 +184,7 @@ For detailed information on agent interaction, see [guidelines/README.md](./guid
 #### Customizing developer experience
 
 As developers, we often have our own preferred workflows, and that includes working with AI agents. To that point, we've added agent guidance
-to allow customization for your work environment through a tool-agnostic git-ignored directory `./.agent` in the root of the project.
+to allow customization for your work environment through a tool-agnostic gitignored directory `./.agent` in the root of the project.
 
 #### Noting AI agent contributions
 

GOVERNANCE.md

@@ -9,10 +9,10 @@ GitHub workflows perform checks for
 - Spelling and linting for most files
 - Unit testing
 - E2E testing
-- Dependency Auditing: Automated `npm audit` checks to identify and block critical-risk vulnerabilities in the project's dependency tree, running on every dependency change and daily thereafter.
+- Dependency Auditing: Automated `npm audit` checks to identify critical-risk vulnerabilities in the project's dependency tree, running on every dependency change and daily thereafter.
 - Conditional Data Auditing: If and when related files are updated, an automated audit verifies the integrity and reachability of PatternFly documentation entries.
 
-> Core contributors may receive an automated pass on Layer-1 policy checks when the workflow makes an allowance. This pass does not remove the remaining steps of automated review, nor the later layers of review and runtime boundaries.
+> Layer-1 policy feedback may be handled at the maintainer or organization level for established contributors. Any such discretion applies only to how policy findings are triaged; it does not extend to waiving automated checks, human review (Layer 2), or runtime boundaries (Layer 3).
 
 ## Layer 2: Human Review
 
@@ -31,4 +31,4 @@ The PatternFly MCP server implements security at the execution level:
 
 ## What This Means in Practice
 
-No single automated check or individual contributor can bypass the security chain. A malicious or accidental change must pass Layer-1, a Human Maintainer (Layer 2), and still operate within the Sandbox (Layer 3) to affect a user.
+No single automated check or individual contributor can bypass the security chain. A malicious or accidental change must pass Layer-1, a Human maintainer (Layer 2), and still operate within the Sandbox (Layer 3) to affect a user.

SECURITY.md

@@ -20,7 +20,7 @@ Security concerns for this MCP server include:
 To maintain codebase integrity:
 - PRs from non-core contributors that modify core behavior or exceed recommended file limits are considered placed on **Policy Hold** until they are reviewed in-depth to ensure architectural alignment.
 - PRs from community contributors can refer to the mirrored guidance and status in the **GitHub Actions workflow logs** for helpful feedback.
-- PRs require a secondary review by a Maintainer to be promoted from Policy Hold status.
+- PRs require a secondary review by a maintainer to be promoted from Policy Hold status.
 
 ## Release Integrity
 

docs/architecture.md

@@ -53,7 +53,7 @@ this actively plays a role in the library architecture because it allows us to f
 
 Key goals aided by moving towards plugins:
 - **Providing a tailored experience for users** - Plugins a designer uses may differ from those of a developer, researcher, or community member.
-- **Evolving/future proofing** - Plugins can evolve over time, and the MCP server can evolve to support them. (e.g., a new JS framework or design framework, etc.)
+- **Evolving/future-proofing** - Plugins can evolve over time, and the MCP server can evolve to support them. (e.g., a new JS framework or design framework)
 - **Maintainability** - MCP server core can focus on features and issues while plugins are added and maintained by the community.
 
 ## Server architecture
@@ -94,7 +94,7 @@ Our roadmap focuses on expanding the server's reach and providing a more integra
 - **Experimental Context Management**: Streamlining MCP resources into two primary types: **collections** and **records**. This includes providing exact hashes for records to ensure context stability.
 - **PatternFly API Integration**: Transitioning to the unified Library concept for standalone purposes and latest PatternFly version access.
    - **SQLite Persistence Layer (Opt-in)**: Leveraging **Node.js 22+** to provide an optional persistence layer for up-to-date library records and resource caching.
-   - **Records' Seed Integration**: A "fallback" set of resource records applied to every PatternFly MCP server instance that ensures users who do not opt into SQLite persistence still receive up-to-date documentation within an average MCP server use session.
+   - **Record Seed Integration**: A "fallback" set of resource records applied to every PatternFly MCP server instance that ensures users who do not opt into SQLite persistence still receive up-to-date documentation within an average MCP server use session.
 
 #### In-planning and under review
 - **Skills-as-Tools (On Track)**: Expand MCP functionality with agent skills using common Markdown. This provides consumers with significant customization without modifying the PatternFly MCP server core. You can start contributing to the MCP now by adding skills through our [AI Plugin Marketplace](https://github.com/patternfly/ai-helpers).
@@ -112,7 +112,7 @@ Our roadmap focuses on expanding the server's reach and providing a more integra
 >
 > Contributions that overlap with upcoming roadmap items (such as the shift to modular plugins or dynamic API-level data) may be deferred or redirected to ensure they align with the future state of the project.
 >
-> Review our [contribution guidelines](../CONTRIBUTING.md)
+> Review our [contribution guidelines](../CONTRIBUTING.md).
 
 #### Future state