diff --git a/docs/architecture/sprint-execution-modes.md b/docs/architecture/sprint-execution-modes.md
index 02ec11e..dc0fb4e 100644
--- a/docs/architecture/sprint-execution-modes.md
+++ b/docs/architecture/sprint-execution-modes.md
@@ -19,7 +19,7 @@ related: [project-structure.md](./project-structure.md), [data-model.md](./data-
 
 `STORY` en `SPRINT` triggeren beide het PER_TASK-pad: per TO_DO-task één
 `ClaudeJob` met `kind=TASK_IMPLEMENTATION`. Het verschil zit alleen in de
-PR-strategie van [`maybeCreateAutoPr`](../../scrum4me-mcp/src/tools/update-job-status.ts).
+PR-strategie van [`maybeCreateAutoPr`](https://github.com/madhura68/scrum4me-mcp/blob/main/src/tools/update-job-status.ts).
 
 `SPRINT_BATCH` triggert het PER_SPRINT-pad: één `ClaudeJob` met
 `kind=SPRINT_IMPLEMENTATION` die alle TO_DO-tasks van de sprint sequentieel
@@ -91,5 +91,5 @@ PER_TASK (STORY/SPRINT):                  SPRINT_BATCH:
 | `job_heartbeat` | ✓ (lease-extend, no sprint-fields) | ✓ (lease-extend + `sprint_run_status` poll) |
 | `update_job_status` | ✓ (per-task) | ✓ (aggregate `checkSprintVerifyGate` + `finalizeSprintRunOnDone`) |
 
-Volledige tool-catalogus: [scrum4me-mcp README](../../scrum4me-mcp/README.md).
-Worker-loop pseudocode: [scrum4me-docker CLAUDE.md](../../scrum4me-docker/CLAUDE.md).
+Volledige tool-catalogus: [scrum4me-mcp README](https://github.com/madhura68/scrum4me-mcp#readme).
+Worker-loop pseudocode: [scrum4me-docker CLAUDE.md](https://github.com/madhura68/scrum4me-docker/blob/master/CLAUDE.md).