diff --git a/docs/cli/onboard.md b/docs/cli/onboard.md
index 8408d7d3437..8494367a293 100644
--- a/docs/cli/onboard.md
+++ b/docs/cli/onboard.md
@@ -181,12 +181,14 @@ openclaw onboard --non-interactive \
     When an auth choice implies a preferred provider, onboarding prefilters the default-model and allowlist pickers to that provider. For Volcengine and BytePlus, this also matches the coding-plan variants (`volcengine-plan/*`, `byteplus-plan/*`).
 
     If the preferred-provider filter yields no loaded models yet, onboarding falls back to the unfiltered catalog instead of leaving the picker empty.
+
   </Accordion>
   <Accordion title="Web-search follow-ups">
     Some web-search providers trigger provider-specific follow-up prompts:
 
     - **Grok** can offer optional `x_search` setup with the same `XAI_API_KEY` and an `x_search` model choice.
     - **Kimi** can ask for the Moonshot API region (`api.moonshot.ai` vs `api.moonshot.cn`) and the default Kimi web-search model.
+
   </Accordion>
   <Accordion title="Other behaviors">
     - Local onboarding DM scope behavior: [CLI setup reference](/start/wizard-cli-reference#outputs-and-internals).
diff --git a/docs/install/updating.md b/docs/install/updating.md
index f4d44b9b32f..2916791de1c 100644
--- a/docs/install/updating.md
+++ b/docs/install/updating.md
@@ -108,6 +108,7 @@ bun add -g openclaw@latest
     OpenClaw treats packaged global installs as read-only at runtime, even when the global package directory is writable by the current user. Bundled plugin runtime dependencies are staged into a writable runtime directory instead of mutating the package tree. This keeps `openclaw update` from racing with a running gateway or local agent that is repairing plugin dependencies during the same install.
 
     Some Linux npm setups install global packages under root-owned directories such as `/usr/lib/node_modules/openclaw`. OpenClaw supports that layout through the same external staging path.
+
   </Accordion>
   <Accordion title="Hardened systemd units">
     Set a writable stage directory that is included in `ReadWritePaths`:
@@ -118,6 +119,7 @@ bun add -g openclaw@latest
     ```
 
     If `OPENCLAW_PLUGIN_STAGE_DIR` is not set, OpenClaw uses `$STATE_DIRECTORY` when systemd provides it, then falls back to `~/.openclaw/plugin-runtime-deps`. The repair step treats that stage as an OpenClaw-owned local package root and ignores user npm prefix and global settings, so global-install npm config does not redirect bundled plugin dependencies into `~/node_modules` or the global package tree.
+
   </Accordion>
   <Accordion title="Disk-space preflight">
     Before package updates and bundled runtime-dependency repairs, OpenClaw tries a best-effort disk-space check for the target volume. Low space produces a warning with the checked path, but does not block the update because filesystem quotas, snapshots, and network volumes can change after the check. The actual npm install, copy, and post-install verification remain authoritative.
@@ -126,6 +128,7 @@ bun add -g openclaw@latest
     Packaged installs keep bundled plugin runtime dependencies out of the read-only package tree. On startup and during `openclaw doctor --fix`, OpenClaw repairs runtime dependencies only for bundled plugins that are active in config, active through legacy channel config, or enabled by their bundled manifest default. Persisted channel auth state alone does not trigger Gateway startup runtime-dependency repair.
 
     Explicit disablement wins. A disabled plugin or channel does not get its runtime dependencies repaired just because it exists in the package. External plugins and custom load paths still use `openclaw plugins install` or `openclaw plugins update`.
+
   </Accordion>
 </AccordionGroup>