diff --git a/docs/src/content/docs/patterns/project-ops.mdx b/docs/src/content/docs/patterns/project-ops.mdx
index 4cb7be7f50b..0e6adea02bb 100644
--- a/docs/src/content/docs/patterns/project-ops.mdx
+++ b/docs/src/content/docs/patterns/project-ops.mdx
@@ -30,7 +30,7 @@ ProjectOps combines two capability layers:
   - **[`update-project`](/gh-aw/reference/safe-outputs/#project-board-updates-update-project)** — use when you want to add issues/PRs to a project or update fields (status, priority, owner, dates, custom values).
   - **[`create-project-status-update`](/gh-aw/reference/safe-outputs/#project-status-updates-create-project-status-update)** — use when you want a stakeholder-facing summary in the project Updates tab (weekly health, blockers, risks, next decisions).
   - **[`create-project`](/gh-aw/reference/safe-outputs/#project-creation-create-project)** — use when automation needs to bootstrap a new board for an initiative or team.
-  - **[`add-comment`](/gh-aw/reference/safe-outputs/#issue-and-pr-comments-add-comment)** — use when you want to explain routing decisions or request missing info on the triggering issue/PR.
+  - **[`add-comment`](/gh-aw/reference/safe-outputs/#comment-creation-add-comment)** — use when you want to explain routing decisions or request missing info on the triggering issue/PR.
 
 Let's look at examples of these in action, starting with the [Project Board Summarizer](#project-board-summarizer) (read-only analysis), then moving to controlled write operations with the [Project Board Maintainer](#project-board-maintainer) example.