Reorder sidebar (Live View 1, HITL 2), fix CDP→Browser Sessions wording, add coming-soon handoff note, style fixes

Author: kathayl

src/content/docs/browser-rendering/features/custom-fonts.mdx

@@ -3,7 +3,7 @@ pcx_content_type: how-to
 title: Custom fonts
 description: Learn how to add custom fonts to Browser Rendering for use in screenshots and PDFs.
 sidebar:
-  order: 1
+  order: 3
 ---
 
 import { Tabs, TabItem } from "~/components";

src/content/docs/browser-rendering/features/human-in-the-loop.mdx

@@ -3,20 +3,22 @@ pcx_content_type: how-to
 title: Human in the Loop
 description: Temporarily hand off browser control to a human operator for authentication, sensitive actions, or tasks that are difficult to fully automate.
 sidebar:
-  order: 3
+  order: 2
   badge: Beta
 ---
 
-Some browser automation workflows require manual intervention. A login page may need multi-factor authentication, a form may require sensitive credentials you do not want to pass to an automation script, or a task may be too complex to fully automate. Human in the Loop lets you pause an automation script and hand off control to a human operator through [Live View](/browser-rendering/features/live-view/), then resume the script once the human is done.
+Some browser automation workflows require manual intervention. A login page may need multi-factor authentication, a form may require sensitive credentials you do not want to pass to an automation script, or a task may be too complex to fully automate. Human in the Loop lets a human step into a live browser session through [Live View](/browser-rendering/features/live-view/) to handle what automation cannot, then hand control back to the script.
 
 ## How it works
 
-Human in the Loop builds on [Live View](/browser-rendering/features/live-view/) and the [CDP](/browser-rendering/cdp/) endpoints:
+Human in the Loop works with any [Browser Session](/browser-rendering/#integration-methods) and uses [Live View](/browser-rendering/features/live-view/) to give humans access:
 
-1. Your automation script navigates to a page that needs human input
-2. The script retrieves the Live View URL via `Cloudflare.getLiveView` and shares it with a human operator (for example, by logging it, sending it via Slack, or displaying it in a UI)
-3. The human operator opens the Live View URL and completes the required action (logging in, solving a CAPTCHA, entering sensitive data, etc.)
-4. The automation script detects that the human is done (for example, by waiting for a navigation event or polling for a page element) and resumes
+1. Your automation script navigates to a page that needs human input.
+2. The script retrieves the Live View URL via `Cloudflare.getLiveView` and shares it with a human operator (for example, by logging it, sending it via Slack, or displaying it in a UI).
+3. The human operator opens the Live View URL and completes the required action (logging in, solving a CAPTCHA, entering sensitive data, etc.).
+4. The automation script detects that the human is done (for example, by waiting for a navigation event or polling for a page element) and resumes.
+
+A more structured handoff flow where the agent can signal that it needs help and notify a human is coming soon.
 
 ## Example: login with human assistance
 

src/content/docs/browser-rendering/features/live-view.mdx

@@ -3,15 +3,15 @@ pcx_content_type: how-to
 title: Live View
 description: View and interact with remote Browser Run sessions in real time using the hosted DevTools UI or native Chrome DevTools.
 sidebar:
-  order: 2
+  order: 1
   badge: Beta
 ---
 
 import { CURL, DashButton, Tabs, TabItem } from "~/components";
 
 Live View lets you see and interact with a remote Browser Run session in real time. This is useful for debugging automation scripts, monitoring what a browser is doing, or manually stepping in when a task requires human intervention (see [Human in the Loop](/browser-rendering/features/human-in-the-loop/)).
 
-Live View is available for any browser session created through the [CDP](/browser-rendering/cdp/) endpoints.
+Live View is available for any [Browser Session](/browser-rendering/#integration-methods), including sessions created with [Puppeteer](/browser-rendering/puppeteer/), [Playwright](/browser-rendering/playwright/), or the [CDP](/browser-rendering/cdp/) endpoints.
 
 ## How to access Live View
 
@@ -39,7 +39,7 @@ The hosted UI supports three viewing modes, controlled by the `mode` parameter i
 
 Because Browser Run speaks standard CDP, you can connect Chrome's built-in DevTools directly to a remote session. Replace the `https://live.browser.run/ui/inspector?wss=` prefix in the `devtoolsFrontendUrl` with the `devtools://` protocol:
 
-```
+```txt
 devtools://devtools/bundled/inspector.html?wss=live.browser.run/api/devtools/browser/SESSION_ID/page/TARGET_ID?jwt=...
 ```