diff --git a/apps/docs/content/guides/deployment-lifecycle.mdx b/apps/docs/content/guides/deployment-lifecycle.mdx
index f7e2e081..bb140214 100644
--- a/apps/docs/content/guides/deployment-lifecycle.mdx
+++ b/apps/docs/content/guides/deployment-lifecycle.mdx
@@ -86,7 +86,7 @@ Default behavior (`temporaryShutdown: false`):
 
 ### Deploy strategy & checks
 
-`temporaryShutdown` (in the `deploy` block) controls cutover order: `false` (default) starts new containers before removing old ones (zero-downtime); `true` stops old before new (downtime, use only when two versions cannot coexist — exclusive DB migrations, singleton locks). The **readiness check** gates traffic to the new container during a deploy; the **health check** monitors the live app continuously. For check behavior, params, the httpGet/exec timeouts, and the production pattern, see `zerops://guides/readiness-health-checks`.
+`temporaryShutdown` (in the `deploy` block) controls cutover order: `false` (default) starts new containers before removing old ones (zero-downtime); `true` stops old before new (downtime, use only when two versions cannot coexist — exclusive DB migrations, singleton locks). The **readiness check** gates traffic to the new container during a deploy; the **health check** monitors the live app continuously. For check behavior, params, the httpGet/exec timeouts, and the production pattern, see `zerops_knowledge uri="zerops://guides/readiness-health-checks"`.
 
 ---
 
diff --git a/apps/docs/content/guides/production-checklist.mdx b/apps/docs/content/guides/production-checklist.mdx
index f935ea20..18dfaa31 100644
--- a/apps/docs/content/guides/production-checklist.mdx
+++ b/apps/docs/content/guides/production-checklist.mdx
@@ -141,7 +141,7 @@ Remove entirely or disable `enableSubdomainAccess`. Use VPN + pgAdmin/DBeaver lo
 
 ## Health Check Pattern
 
-Production services should pair a `deploy.readinessCheck` (gates traffic during deploy) with a `run.healthCheck` (continuous — the LB routes around an unhealthy container). The combined pattern, params, and behavior are in `zerops://guides/readiness-health-checks`.
+Production services should pair a `deploy.readinessCheck` (gates traffic during deploy) with a `run.healthCheck` (continuous — the LB routes around an unhealthy container). The combined pattern, params, and behavior are in `zerops_knowledge uri="zerops://guides/readiness-health-checks"`.
 
 ## Gotchas
 1. **HA is immutable**: Must delete and recreate service to switch modes
diff --git a/apps/docs/content/guides/zerops-yaml-advanced.mdx b/apps/docs/content/guides/zerops-yaml-advanced.mdx
index b0c29580..d9b0c704 100644
--- a/apps/docs/content/guides/zerops-yaml-advanced.mdx
+++ b/apps/docs/content/guides/zerops-yaml-advanced.mdx
@@ -9,7 +9,7 @@ Behavioral semantics for advanced zerops.yml features: health/readiness checks,
 
 ## Health / Readiness Checks & temporaryShutdown
 
-Health checks (`run.healthCheck`, continuous), readiness checks (`deploy.readinessCheck`, deploy-time traffic gate), the httpGet/exec shape + params + failure sequence, the dev/stage placement rule (dev uses `start: zsc noop --silent`, no healthCheck), and `temporaryShutdown` deploy ordering are all owned by `zerops://guides/readiness-health-checks`.
+Health checks (`run.healthCheck`, continuous), readiness checks (`deploy.readinessCheck`, deploy-time traffic gate), the httpGet/exec shape + params + failure sequence, the dev/stage placement rule (dev uses `start: zsc noop --silent`, no healthCheck), and `temporaryShutdown` deploy ordering are all owned by `zerops_knowledge uri="zerops://guides/readiness-health-checks"`.
 
 ---