Clarify handoff failure wording

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: rachaelrenk

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

@@ -22,7 +22,7 @@ When you send a follow-up to a run whose session has ended, the run continues wi
 * **The prior workspace state** - The prior session's repository changes (tracked and untracked) are restored before the agent answers your follow-up. For Git-managed sessions, the new session continues on the same Git branch.
 * **Stable run identity** - The run's ID, task, creator, environment, schedule trigger, and integration source are preserved. Compute usage is recorded per session but rolls up to the same run.
 
-If applying any change fails, the agent reports what couldn't be applied and continues with the changes it could apply rather than starting over silently.
+If any changes fail to apply, the agent reports which changes failed and continues with the changes that applied cleanly.
 
 ## Prerequisites
 

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

@@ -32,7 +32,7 @@ Handoff preserves enough state that the receiving agent can resume the work, not
 * **Workspace state** - Local-to-cloud and cloud-to-cloud capture the prior session's repository changes (tracked and untracked) and apply them in the receiving run before the agent answers the next prompt. The cloud-to-local direction doesn't currently apply workspace patches to your local checkout; review the cloud agent's branch or pull request artifact to inspect those changes.
 * **Conversation attachments** - Files attached during the prior session remain available to the receiving agent.
 
-Handoff is best-effort. When the receiving agent can apply the prior session's changes cleanly, it picks up where the prior agent left off. When it can't, the agent reports what failed and continues with the changes it could apply rather than starting over silently.
+Handoff is best-effort. When the receiving agent can apply the prior session's changes cleanly, it picks up where the prior agent left off. When it can't, the agent reports which changes failed to apply and continues with the changes that applied cleanly.
 
 ## When to use handoff
 

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

@@ -25,7 +25,7 @@ When you hand off from local to cloud, the receiving cloud agent inherits:
 * **A workspace snapshot** - Warp captures your uncommitted repository changes — both tracked modifications and untracked files — and packages them for the cloud agent. The cloud agent applies them before answering your follow-up.
 * **Conversation attachments** - Files attached to the local conversation remain available in the cloud run.
 
-If applying any change fails in the cloud run, the cloud agent reports what couldn't be applied and proceeds with what it could rather than silently dropping changes.
+If any changes fail to apply in the cloud run, the cloud agent reports which changes failed and continues with the changes that applied cleanly.
 
 ## Prerequisites