Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/about/how-it-works.md`:
- Line 3: The page title string page: "NemoClaw Architecture Overview: Plugin,
Blueprint, and Sandbox Lifecycle" contains a colon which violates the docs title
rule; update that string to a no-colon variant (e.g., replace the colon with
"and" or split wording) so it reads something like page: "NemoClaw Architecture
Overview and Plugin, Blueprint, and Sandbox Lifecycle" (or another clear
no-colon phrasing) to satisfy the guideline; ensure you only change the title
string value.

In `@docs/about/overview.md`:
- Line 31: The docs line currently links to the third-party repo
"https://github.com/NVIDIA/OpenShell" which violates the markdown rule; remove
the hyperlink and either leave "NVIDIA OpenShell" as plain text or replace it
with a non-link reference (e.g., "NVIDIA OpenShell (project)") in the sentence
that mentions the sandbox runtime and the `nemoclaw` CLI so the prose no longer
contains an external GitHub link.
- Line 28: Update the sentence "This enables self-evolving claws to run more
safely in clouds, on prem, RTX PCs and DGX Spark." to use hyphenated "on-prem"
instead of "on prem" so it reads "This enables self-evolving claws to run more
safely in clouds, on-prem, RTX PCs and DGX Spark."; ensure only the
spacing/hyphenation is changed and no other wording is altered.

In `@docs/get-started/quickstart-hermes.md`:
- Around line 30-33: Replace the unsupported MyST admonition type "admonition"
with a supported callout such as "warning" (or "note"/"tip") in the Hermes agent
block so it conforms to the docs callout rule; specifically update the opening
tag :::{admonition} to :::{warning} (and keep the same inner text and closing
:::) so the Hermes experimental feature note uses a valid MyST admonition.

In `@docs/index.md`:
- Line 143: The sentence "To find detailed instruction on the installation
process, refer to the [Quickstart](get-started/quickstart.md) guide." uses
singular "instruction" incorrectly; update that phrase to "detailed
instructions" so the sentence reads "To find detailed instructions on the
installation process, refer to the [Quickstart](get-started/quickstart.md)
guide." and keep the rest of the sentence and link unchanged.

---

Nitpick comments:
In `@docs/about/ecosystem.md`:
- Around line 31-32: Change the passive sentence "There are three pieces that
are put together in a NemoClaw deployment: OpenClaw, OpenShell, and NemoClaw,
each with a distinct scope." to active voice by making the subject perform the
action (for example: "Three components make up a NemoClaw deployment: OpenClaw,
OpenShell, and NemoClaw, each with a distinct scope.") — update the opening
sentence in docs/about/ecosystem.md accordingly to satisfy the "Active voice
required" guideline.
- Line 31: The sentence "There are three pieces that are put together in a
NemoClaw deployment: OpenClaw, OpenShell, and NemoClaw, each with a distinct
scope." uses a colon as general punctuation; update that sentence (and the
similar lines at 64 and 66) to remove the colon and use a period or comma
structure instead (e.g., "There are three pieces that are put together in a
NemoClaw deployment. OpenClaw, OpenShell, and NemoClaw each have a distinct
scope." or "There are three pieces that are put together in a NemoClaw
deployment — OpenClaw, OpenShell, and NemoClaw — each with a distinct scope.")
so colons only introduce actual lists.

In `@docs/about/overview.md`:
- Line 23: The H1 heading currently reads "Overview of NVIDIA NemoClaw" but must
match the frontmatter key title.page ("NemoClaw Overview: What It Is"); update
the top-level H1 in this document to exactly "NemoClaw Overview: What It Is" so
the page title and H1 are identical and comply with the page-structure rule.
- Line 48: The table row containing "Messaging channels | OpenShell-managed
processes connect Telegram, Discord, Slack, and similar platforms to the
sandboxed agent. NemoClaw configures channels during onboarding; OpenShell
supplies the native constructs, credential flow, and runtime supervision."
should be split so each sentence occupies its own source line; update the cell
so one line reads "Messaging channels | OpenShell-managed processes connect
Telegram, Discord, Slack, and similar platforms to the sandboxed agent." and the
next line reads "NemoClaw configures channels during onboarding; OpenShell
supplies the native constructs, credential flow, and runtime supervision."
thereby ensuring one sentence per line while preserving the table structure and
wording (references: the "Messaging channels" table row and the NemoClaw
sentence).