diff --git a/docs/src/content/docs/patterns/project-ops.mdx b/docs/src/content/docs/patterns/project-ops.mdx
index 11b8d21a7c8..fb31904b143 100644
--- a/docs/src/content/docs/patterns/project-ops.mdx
+++ b/docs/src/content/docs/patterns/project-ops.mdx
@@ -17,10 +17,10 @@ In practice, this gives teams faster triage decisions, cleaner board state, stro
 ## Prerequisites
 
 1. **A Project board** and copy the project URL. See [Creating a project](https://docs.github.com/en/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project#creating-a-project).
-2. **A Project token** (PAT or GitHub App token). See [Authentication for Project Operations](#authentication-for-project-operations).
+2. **A Project token** (PAT or GitHub App token). See [Project Token Authentication](#project-token-authentication).
 3. **A field contract** (for example: Status, Priority, Team, Iteration, Target Date). See [Understanding fields](https://docs.github.com/en/issues/planning-and-tracking-with-projects/understanding-fields).
 
-## Authentication for Project Operations
+## Project Token Authentication
 
 Project operations need additional authentication because the default `GITHUB_TOKEN` is repository-scoped and cannot access Projects APIs for read/write project operations.
 
@@ -74,7 +74,7 @@ Let's look at examples of these in action, starting with the [Project Board Summ
 
 ## Examples
 
-### Project Board Summarizer (Read-only)
+### Project Board Summarizer
 
 Let's start with a simple agentic workflow that reviews project board state and generates a summary without applying any changes.
 
@@ -119,7 +119,7 @@ Running the agentic workflow generates a concise summary of project status. We c
   <img alt="Workflow summary output generated by Project Board Summarizer" src="/gh-aw/images/projectops-read-summary_light.png" />
 </picture>
 
-### Project Board Maintainer (Write)
+### Project Board Maintainer
 
 Let's write an agentic workflow that applies changes to a project board based on issue content and context.
 This workflow will run on new issues, analyze the issue and project state, and decide whether to add the issue to the project board and how to set key fields.
@@ -187,7 +187,7 @@ In production, keep the loop simple: issue arrives, agent classifies and propose
 
 ## Related documentation
 
-- **[Authentication for Project Operations](/gh-aw/patterns/project-ops/#authentication-for-project-operations)**
+- **[Project Token Authentication](/gh-aw/patterns/project-ops/#project-token-authentication)**
 - **[Safe Outputs Reference](/gh-aw/reference/safe-outputs/)**
 - **[Projects & Monitoring](/gh-aw/patterns/monitoring/)**
 - **[IssueOps](/gh-aw/patterns/issue-ops/)**