docs: Improve remote browser page flow and structure

Author: beran-t

docs/use-cases/remote-browser.mdx

@@ -4,28 +4,17 @@ description: "Use Kernel cloud browsers with E2B sandboxes for web scraping, app
 icon: "globe"
 ---
 
-[Kernel](https://www.kernel.computer/) provides cloud browsers — remote Chromium instances your agents can control via [CDP](https://chromedevtools.github.io/devtools-protocol/) (Chrome DevTools Protocol).
+[Kernel](https://www.kernel.computer/) provides cloud browsers — remote Chromium instances your agents can control through Playwright. Instead of running a browser inside the sandbox, your agent connects to a Kernel browser over the network.
 
-## Why use a remote browser?
+This keeps your sandbox lightweight — no Chrome installation, no GPU-hungry rendering. Kernel also handles CAPTCHA and bot detection with stealth mode, residential proxies, and persistent browser profiles. You can spin up multiple browsers simultaneously from a single sandbox.
 
-Running a browser inside the sandbox works, but offloading it to Kernel has real advantages:
-
-- **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 from a single sandbox.
-
-## Two approaches
-
-E2B provides pre-built sandbox templates with the Kernel SDK already installed:
+E2B provides two pre-built sandbox templates with the Kernel SDK already installed:
 
 | Template | What's included | Best for |
 |---|---|---|
 | `kernel-browser` | Kernel SDK, Playwright | Programmatic browsing — screenshots, scraping, app previews |
 | `kernel-agent-browser` | Kernel SDK, Playwright, Browser Use | Autonomous AI agents that browse on their own |
 
-Both templates connect to Kernel browsers over CDP. The difference is whether *you* write the browsing logic or an *LLM agent* decides what to do.
-
 ## Prerequisites
 
 - An [E2B API key](https://e2b.dev/dashboard?tab=keys)
@@ -77,7 +66,7 @@ sandbox.commands.run(
 </Step>
 
 <Step title="Get the public URL and browse with Kernel">
-E2B exposes any sandbox port as a public HTTPS endpoint. A script inside the sandbox creates a Kernel browser, connects via Playwright CDP, and screenshots each route.
+E2B exposes any sandbox port as a public HTTPS endpoint. A script inside the sandbox creates a Kernel browser, connects via Playwright, and screenshots each route.
 
 ```python
 host = sandbox.get_host(8000)