kernel · andrewleesteele · Jul 28, 2026 · Jul 29, 2026 · Jul 29, 2026 · Jul 29, 2026
diff --git a/auth/profiles.mdx b/auth/profiles.mdx
@@ -264,7 +264,7 @@ You cannot load a profile into a browser that was already created with a profile
 </Warning>
 
 <Note>
-To use profiles with browser pools, read: [Can pooled browsers save changes back to a profile?](/browsers/pools/faq#can-pooled-browsers-save-changes-back-to-a-profile)
+To use profiles with browser pools, see [Profiles with browser pools](/browsers/pools#profiles-with-browser-pools)
 </Note>
 
 ## Other ways to use profiles
@@ -494,5 +494,5 @@ _ = browser
 - Profiles store cookies and local storage. Start the session with `save_changes: true` to write changes back when the browser is closed.
 - To keep a profile immutable for a run, omit `save_changes` (default) when creating the browser.
 - Multiple browsers in parallel can use the same profile, but only one browser should write (`save_changes: true`) to it at a time. Parallel browsers with `save_changes: true` may cause profile corruption and unpredictable behavior.
-- `save_changes` applies to a profile attached to a single browser — either at creation (`kernel.browsers.create()`) or loaded afterward with `kernel.browsers.update()`. A profile set on a [browser pool's](/browsers/pools/overview) config is loaded read-only and never persisted; `save_changes` sent on a pool's profile is silently ignored. To persist per-user state through a pool, attach the profile after acquiring the browser and release with `reuse: false` — see [Per-user profiles with pools](/browsers/pools/overview#per-user-profiles-with-pools).
+- `save_changes` applies to a profile attached to a single browser — either at creation (`kernel.browsers.create()`) or loaded afterward with `kernel.browsers.update()`. A profile set on a [browser pool's](/browsers/pools) config is loaded read-only and never persisted; `save_changes` sent on a pool's profile is silently ignored. To persist per-user state through a pool, attach the profile after acquiring the browser and release with `reuse: false` — see [Per-user profiles with pools](/browsers/pools#per-user-profiles-with-browser-pools).
 - Profile data is encrypted end to end using a per-organization key.
diff --git a/browsers/bot-detection/overview.mdx b/browsers/bot-detection/overview.mdx
@@ -31,12 +31,12 @@ Every Kernel browser launches with anti-detection chrome configuration applied.
 On top of the defaults, stealth mode adds a default ISP proxy and an automatic CAPTCHA solver. Both are opt-out so you can BYO proxy and/or CAPTCHA tooling.
 
 ### [Configurable Proxies](/proxies/overview)
-Bring your own proxy network or use Kernel's managed pool (selectable down to ZIP-code level). If needed, use the same IP to reduce detection and allow for regional testing or QA.
+Bring your own proxy network or use Kernel's managed proxy pool (selectable down to ZIP-code level). If needed, use the same IP to reduce detection and allow for regional testing or QA.
 
 ### [Profiles](/auth/profiles)
 Profiles persist cookies, local storage, and session data between runs. Combined with a fixed proxy, this mimics a returning user. We recommend using them to persist authenticated states and reduce CAPTCHAs.
 
-### [Browser Pools](/browsers/pools/overview)
+### [Browser Pools](/browsers/pools)
 Browser pools let you reuse browsers across multiple visits to the same website, which introduces consistency with respect to the IP address. Since IP addresses are one of the main components of fingerprinting used by modern bot detection systems, browser pools drastically increase your chances of avoiding detection.
 
 ### [Playwright Execution API](/browsers/playwright-execution)
@@ -92,7 +92,7 @@ Kernel's [stealth mode](/browsers/bot-detection/stealth) uses static ISP proxies
 
 [Residential proxies](/proxies/residential) route traffic through real consumer devices, making them the least detectable proxy type by ASN classification. However, exit IPs [rotate per connection](/proxies/residential#ip-rotation-behavior) since the underlying devices come online and offline dynamically — different tabs hitting different domains will likely show different public IPs.
 
-Some IP-reputation-based detection systems (such as reCAPTCHA) can detect rotating pool traffic patterns and penalize them, regardless of how clean the individual exit IPs are. On the other hand, residential proxies tend to be a stronger choice against fingerprint-heavy vendors where detection focuses on the browser and behavioral layer rather than the network layer. Residential proxies also offer richer geo-targeting (country, state, city, ZIP, ASN) compared to ISP.
+Some IP-reputation-based detection systems (such as reCAPTCHA) can detect rotating proxy-pool traffic patterns and penalize them, regardless of how clean the individual exit IPs are. On the other hand, residential proxies tend to be a stronger choice against fingerprint-heavy vendors where detection focuses on the browser and behavioral layer rather than the network layer. Residential proxies also offer richer geo-targeting (country, state, city, ZIP, ASN) compared to ISP.
 
 ### Datacenter proxies
 

diff --git a/browsers/chrome-policies.mdx b/browsers/chrome-policies.mdx
@@ -9,7 +9,7 @@ Keys are Chrome policy names and values are the corresponding settings. The same
 
 ## Setting chrome policies on a pool
 
-Pass a `chrome_policy` object when [creating](/browsers/pools/overview#create-a-pool-of-reserved-browsers) or [updating](/browsers/pools/overview#update-a-pool) a pool.
+Pass a `chrome_policy` object when [creating](/browsers/pools#create-a-browser-pool) or [updating](/browsers/pools#update-a-browser-pool) a pool.
 
 <CodeGroup>
 ```typescript Typescript/Javascript

diff --git a/browsers/curl.mdx b/browsers/curl.mdx
@@ -157,9 +157,9 @@ func main() {
 
 Browser curl concurrency is constrained by Chromium's internal networking limits:
 
-- **HTTP/1.x (direct)** — About 6 sockets per host group and up to 256 active sockets per pool.
+- **HTTP/1.x (direct)** — About 6 sockets per host group and up to 256 active sockets per connection pool.
 - **Proxied chains** — On the order of tens of sockets per proxy chain (Chromium clamps configured values into a bounded range).
 - **HTTP stream pool** — Similar per-group and per-pool behavior to HTTP/1.x direct connections.
 - **HTTP/2** — Roughly 100 concurrent streams per session initially, updated from the server's `SETTINGS_MAX_CONCURRENT_STREAMS`, with an upper cap in Chromium (on the order of 256).
 
-If you're issuing many parallel curls from one browser, you're sharing those pools with navigation, XHR, and other session traffic. Latency may vary, as Chromium may queue requests when it reaches its limits.
+If you're issuing many parallel curls from one browser, you're sharing those connection pools with navigation, XHR, and other session traffic. Latency may vary, as Chromium may queue requests when it reaches its limits.
diff --git a/browsers/extensions.mdx b/browsers/extensions.mdx
@@ -52,7 +52,7 @@ The response includes the extension's ID, name, size, and timestamps.
 Passing the extension name or ID to the `create` method will load it into the browser.
 
 <Info>
-    Loading an extension into a browser triggers a Chromium restart, which can take several seconds. Use [browser pools](/browsers/pools/overview) to access browsers with extensions faster.
+    Loading an extension into a browser triggers a Chromium restart, which can take several seconds. Use [browser pools](/browsers/pools) to access browsers with extensions faster.
 </Info>
 
 

diff --git a/browsers/live-view.mdx b/browsers/live-view.mdx
@@ -88,7 +88,7 @@ connect-src https://*.onkernel.com:8443
 Kiosk mode provides a fullscreen live view experience without browser UI elements like the address bar and tabs. You can enable kiosk mode when creating a browser by setting the `kiosk_mode` parameter to `true`.
 
 <Info>
-    Kiosk mode triggers a Chromium restart, which can take several seconds. Use [browser pools](/browsers/pools/overview) to access kiosk mode browsers faster.
+    Kiosk mode triggers a Chromium restart, which can take several seconds. Use [browser pools](/browsers/pools) to access kiosk mode browsers faster.
 </Info>
 
 <CodeGroup>

diff --git a/browsers/performance.mdx b/browsers/performance.mdx
@@ -11,7 +11,7 @@ Kernel browsers [benchmark](https://www.kernel.sh/benchmarks) as the fastest, mo
 | P99 | 105ms | April 24, 2026 |
 
 ### Troubleshooting latency
-If you're experiencing slower-than-expected browser creation (or [browser pool acquisition](/browsers/pools/overview)), review your configuration for the following:
+If you're experiencing slower-than-expected browser creation (or [browser pool acquisition](/browsers/pools)), review your configuration for the following:
 
 1. App code ⇔ Kernel browser region
 
@@ -23,11 +23,11 @@ Kernel enforces [rate limits](/info/pricing#rate-limiting) on browser creation b
 
 3. Non-default browser configurations
 
-Certain browser configurations trigger Chromium to restart, which can take several seconds. Use [browser pools](/browsers/pools/overview) to access browsers with custom configurations faster. The following configurations cause browser restarts, as well as disrupt active CDP connections:
+Certain browser configurations trigger Chromium to restart, which can take several seconds. Use [browser pools](/browsers/pools) to access browsers with custom configurations faster. The following configurations cause browser restarts, as well as disrupt active CDP connections:
 - Custom viewport configurations
 - Chrome extensions
 - Setting the live view to `kiosk mode`
 
 4. Browser pool refill rate
 
-Browser pools fill at a [specified rate](https://www.kernel.sh/docs/api-reference/browser-pools/create-a-browser-pool#body-fill-rate-per-minute). Read about browser pool lifecycle best practices [here](/browsers/pools/overview#how-browser-pools-work).
+Browser pools fill at a [specified rate](https://www.kernel.sh/docs/api-reference/browser-pools/create-a-browser-pool#body-fill-rate-per-minute). Read about browser pool lifecycle best practices [here](/browsers/pools#how-browser-pools-work).
-Original file line number
+Diff line change
@@ Expand Up @@
     Passing the extension name or ID to the `create` method will load it into the browser.
     <Info>
-        Loading an extension into a browser triggers a Chromium restart, which can take several seconds. Use [browser pools](/browsers/pools/overview) to access browsers with extensions faster.
+        Loading an extension into a browser triggers a Chromium restart, which can take several seconds. Use [browser pools](/browsers/pools) to access browsers with extensions faster.
     </Info>
@@ Expand Down @@