diff --git a/content/manuals/ai/sandboxes/customize/kits.md b/content/manuals/ai/sandboxes/customize/kits.md
index 1b7f0942323..596ed605548 100644
--- a/content/manuals/ai/sandboxes/customize/kits.md
+++ b/content/manuals/ai/sandboxes/customize/kits.md
@@ -316,8 +316,9 @@ $ sbx run claude --kit /path/to/ruff-lint/
 
 To apply the mixin to a sandbox that's already running, use
 [`sbx kit add`](#local) instead. The `--kit` flag only takes effect when a
-sandbox is created. `sbx kit add` recreates the sandbox container, but VM state
-— installed packages, Docker images, volumes, and agent history — is preserved.
+sandbox is created. `sbx kit add` restarts the sandbox to apply the kit, but VM
+state — installed packages, Docker images, volumes, and agent history — is
+preserved.
 
 ## Sandbox kits
 
@@ -389,9 +390,9 @@ several kits on the same sandbox.
 > against an existing sandbox name fails with
 > `--kit can only be used when creating a new sandbox`. To extend a
 > running sandbox with a kit, use [`sbx kit add`](#local) instead.
-> `sbx kit add` recreates the sandbox container with the updated kit set.
+> `sbx kit add` restarts the sandbox to apply the updated kit set.
 > VM state — installed packages, Docker images, volumes, and agent history
-> — is preserved across the recreation.
+> — is preserved across the restart.
 
 ### Local
 
@@ -408,9 +409,9 @@ While iterating on a kit, apply changes to a running sandbox with `sbx kit add`:
 $ sbx kit add my-sandbox ./my-kit/
 ```
 
-`sbx kit add` recreates the sandbox container with the updated kit set.
+`sbx kit add` restarts the sandbox to apply the updated kit set.
 VM state — installed packages, Docker images, volumes, and agent history — is
-preserved across the recreation. The kit's network allow/deny rules take effect
+preserved across the restart. The kit's network allow/deny rules take effect
 immediately. Kits can't be removed from a running sandbox — remove and recreate
 it to start clean.