NVIDIA · miyoungc · Jun 2, 2026 · Jun 2, 2026
diff --git a/docs/about/ecosystem-hermes.mdx b/docs/about/ecosystem-hermes.mdx
@@ -3,7 +3,7 @@
 # SPDX-License-Identifier: Apache-2.0
 title: "Ecosystem"
 sidebar-title: "Ecosystem"
-description: "How Hermes, OpenShell, and NemoClaw form one stack, where NemoClaw sits, what it adds beyond a DIY OpenShell deployment, and when to use the reference integration versus OpenShell alone."
+description: "How Hermes, OpenShell, and NemoClaw form one stack, where NemoClaw sits, what it adds beyond a custom OpenShell deployment, and when to use the reference integration versus OpenShell alone."
 description-agent: "Explains how Hermes, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond integrating OpenShell yourself, and when to prefer NemoHermes versus OpenShell. Use when users ask about Hermes, OpenShell, and NemoClaw together, or when to use NemoClaw versus OpenShell for Hermes."
 keywords: ["nemoclaw ecosystem", "hermes agent", "nemohermes", "nemoclaw vs openshell", "run hermes openshell sandbox"]
 content:
@@ -12,11 +12,11 @@ content:
 NemoClaw provides onboarding, lifecycle management, and Hermes operations within OpenShell containers.
 Use the `nemohermes` CLI alias when you work from the Hermes agent guide; it is equivalent to `nemoclaw` with the Hermes agent pre-selected.
 
