docs: Remove cost framing from remote browser benefits

Author: beran-t

docs/use-cases/remote-browser.mdx

@@ -10,10 +10,10 @@ icon: "globe"
 
 Running a browser inside the sandbox works, but offloading it to Kernel has real advantages:
 
-- **No sandbox compute wasted on Chrome** — Chromium is resource-hungry. Kernel runs it on dedicated infrastructure so your sandbox CPU and memory stay available for your agent's actual work.
+- **Keeps your sandbox lightweight** — Chromium is resource-hungry. Offloading it to Kernel frees your sandbox CPU and memory for your agent's actual work.
 - **Zero installation** — no need to install Chrome, Chromium, or Playwright binaries in your sandbox template. Kernel provides the browser remotely.
 - **Built-in CAPTCHA and bot detection handling** — Kernel browsers support stealth mode, residential proxies, and browser profiles that persist cookies and sessions across runs.
-- **Parallel browsing** — spin up multiple Kernel browsers simultaneously without multiplying sandbox costs.
+- **Parallel browsing** — spin up multiple Kernel browsers simultaneously from a single sandbox.
 
 ## Two approaches