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/ecosystem.md`:
- Line 89: The table cell under "Filesystem policy" contains three sentences on
one line; split them so each sentence is on its own source line to follow "one
sentence per line" guideline—edit the table row containing "Filesystem policy"
(the cell mentioning "The community sandbox bundles a policy for OpenClaw.
NemoClaw defines a targeted read-only and read-write layout. System paths...")
and break the sentences into separate lines (either by inserting <br/> tags
where appropriate or reformatting the cell so each sentence is a separate line)
while preserving the same content and meaning.

In `@docs/get-started/quickstart.md`:
- Around line 209-234: The Model Router dropdown block has mismatched MyST
directive fences: it opens with four-colon fences (::::) but closes with three
(:::); update the closing fence to match the opening (use ::::: or change the
opening to :::) so the Option 8 "Model Router" dropdown block uses consistent
fence markers (refer to the "Option 8: Model Router" dropdown and the
surrounding opening '::::' and closing ':::' markers) to restore proper MyST
parsing/rendering.

In `@docs/reference/troubleshooting.md`:
- Line 673: The paragraph starting with "Host-side `config set` validates any
HTTP or HTTPS URLs..." in docs/reference/troubleshooting.md contains multiple
sentences on one line; split that single line into four separate lines so each
sentence is on its own line: 1) "Host-side `config set` validates any HTTP or
HTTPS URLs in the new value, including URLs nested inside JSON objects or
arrays." 2) "NemoClaw rejects loopback, private, reserved, and internal hosts;
DNS names must resolve successfully and must not resolve to private/internal
addresses." 3) "HTTP URLs are written with the validated IP address pinned to
reduce DNS-rebinding risk." 4) "Avoid putting credentials in config values;
rotate provider credentials with the credential-management commands instead."
Ensure the surrounding paragraph structure is preserved.

---

Nitpick comments:
In `@docs/inference/set-up-sub-agent.md`:
- Line 79: The sentence beginning "In the default mutable state, this keeps the
local hash consistent but does not make it tamper-proof; lock the config
root-owned and read-only afterward if the sandbox should enforce config
integrity at startup." should be split into two clearer sentences: end the first
after "tamper‑proof." and start a second instructing to "lock the config
root-owned and read-only afterward if the sandbox should enforce config
integrity at startup." Update the document text accordingly to improve
readability and align with the one-sentence-per-line guideline.

In `@docs/reference/commands.md`:
- Line 237: Change the British spelling "honoured" to US spelling "honored" in
the sentence "When prompting is impossible (no TTY or `--non-interactive`), the
env var is also honoured so existing CI scripts keep working." so it reads "…the
env var is also honored…".