-This page describes how the ecosystem is formed across projects, where NemoClaw sits relative to [OpenShell](https://github.com/NVIDIA/OpenShell) and [Hermes](https://hermes-agent.nousresearch.com/docs/), and how to choose between NemoHermes and OpenShell alone.
+This page describes how these projects form the ecosystem, where NemoClaw sits relative to [OpenShell](https://github.com/NVIDIA/OpenShell) and [Hermes](https://hermes-agent.nousresearch.com/docs/), and how to choose between NemoHermes and OpenShell alone.
 
 ## How the Stack Fits Together
 
-There are three pieces in a NemoClaw for Hermes deployment: Hermes, OpenShell, and NemoClaw, each with a distinct scope.
+A NemoClaw for Hermes deployment combines three pieces with distinct scopes: Hermes, OpenShell, and NemoClaw.
 The following diagram shows how they fit together.
 
 ```mermaid
@@ -60,18 +60,18 @@ The difference is who owns the integration work.
 
 | Path | What it means |
 |------|---------------|
-| **NemoClaw path** | You adopt the reference stack. NemoClaw's Hermes blueprint encodes a hardened image, default policies, and orchestration so `nemohermes onboard` can stand up a known-good Hermes-on-OpenShell setup with less custom glue. |
+| **NemoClaw path** | You adopt the reference stack. NemoClaw's Hermes blueprint encodes a hardened image, default policies, and orchestration so `nemohermes onboard` can create a known-good Hermes-on-OpenShell setup with less custom glue. |
 | **OpenShell path** | You use OpenShell as the platform and supply your own container, Hermes install steps, policy YAML, provider setup, and any host bridges. OpenShell stays the sandbox and policy engine; nothing requires NemoClaw's blueprint or CLI. |
 
-## What NemoClaw Adds Beyond DIY OpenShell
+## What NemoClaw Adds Beyond Custom OpenShell
 
 You can run Hermes inside OpenShell without NemoClaw by building your own image, writing policy YAML, registering providers, and wiring inference routes yourself.
 That path is valid when you need full control over the container layout.
 
 NemoClaw builds on OpenShell with additional security hardening, automation, and lifecycle tooling for Hermes.
-The following table compares DIY OpenShell integration with `nemohermes onboard`.
+The following table compares custom OpenShell integration with `nemohermes onboard`.
 
-| Capability | DIY OpenShell + Hermes | `nemohermes onboard` |
+| Capability | Custom OpenShell + Hermes | `nemohermes onboard` |
 |---|---|---|
 | Sandbox isolation | Yes, when you apply OpenShell seccomp, Landlock, network namespace isolation, and no-new-privileges enforcement through your policy. | Yes. NemoClaw applies these through the blueprint and layers a Hermes-specific restrictive policy on top. |
 | Credential handling | You create OpenShell providers manually with `openshell provider create` and configure placeholder resolution at egress. | NemoClaw creates OpenShell providers during onboarding and filters sensitive host environment variables from the sandbox creation command to reduce accidental leakage through build args. |
@@ -94,9 +94,9 @@ Use the following table to decide when to use NemoHermes versus OpenShell alone.
 | You are standardizing on the NVIDIA reference for always-on Hermes agents with policy and inference routing. | NemoClaw (`nemohermes`) |
 | You are building internal platform abstractions where the NemoClaw CLI or blueprint is not the right fit. | OpenShell (and your orchestration) |
 
-## Related topics
+## Related Topics
 
-- [Overview](overview) contains what NemoClaw is, capabilities, benefits, and use cases.
+- [Overview](overview) describes what NemoClaw is, including capabilities, benefits, and use cases.
 - [How It Works](how-it-works) describes how NemoClaw runs, the blueprint, sandbox creation, routing, and protection layers for Hermes.
 - [Architecture](../reference/architecture) shows the repository structure and technical diagrams.
 - [Quickstart with Hermes](../get-started/quickstart-hermes) installs NemoClaw and launches your first Hermes sandbox.
diff --git a/docs/about/ecosystem.mdx b/docs/about/ecosystem.mdx
@@ -11,11 +11,11 @@ content:
 ---
 NemoClaw provides onboarding, lifecycle management, and OpenClaw operations within OpenShell containers.
 
-This page describes how the ecosystem is formed across projects, where NemoClaw sits relative to [OpenShell](https://github.com/NVIDIA/OpenShell) and [OpenClaw](https://openclaw.ai), and how to choose between NemoClaw and OpenShell.
+This page describes how these projects form the ecosystem, where NemoClaw sits relative to [OpenShell](https://github.com/NVIDIA/OpenShell) and [OpenClaw](https://openclaw.ai), and how to choose between NemoClaw and OpenShell.
 
 ## How the Stack Fits Together
 
-There are three pieces that are put together in a NemoClaw for OpenClaw deployment: OpenClaw, OpenShell, and NemoClaw, each with a distinct scope.
+A NemoClaw for OpenClaw deployment combines three pieces with distinct scopes: OpenClaw, OpenShell, and NemoClaw.
 The following diagram shows how they fit together.
 
 ```mermaid
@@ -59,7 +59,7 @@ The difference is who owns the integration work.
 
 | Path | What it means |
 |------|---------------|
-| **NemoClaw path** | You adopt the reference stack. NemoClaw's blueprint encodes a hardened image, default policies, and orchestration so `nemoclaw onboard` can stand up a known-good OpenClaw-on-OpenShell setup with less custom glue. |
+| **NemoClaw path** | You adopt the reference stack. NemoClaw's blueprint encodes a hardened image, default policies, and orchestration so `nemoclaw onboard` can create a known-good OpenClaw-on-OpenShell setup with less custom glue. |
 | **OpenShell path** | You use OpenShell as the platform and supply your own container, install steps for OpenClaw, policy YAML, provider setup, and any host bridges. OpenShell stays the sandbox and policy engine; nothing requires NemoClaw's blueprint or CLI. |
 
 ## What NemoClaw Adds Beyond the OpenShell Community Sandbox
@@ -77,7 +77,7 @@ The following table compares the two paths.
 | Credential handling | OpenShell's provider system replaces real credentials with placeholder tokens in the sandbox environment. The L7 proxy resolves placeholders to real values at egress. You create providers manually with `openshell provider create`. | NemoClaw creates OpenShell providers automatically during onboarding. It also filters sensitive host environment variables (provider API keys, `DISCORD_BOT_TOKEN`, `SLACK_BOT_TOKEN`, `TELEGRAM_BOT_TOKEN`) from the sandbox creation command to prevent accidental leakage through build args. |
 | Image hardening | The community image includes standard system tools for general-purpose use. | NemoClaw strips build toolchains (`gcc`, `g++`, `make`) and network probes (`netcat`) from the runtime image to reduce attack surface. |
 | Filesystem policy | The community sandbox bundles a policy for OpenClaw. | NemoClaw defines a targeted read-only and read-write layout. System paths (`/usr`, `/lib`, `/etc`) are read-only. The agent's home directory (`/sandbox`) and config directory (`/sandbox/.openclaw`) are writable by default so the agent can manage config, install skills, and write to standard paths natively. |
-| Inference setup | The community sandbox includes an `openclaw-start` script that runs OpenClaw's onboarding wizard inside the sandbox. You can also create providers and configure OpenShell inference routing manually from the host. | NemoClaw's onboarding wizard validates your credential from the host, lets you select a provider (NVIDIA Endpoints, OpenAI, Anthropic, Google Gemini, Ollama, and compatible endpoints), and configures OpenShell's inference routing automatically. Credentials stay on the host and are delivered through OpenShell's provider system. |
+| Inference setup | The community sandbox includes an `openclaw-start` script that runs OpenClaw's onboarding wizard inside the sandbox. You can also create providers and configure OpenShell inference routing manually from the host. | NemoClaw's onboarding wizard validates your credential from the host, lets you select a provider (NVIDIA Endpoints, OpenAI, Anthropic, Google Gemini, Ollama, and compatible endpoints), and configures OpenShell's inference routing automatically. Credentials stay on the host, and OpenShell's provider system delivers them. |
 | Channel messaging | OpenShell provides the credential provider system and L7 proxy that delivers channel tokens securely (including path-based resolution for Telegram's `/bot<token>/` URL pattern). You create providers and configure OpenClaw's channel settings manually. | NemoClaw automates channel setup during onboarding: it collects bot tokens, registers them as OpenShell providers, and bakes OpenClaw channel config with placeholder tokens that OpenShell's proxy resolves at egress. No separate bridge process runs on the host. |
 | Blueprint versioning | No blueprint. The community sandbox uses whatever image version is currently published. | NemoClaw downloads the blueprint artifact, checks version compatibility, and verifies its digest before applying. Running `nemoclaw onboard` on different machines produces the same sandbox. |
 | State migration | Not included. | NemoClaw migrates agent state across machines with credential stripping and integrity verification. |
@@ -94,8 +94,8 @@ Use the following table to decide when to use NemoClaw versus OpenShell.
 | You are standardizing on the NVIDIA reference for always-on assistants with policy and inference routing. | NemoClaw |
 | You are building internal platform abstractions where the NemoClaw CLI or blueprint is not the right fit. | OpenShell (and your orchestration) |
 
-## Related topics
+## Related Topics
 
-- [Overview](overview) contains what NemoClaw is, capabilities, benefits, and use cases.
-- [How It Works](how-it-works) describes how NemoClaw runs, plugin, blueprint, sandbox creation, routing, protection layers.
+- [Overview](overview) describes what NemoClaw is, including capabilities, benefits, and use cases.
+- [How It Works](how-it-works) describes how NemoClaw runs, including the plugin, blueprint, sandbox creation, routing, and protection layers.
 - [Architecture](../reference/architecture) shows the repository structure and technical diagrams.
diff --git a/docs/about/how-it-works.mdx b/docs/about/how-it-works.mdx
@@ -47,7 +47,7 @@ For repository layout, file paths, and deeper diagrams, see [Architecture](../re
 
 ## Design Principles
 
-NemoClaw architecture follows the following principles.
+NemoClaw follows these architecture principles.
 
 Versioned blueprint
 : Host-side orchestration uses a versioned blueprint and runner that can evolve on its own release cadence.
@@ -60,8 +60,7 @@ Supply chain safety
 : Blueprint artifacts are immutable, versioned, and digest-verified before execution.
 
 OpenShell-backed lifecycle
-: NemoClaw orchestrates OpenShell resources under the hood, but <AgentCli /> onboard
-  is the supported operator entry point for creating or recreating NemoClaw-managed sandboxes.
+: NemoClaw orchestrates OpenShell resources under the hood, but <AgentCli /> onboard is the supported operator entry point for creating or recreating NemoClaw-managed sandboxes.
 
 Reproducible setup
 : Running setup again recreates the sandbox from the same blueprint and policy definitions.
@@ -79,7 +78,7 @@ NemoClaw is split into integration pieces on the host and in the sandbox image:
 </AgentOnly>
 <AgentOnly variant="hermes">
 
-- _Hermes runtime configuration_ is written into `/sandbox/.hermes` during onboarding, including `config.yaml`, environment files, and platform adapter settings for supported messaging channels.
+- NemoClaw writes Hermes runtime configuration into `/sandbox/.hermes` during onboarding, including `config.yaml`, environment files, and platform adapter settings for supported messaging channels.
 
 </AgentOnly>
 - The _blueprint_ is a versioned YAML package with the sandbox image, policy, inference profile, and supporting assets.

diff --git a/docs/about/overview.mdx b/docs/about/overview.mdx
@@ -16,7 +16,7 @@ import { AgentCli, AgentOnly } from "../_components/AgentGuide";
 NVIDIA NemoClaw is an open-source reference stack for running always-on AI agents more safely inside OpenShell containers.
 NemoClaw provides onboarding, lifecycle management, and agent operations for supported runtimes in OpenShell sandboxes.
 It incorporates policy-based privacy and security guardrails, giving you control over your agents' behavior and data handling.
-This enables self-evolving agents to run more safely in clouds, on-prem, RTX PCs, and DGX Spark.
+These controls help self-evolving agents run more safely in clouds, on-premises environments, RTX PCs, and DGX Spark.
 
 NemoClaw pairs hosted models on inference providers or local endpoints with a hardened sandbox, routed inference, and declarative egress policy so deployment stays safer and more repeatable.
 The sandbox runtime comes from [NVIDIA OpenShell](https://github.com/NVIDIA/OpenShell).
@@ -50,15 +50,15 @@ NemoClaw provides the following benefits to mitigate these risks.
 
 | Benefit                    | Description                                                                                                            |
 |----------------------------|------------------------------------------------------------------------------------------------------------------------|
-| Sandboxed execution        | Every agent runs inside an OpenShell sandbox with Landlock, seccomp, and network namespace isolation. No access is granted by default. |
-| Routed inference           | Model traffic is routed through the OpenShell gateway to your selected provider, transparent to the agent. You can switch providers or models. Refer to [Inference Options](../inference/inference-options).          |
-| Declarative network policy | Egress rules are defined in YAML. Unknown hosts are blocked and surfaced to the operator for approval.                 |
+| Sandboxed execution        | Every agent runs inside an OpenShell sandbox with Landlock, seccomp, and network namespace isolation. The sandbox grants no access by default. |
+| Routed inference           | The OpenShell gateway routes model traffic to your selected provider, transparent to the agent. You can switch providers or models. Refer to [Inference Options](../inference/inference-options).          |
+| Declarative network policy | YAML defines egress rules. OpenShell blocks unknown hosts and surfaces them to the operator for approval.                 |
 | Single CLI                 | The <AgentCli /> command orchestrates the full stack: gateway, sandbox, inference provider, and network policy.           |
 | Blueprint lifecycle        | Versioned blueprints handle sandbox creation, digest verification, and reproducible setup.                             |
 
 ## Use Cases
 
-You can use NemoClaw for various use cases including the following.
+You can use NemoClaw for use cases such as the following.
 
 | Use Case                  | Description                                                                                  |
 |---------------------------|----------------------------------------------------------------------------------------------|

diff --git a/docs/about/release-notes.mdx b/docs/about/release-notes.mdx
@@ -9,7 +9,9 @@ keywords: ["nemoclaw release notes", "nemoclaw changelog"]
 content:
   type: "reference"
 ---
-NVIDIA NemoClaw is available in early preview starting March 16, 2026. Use this page to track the highlights of the latest release. For more detailed release notes, refer to the [NemoClaw GitHub announcements](https://github.com/NVIDIA/NemoClaw/discussions/categories/announcements?discussions_q=is%3Aopen+category%3AAnnouncements).
+NVIDIA NemoClaw is available in early preview starting March 16, 2026.
+Use this page to track the highlights of the latest release.
+For more detailed release notes, refer to the [NemoClaw GitHub announcements](https://github.com/NVIDIA/NemoClaw/discussions/categories/announcements?discussions_q=is%3Aopen+category%3AAnnouncements).
 
 ## v0.0.56
 

diff --git a/docs/deployment/brev-web-ui.mdx b/docs/deployment/brev-web-ui.mdx
@@ -36,7 +36,8 @@ You do not need to install local software for this flow.
 
 ## Get Your NVIDIA API Key
 
-If you already have an NVIDIA API key skip this section. Otherwise, follow these steps to generate a new key:
+If you already have an NVIDIA API key, skip this section.
+Otherwise, follow these steps to generate a new key:
 
 1. Go to [build.nvidia.com](https://build.nvidia.com).
 2. Sign in or create an account.
@@ -55,7 +56,7 @@ Use the [NemoClaw Brev launchable](https://brev.nvidia.com/launchable/deploy/now
 2. Review the instance type, cloud provider, and estimated hourly cost on the NemoClaw setup page.
 3. Click **Deploy NemoClaw**.
 
-The right-side deployment panel shows progress while Brev deploys the CPU instance and prepares VM mode.
+The deployment panel on the right shows progress while Brev deploys the CPU instance and prepares VM mode.
 Keep this page open until the deployment completes.
 When the panel shows the **NemoClaw** button, click it to open the agent setup page.
 
@@ -104,7 +105,8 @@ Click **Chat With Agent** to open the OpenClaw dashboard.
 <Note>
 The dashboard might initially show a **Pairing required** warning.
 This means the gateway is still completing pairing in the background.
-Wait for about a few minutes for pairing to finish automatically. Refresh the dashboard to see if the warning is resolved and the connection is established.
+Wait a few minutes for pairing to finish automatically.
+Refresh the dashboard to check whether the warning has cleared and the dashboard has connected.
 If pairing does not finish, go to the **Overview** page in the OpenClaw UI, find the **Gateway Access** panel, and click **Connect**.
 </Note>
 
@@ -117,7 +119,7 @@ Hello! What can you do for me? What skills do you have available?
 ```
 
 The agent reads its workspace files and introduces itself.
-The starter workspace includes example skills such as:
+The starter workspace includes these example skills:
 
 - **Weather** gets current weather and forecasts.
 - **Healthcheck** runs security audit and hardening checks.