docs: removed the word "new" from sandbox specific documentation

Environment-Variables.md

@@ -97,7 +97,7 @@ The following variable controls Coyote's [Sandbox mode](Sandboxes):
   created.
 - The path is passed verbatim to `sbx create --kit`; it must be a valid sbx kit (containing `spec.yaml`), not just any
   directory.
-- No environment variables map to the new sandbox-mode CLI flags (`--fresh`, `--no-mixins`). These are intentionally 
+- No environment variables map to the sandbox-mode CLI flags (`--fresh`, `--no-mixins`). These are intentionally 
   CLI-only. They're one-time per-invocation decisions, not configuration knobs.
 
 # Logging Related Variables

Sandboxes.md

@@ -33,7 +33,7 @@ The first run takes a few minutes (building the Coyote sandbox image, installing
 and installed tools persist inside the sandbox until you `sbx rm` it.
 
 Re-running `coyote --sandbox [NAME]` with the same name **re-attaches** to the existing sandbox silently rather than 
-creating a fresh one. `--fresh` and `--no-mixins` are ignored on re-attach (they only affect new sandbox creation).
+creating a fresh one. `--fresh` and `--no-mixins` are ignored on re-attach (they only affect sandbox creation).
 
 > **Tip:** Inside the sandbox REPL, prefix any line with `!` to run a shell command without going through `sbx exec 
 > <name> -- <cmd>` to modify the sandbox state; .e.g, `!apt-get update`, `!git pull`, `!cargo build`, etc. Output