diff --git a/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx b/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx
index 55477f3e..77df6335 100644
--- a/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx
@@ -88,7 +88,7 @@ The parent (the "writer") proposes a solution, then spawns a critic child to rev
 
 ### Review swarm (cloud → cloud)
 
-A scheduled or webhook-triggered parent spawns one cloud child per open pull request to run reviews in parallel. Each child posts its findings as a comment and exits. The parent fans in the results and posts a summary back to the triggering system.
+A [scheduled](/agent-platform/cloud-agents/triggers/scheduled-agents/) or webhook-triggered parent spawns one cloud child per open pull request to run reviews in parallel. Each child posts its findings as a comment and exits. The parent fans in the results and posts a summary back to the triggering system.
 
 ### DAG
 
diff --git a/src/content/docs/agent-platform/cloud-agents/platform.mdx b/src/content/docs/agent-platform/cloud-agents/platform.mdx
index a3e823d3..f825d2b9 100644
--- a/src/content/docs/agent-platform/cloud-agents/platform.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/platform.mdx
@@ -90,6 +90,7 @@ The orchestrator:
 * Tracks lifecycle state (created → running → completed/failed) and associated metadata.
 * Exposes task lifecycle operations via the [Oz CLI](/reference/cli/) and a [REST API](/reference/api-and-sdk/) (create tasks, query history, and inspect status/outputs).
 * Powers SDKs (TypeScript/Python) for programmatic usage on top of the orchestrator API.
+* Supports [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) for parent/child workflows, fan-out, and review swarms.
 
 #### When teams use the API/SDK
 
diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx
index a703ecb3..a0d712ee 100644
--- a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx
@@ -300,6 +300,6 @@ Carefully review prompts and schedules before deploying them broadly, especially
 
 Scheduled Agents are best when work should happen on a predictable cadence.
 
-If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use triggered cloud agents instead.
+If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use [integrations](/agent-platform/cloud-agents/integrations/) to trigger cloud agents instead.
 
-Many teams use both together: triggers for reactive workflows, and Scheduled Agents for proactive maintenance.
+Many teams use both together: [triggers](/agent-platform/cloud-agents/triggers/) for reactive workflows, and Scheduled Agents for proactive maintenance.