Standardize title capitalization to sentence case across docs

Converts all Title Case headings, page titles, sidebar titles, and
navigation group names to sentence case — only the first word and
proper nouns/acronyms remain capitalized.

Author: beran-t

docs.json

@@ -23,7 +23,7 @@
         "icon": "book-open-cover",
         "groups": [
           {
-            "group": "Getting Started",
+            "group": "Getting started",
             "pages": [
               "docs",
               {
@@ -50,7 +50,7 @@
             ]
           },
           {
-            "group": "Agents in Sandbox",
+            "group": "Agents in sandbox",
             "pages": [
               "docs/agents/amp-code",
               "docs/agents/claude-code",
@@ -59,7 +59,7 @@
             ]
           },
           {
-            "group": "Code Interpreting",
+            "group": "Code interpreting",
             "pages": [
               {
                 "group": "Analyze data with AI",
@@ -173,7 +173,7 @@
             ]
           },
           {
-            "group": "MCP Gateway",
+            "group": "MCP gateway",
             "pages": [
               "docs/mcp",
               "docs/mcp/quickstart",
@@ -218,7 +218,7 @@
         ]
       },
       {
-        "anchor": "SDK Reference",
+        "anchor": "SDK reference",
         "icon": "brackets-curly",
         "href": "https://e2b.dev/docs/sdk-reference"
       }

docs.mdx

@@ -38,7 +38,7 @@ print(result.stdout)
 ```
 </CodeGroup>
 
-## E2B Building Blocks
+## E2B building blocks
 
 A quick overview of the core building blocks you'll interact with when using E2B.
 

docs/agents/amp-code.mdx

@@ -20,7 +20,7 @@ Once inside the sandbox, start AMP.
 amp
 ```
 
-## Run Headless
+## Run headless
 
 Use `-x` for non-interactive mode and `--dangerously-allow-all` to auto-approve all tool calls (safe inside E2B sandboxes). AMP uses its own API key from [ampcode.com/settings](https://ampcode.com/settings).
 
@@ -170,7 +170,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Thread Management
+## Thread management
 
 AMP persists conversations as threads that can be resumed or continued with follow-up tasks.
 
@@ -236,7 +236,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Build a Custom Template
+## Build a custom template
 
 If you need to customize the environment (e.g. pre-install dependencies, add config files), build your own template on top of the pre-built `amp-code` template.
 
@@ -295,7 +295,7 @@ python build.py
 ```
 </CodeGroup>
 
-## Related Guides
+## Related guides
 
 <CardGroup cols={3}>
   <Card title="Sandbox Persistence" icon="clock" href="/docs/sandbox/persistence">

docs/agents/claude-code.mdx

@@ -20,7 +20,7 @@ Once inside the sandbox, start Claude Code.
 claude
 ```
 
-## Run Headless
+## Run headless
 
 Use `-p` for non-interactive mode and `--dangerously-skip-permissions` to auto-approve all tool calls (safe inside E2B sandboxes).
 
@@ -111,7 +111,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Structured Output
+## Structured output
 
 Use `--output-format json` to get machine-readable responses — useful for building pipelines or extracting specific results.
 
@@ -152,7 +152,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Streaming Output
+## Streaming output
 
 Use `--output-format stream-json` to get a real-time JSONL event stream — including tool calls, token usage, and result metadata.
 
@@ -210,7 +210,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Resume a Session
+## Resume a session
 
 Claude Code persists conversations that can be resumed with follow-up tasks using `--session-id`.
 
@@ -274,7 +274,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Custom System Prompt
+## Custom system prompt
 
 Write a `CLAUDE.md` file into the sandbox for project context or use `--system-prompt` to provide task-specific instructions.
 
@@ -324,7 +324,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Connect MCP Tools
+## Connect MCP tools
 
 Claude Code has built-in support for [MCP](https://modelcontextprotocol.io/). E2B provides an [MCP gateway](/docs/mcp) that gives Claude access to 200+ tools from the [Docker MCP Catalog](https://hub.docker.com/mcp).
 
@@ -385,7 +385,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Build a Custom Template
+## Build a custom template
 
 If you need to customize the environment (e.g. pre-install dependencies, add config files), build your own template on top of the pre-built `claude` template.
 
@@ -444,7 +444,7 @@ python build.py
 ```
 </CodeGroup>
 
-## Related Guides
+## Related guides
 
 <CardGroup cols={3}>
   <Card title="MCP Tools" icon="plug" href="/docs/mcp">

docs/agents/codex.mdx

@@ -20,7 +20,7 @@ Once inside the sandbox, start Codex.
 codex
 ```
 
-## Run Headless
+## Run headless
 
 Use `codex exec` for non-interactive mode and `--full-auto` to auto-approve tool calls (safe inside E2B sandboxes). Pass `--skip-git-repo-check` to bypass git directory ownership checks inside the sandbox. Pass `CODEX_API_KEY` as an environment variable.
 
@@ -113,7 +113,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Schema-Validated Output
+## Schema-validated output
 
 Use `--output-schema` to constrain the agent's final response to a JSON Schema. This ensures the output conforms to a specific structure — useful for building reliable pipelines.
 
@@ -194,7 +194,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Streaming Events
+## Streaming events
 
 Use `--json` to get a JSONL event stream. Each line is a JSON object representing an agent event (tool calls, file changes, messages). Progress goes to stderr; events go to stdout.
 
@@ -244,7 +244,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Image Input
+## Image input
 
 Pass screenshots or design mockups with `--image` to give Codex visual context alongside the prompt.
 
@@ -292,7 +292,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Build a Custom Template
+## Build a custom template
 
 If you need to customize the environment (e.g. pre-install dependencies, add config files), build your own template on top of the pre-built `codex` template.
 
@@ -351,7 +351,7 @@ python build.py
 ```
 </CodeGroup>
 
-## Related Guides
+## Related guides
 
 <CardGroup cols={3}>
   <Card title="Sandbox Persistence" icon="clock" href="/docs/sandbox/persistence">

docs/agents/examples.mdx

@@ -1,5 +1,5 @@
 ---
 url: https://github.com/e2b-dev
-title: All Examples
+title: All examples
 icon: "github"
 ---

docs/agents/openclaw.mdx

@@ -20,7 +20,7 @@ Once inside the sandbox, start OpenClaw.
 openclaw agent --local --message "Hello"
 ```
 
-## Run Headless
+## Run headless
 
 Use `openclaw agent --message` for non-interactive mode. Pass `--local` to use API keys from environment variables and `--thinking` to control reasoning depth.
 
@@ -111,7 +111,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Structured Output
+## Structured output
 
 Use `--json` to get machine-readable responses with structured payload and metadata.
 
@@ -270,7 +270,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Add Skills
+## Add skills
 
 OpenClaw supports a [skills ecosystem](https://docs.openclaw.ai/tools/skills) via [ClawHub](https://clawhub.com). Skills are markdown files (`SKILL.md`) that extend the agent with additional tools. Install them with the `clawhub` CLI or write them directly into the workspace.
 
@@ -382,7 +382,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Launch the Gateway
+## Launch the gateway
 
 OpenClaw has a built-in [web UI and chat interface](https://openclaw.ai) served by its gateway. Start it inside a sandbox and connect from your browser.
 
@@ -426,7 +426,7 @@ print(f"Sandbox ID: {sandbox.sandbox_id}")
 ```
 </CodeGroup>
 
-## Build a Custom Template
+## Build a custom template
 
 If you need to customize the environment (e.g. pre-install dependencies, add config files), build your own template on top of the pre-built `openclaw` template.
 
@@ -495,7 +495,7 @@ python build.py
 ```
 </CodeGroup>
 
-## Related Guides
+## Related guides
 
 <CardGroup cols={3}>
   <Card title="Sandbox Persistence" icon="clock" href="/docs/sandbox/persistence">

docs/agents/opencode.mdx

@@ -20,7 +20,7 @@ Once inside the sandbox, start OpenCode.
 opencode
 ```
 
-## Run Headless
+## Run headless
 
 Use `opencode run` for non-interactive mode. Pass your LLM provider's API key as an environment variable — OpenCode supports `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GEMINI_API_KEY`, and [others](https://opencode.ai/docs/config/).
 
@@ -111,7 +111,7 @@ sandbox.kill()
 ```
 </CodeGroup>
 
-## Launch the Web UI
+## Launch the web UI
 
 OpenCode has a [built-in web interface](https://opencode.ai/docs/web/). Start it inside a sandbox and connect from your browser.
 
@@ -163,7 +163,7 @@ print(f"Sandbox ID: {sandbox.sandbox_id}")
 ```
 </CodeGroup>
 
-## Build a Custom Template
+## Build a custom template
 
 If you need to customize the environment (e.g. pre-install dependencies, add config files), build your own template on top of the pre-built `opencode` template.
 
@@ -238,7 +238,7 @@ python build.py
 ```
 </CodeGroup>
 
-## Related Guides
+## Related guides
 
 <CardGroup cols={3}>
   <Card title="Sandbox Persistence" icon="clock" href="/docs/sandbox/persistence">

docs/api-key.mdx

@@ -1,5 +1,5 @@
 ---
-title: "API Key"
+title: "API key"
 icon: "key"
 ---
 
@@ -27,15 +27,15 @@ You can get your API key at [dashboard](https://e2b.dev/dashboard?tab=keys).
 
 <br/>
 
-# Access Token
+# Access token
 
 The access token is used only in the CLI and is **not needed in the SDK**. There's no need to set it when logging into the CLI using `e2b auth login`.
 
 <Note>
 To authenticate without the browser, you can set `E2B_ACCESS_TOKEN` as an environment variable. This is useful for CI/CD pipelines.
 </Note>
 
-## Where to find Access token
+## Where to find access token
 
 You can get your **Access token key** at the [dashboard](https://e2b.dev/dashboard/account).
 

docs/byoc.mdx

@@ -1,6 +1,6 @@
 ---
-title: "BYOC (Bring Your Own Cloud)"
-sidebarTitle: Bring Your Own Cloud
+title: "BYOC (bring your own cloud)"
+sidebarTitle: Bring your own cloud
 ---
 
 BYOC (Bring Your Own Cloud) allows you to deploy E2B sandboxes to your own cloud infrastructure within your VPC.
@@ -29,7 +29,7 @@ sandbox traffic, and logs, is transmitted directly from the client to the custom
     <img src="/images/byoc-architecture-diagram.png" />
 </Frame>
 
-### BYOC Cluster Components
+### BYOC cluster components
 - **Orchestrator**: Represents a node that is responsible for managing sandboxes and their lifecycle. Optionally, it can also run the template builder component.
 - **Edge Controller**: Routes traffic to sandboxes, exposes API for cluster management, and gRPC proxy used by E2B control plane to communicate with orchestrators.
 - **Monitoring**: Collector that receives sandbox and build logs and system metrics from orchestrators and edge controllers. Only anonymized metrics are sent to the E2B Cloud for observability purposes.