Update src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx

Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>

Author: hongyi-chen

src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx

@@ -44,9 +44,9 @@ You don't take a separate "hand off" action — you send a follow-up, and the ru
 The run picks up where it left off, with workspace state restored.
 
 ### Third-party harnesses
+### Third-party agent runtimes
 
-Cloud-to-cloud handoff works for third-party harnesses too, but the affordance is a **Continue** button followed by an input prompt instead of the standard follow-up input. Click **Continue** on the ended run (from the conversation details panel or the end-of-run tombstone) and enter the next message you want the agent to act on.
-
+Cloud-to-cloud handoff also works for supported third-party agent runtimes, but the affordance is a **Continue** button followed by an input prompt instead of the standard follow-up input. Click **Continue** on the ended run (from the conversation details panel or the end-of-run tombstone) and enter the next message you want the agent to act on.
 ## Inspecting a run that's been handed off
 
 The [management view](/agent-platform/cloud-agents/managing-cloud-agents/) shows one row per run, even when the run spans multiple sessions. Click into the run to see the full transcript: each execution appears in order, and you can scan the transcript to see where one execution ended and the next began. Per-execution timestamps aren't currently exposed in the API; the transcript is the source of truth.