update intro

Author: matthewlouisbrockman

docs/sandbox/auto-resume.mdx

@@ -3,9 +3,9 @@ title: "AutoResume"
 sidebarTitle: AutoResume
 ---
 
-Managing sandbox lifecycle manually can get painful. Instead of handling pause/resume orchestration yourself, your sandbox should come back to life when you need it.
+You shouldn't have to manually manage sandbox pause/resume. With AutoResume, your sandbox can pause at timeout and come back when traffic arrives, so it's available when needed without extra orchestration.
 
-`AutoResume` builds on [sandbox persistence](/docs/sandbox/persistence): a sandbox pauses at timeout and then resumes from that paused state when it receives traffic.
+`AutoResume` builds on [sandbox persistence](/docs/sandbox/persistence): a sandbox pauses at timeout and resumes from that paused state when it receives traffic.
 Configure `AutoResume` through the `lifecycle` object when creating a sandbox.
 
 ## Configure lifecycle on create
@@ -18,7 +18,7 @@ const sandbox = await Sandbox.create({
   timeoutMs: 10 * 60 * 1000,
   lifecycle: {
     onTimeout: 'pause',
-    resumeOn: 'any',
+    resumeOn: 'any', //the sandbox will resume on any traffic
   },
 })
 ```
@@ -29,7 +29,7 @@ sandbox = Sandbox.create(
     timeout=10 * 60,
     lifecycle={
         "on_timeout": "pause",
-        "resume_on": "any",
+        "resume_on": "any", # the sandbox will resume on any traffic
     },
 )
 ```
@@ -42,8 +42,8 @@ sandbox = Sandbox.create(
   - `pause`: sandbox is paused when timeout is reached
 - `resumeOn` / `resume_on`
   - `off` (default): paused sandboxes do not auto-resume
-  - `any`: paused sandboxes auto-resume on activity
-  - `any` is valid only when `onTimeout`/`on_timeout` is `pause`
+  - `any`: paused sandboxes auto-resume on activity. 
+    - `any` is valid only when `onTimeout`/`on_timeout` is `pause`
 
 ## Behavior summary
 
@@ -60,3 +60,8 @@ Configure `lifecycle` with `onTimeout: "pause"` and `resumeOn: "any"` so the san
 
 2. Code execution workloads
 For agent/tool execution, use `resumeOn: "any"` so the sandbox can start back up automatically when the next command or code execution request arrives.
+
+## Cleanup
+Auto-resume is persistent, meaning if your sandbox resumes and later times out again, it will pause again.
+
+If you call `.kill()`, the sandbox is permanently deleted and cannot be resumed.