docs/manage-sandboxes/runtime-controls.md (3)

81-81: ⚡ Quick win

Avoid colon-as-punctuation in prose lines.

The colons in “Raise shields: ...” and “Lower shields: ...” are clause separators, not list introducers; rewrite with a period or comma.

As per coding guidelines, "Colons should only introduce a list. Flag colons used as general punctuation between clauses."

Also applies to: 94-94

🤖 Prompt for AI Agents

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

In `@docs/manage-sandboxes/runtime-controls.md` at line 81, Change the prose
headings that use a colon as clause separator—specifically the lines beginning
with "Raise shields:" and "Lower shields:"—to use a period or comma instead
(e.g., "Raise shields. Lock `openclaw.json`..." or "Raise shields, lock
`openclaw.json`...") so the colon is only used to introduce lists per the style
guideline; update both occurrences referenced by the "Raise shields" and "Lower
shields" phrases.

---

52-55: 💤 Low value

Remove routine bold emphasis in table values (LLM pattern detected).

**Locked at creation** and similar emphasis here reads as stylistic emphasis rather than a UI label or warning.

As per coding guidelines, "Unnecessary bold on routine instructions ... should be flagged. Bold is reserved for UI labels, parameter names, and genuine warnings."

🤖 Prompt for AI Agents

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

In `@docs/manage-sandboxes/runtime-controls.md` around lines 52 - 55, In the
runtime-controls table remove the unnecessary Markdown bold markup around
routine status values (e.g. change "**Locked at creation**" and similar
occurrences to plain text "Locked at creation" and remove bold from "Runtime
(operator-only)") so the entries read as neutral labels; keep bold only for
genuine UI labels or warnings such as parameter names like `--name` or command
examples like `nemoclaw <name> shields up`/`shields down`, and update the table
cells for "Filesystem layout (Landlock zones, read-only mounts, container
caps)", "Sandbox name", "GPU passthrough enable / device selector", and "Shields
posture (locked ↔ default mutable)" accordingly.

---

37-38: ⚡ Quick win

Use active voice and present tense consistently.

These lines include passive/future constructions (for example, “is baked,” “is initiated,” “are hidden,” “Recorded...,” “will surface”); rewrite in active, present-tense voice addressing the reader directly.

As per coding guidelines, "Active voice required... Second person ('you')... Present tense. Flag future tense ('will') in descriptions of current behavior."

Also applies to: 63-67, 104-104, 108-108

🤖 Prompt for AI Agents

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

In `@docs/manage-sandboxes/runtime-controls.md` around lines 37 - 38, Rewrite the
two sentences to use active voice, present tense, and address the reader in
second person; specifically change "NemoClaw applies its security posture in
three layers — what is baked into the sandbox image at onboard, what is
hot-reloadable on the running sandbox, and what requires a rebuild or
re-onboard." to something like "NemoClaw enforces security across three layers:
settings you bake into the sandbox image when you onboard, settings you
hot-reload on a running sandbox, and settings that require you to rebuild or
re-onboard." and change "The table below maps each commonly changed item to the
layer that owns it and the command that changes it." to an active, present-tense
instruction such as "Use the table below to find which layer owns each commonly
changed item and which command you run to change it." Also update the similar
passive/future phrases identified elsewhere (e.g., "is baked", "is initiated",
"are hidden", "Recorded...", "will surface" and the ranges noted) to active,
present-tense second-person phrasing throughout.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

docs/manage-sandboxes/runtime-controls.md (3)

109-109: ⚡ Quick win

Use present tense instead of future tense.

"shields status will surface..." should be present-tense phrasing.

As per coding guidelines, "Present tense. Flag future tense ('will') in descriptions of current behavior."

🤖 Prompt for AI Agents

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

In `@docs/manage-sandboxes/runtime-controls.md` at line 109, The sentence uses
future tense ("`shields status` will surface the inconsistency on the next
check"); change it to present tense by replacing "will surface" with "surfaces"
so the line reads: "If the timer process is killed before the deadline (e.g.
host reboot), `shields status` surfaces the inconsistency on the next check (see
`#3112` for the fail-open fix)." Update the sentence containing `shields status`
and the reference to `#3112` accordingly.

---

52-54: 💤 Low value

Avoid bold for routine table states (LLM pattern detected).

**Locked at creation** reads like emphasis rather than a warning/UI label.

As per coding guidelines, "Unnecessary bold on routine instructions ... Bold is reserved for UI labels, parameter names, and genuine warnings."

🤖 Prompt for AI Agents

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

In `@docs/manage-sandboxes/runtime-controls.md` around lines 52 - 54, The table
currently uses markdown bold for the routine state string "**Locked at
creation**" in rows like "Filesystem layout (Landlock zones, read-only mounts,
container caps)", "Sandbox name", and "GPU passthrough enable / device
selector"; remove the bold markup and replace it with plain text "Locked at
creation" (or a UI-label-safe format if needed) so the state reads as a regular
instruction rather than emphasized UI/warning text, ensuring only true UI labels
or warnings remain bolded.

---

67-67: ⚡ Quick win

Use active voice for this sentence.

"The commands are hidden..." is passive; rewrite with an active subject.

As per coding guidelines, "Active voice required. Flag passive constructions."

🤖 Prompt for AI Agents

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

In `@docs/manage-sandboxes/runtime-controls.md` at line 67, Replace the passive
sentence "The commands are hidden from the standard `--help` output because they
are operator workflows, not developer workflows; everything below documents the
full surface." with an active-voice version (for example: "We hide the commands
from the standard `--help` output because they are operator workflows, not
developer workflows; everything below documents the full surface.") so the
sentence uses a clear subject and active verb.