wording on auto-resume

Author: matthewlouisbrockman

docs/sandbox/auto-resume.mdx

@@ -11,7 +11,7 @@ Behavior and limits may change as we iterate. Review [Sandbox persistence limita
 
 Many workloads don't need a sandbox running all the time, but when they do need it, it should just work, whether it was paused or not.
 
-`AutoResume` handles this automatically: a paused sandbox wakes up when traffic arrives, so your code never has to check or manage sandbox state.
+`AutoResume` handles this automatically: a paused sandbox wakes up when activity arrives, so your code does not have to check or manage sandbox state.
 Configure it through the `lifecycle` object when creating a sandbox.
 
 ## Configure lifecycle on create
@@ -48,14 +48,15 @@ sandbox = Sandbox.create(
   - `pause`: sandbox is paused when timeout is reached
 - `autoResume` / `auto_resume`
   - `false` (default): paused sandboxes do not auto-resume
-  - `true`: paused sandboxes auto-resume on traffic
+  - `true`: paused sandboxes auto-resume on activity
   - `true` is valid only when `onTimeout`/`on_timeout` is `pause`
 
 ## Behavior summary
 
 - Default behavior is equivalent to `onTimeout: "kill"` with `autoResume: false`.
 - `onTimeout: "pause"` with `autoResume: false` gives auto-pause without auto-resume.
 - `onTimeout: "pause"` with `autoResume: true` gives auto-pause with auto-resume.
+- [`Sandbox.connect()`](/docs/sandbox/connect) can still be used to resume a paused sandbox manually.
 
 If you use `autoResume: false`, resume explicitly with [`Sandbox.connect()`](/docs/sandbox/connect).