Apply suggestions from code review

Signed-off-by: Eddie Knight <[email protected]>

content/en/docs/community_roles/_index.md

@@ -4,7 +4,7 @@ weight: 10
 hide_readingtime: true
 ---
 
-Individuals in following roles are the backbone of this community.
+Individuals the in following roles are the backbone of this community.
 
 Frequently, individuals will act in different roles at different times, or multiple at once.
 

content/en/docs/community_roles/admin.md

@@ -4,13 +4,13 @@ hide_readingtime: true
 weight: 40
 ---
 
-The Organization Administrators serve as the strategic overseers of the GitHub organization, responsible for governance, permissions, and maintaining the integrity of the repository ecosystem. Their role ensures seamless collaboration, safeguards project resources, and provides stewardship over organizational assets— ensuring the community's long-term sustainability and security.
+The Organization Administrators serve as the strategic overseers of the GitHub organization, responsible for governance, permissions, and maintaining the integrity of the repository ecosystem. Their role ensures seamless collaboration, safeguards project resources, and provides stewardship over organizational assets — ensuring the community's long-term sustainability and security.
 
 ## How to Become an Org Admin
 
-Organizational Admins are selected from the Sonatype OSPO and are entrusted with the responsibility of overseeing the GitHub organization's logistics. This role is reserved for those who have demonstrated exceptional leadership and a deep understanding of the project ecosystem.
+Organization Admins are selected from the Sonatype OSPO and are entrusted with the responsibility of overseeing the GitHub organization's logistics. This role is reserved for those who have demonstrated exceptional leadership and a deep understanding of the project ecosystem.
 
-Org Admins manage permissions, enforce policies, and ensure that this organization remains a secure and collaborative environment. With a maximum of three Org Admins at any time, this role requires a proven track record of dedication, trustworthiness, and strategic vision within the open-source community.
+Organization Admins manage permissions, enforce policies, and ensure that this organization remains a secure and collaborative environment. With a maximum of three Organization Admins at any time, this role requires a proven track record of dedication, trustworthiness, and strategic vision within the open-source community.
 
 
 {{% alert %}}

content/en/docs/community_roles/contributor.md

@@ -8,14 +8,16 @@ A Project Contributor plays a pivotal role in shaping the project through code,
 
 ## How to Become a Contributor
 
-To contribute to a project, individuals must first interact with _Paul Botsco_ to sign the Contributor License Agreement (CLA), ensuring that their contributions comply with legal requirements.
+To [contribute](../contributing) to a project, individuals must first interact with _Paul Botsco_ to sign the Contributor License Agreement (CLA), ensuring that their contributions comply with our legal requirements.
 
 _Paul Botsco_ will comment on your first pull request, providing you with the latest links and helpful information to sign the CLA.
 
 Once the CLA is signed, contributors can engage with the project by opening issues to report bugs, request features, or suggest improvements. They can also submit pull requests (PRs) to offer code, documentation, or design enhancements.
 
 In the rare event that the CLA text is updated, Paul Botsco will comment on your next pull request to guide you through the process again.
 
+This role does not require any permissions changes.
+
 **Next level:** [Project Maintainer](./maintainer.md)
 
 {{% alert color="info" %}}

content/en/docs/community_roles/user.md

@@ -8,4 +8,6 @@ A Project User engages with the project primarily by utilizing its features, fol
 
 Feedback may be provided by users through the form of GitHub _Issues_ or _Discussions_, depending on the preference of the project.
 
+This role does not require any permissions changes.
+
 **Next level:** [Project Contributor](./contributor.md)