diff --git a/docs/automation/standing-orders.md b/docs/automation/standing-orders.md
index cc53d4e14bf..d5d533ca21d 100644
--- a/docs/automation/standing-orders.md
+++ b/docs/automation/standing-orders.md
@@ -27,7 +27,7 @@ This is the difference between telling your assistant "send the weekly report" e
 - You only get involved for exceptions and approvals
 - The agent fills idle time productively
 
-## How They Work
+## How they work
 
 Standing orders are defined in your [agent workspace](/concepts/agent-workspace) files. The recommended approach is to include them directly in `AGENTS.md` (which is auto-injected every session) so the agent always has them in context. For larger configurations, you can also place them in a dedicated file like `standing-orders.md` and reference it from `AGENTS.md`.
 
diff --git a/docs/pi.md b/docs/pi.md
index 6dcb12c9e05..3a5c1d9262a 100644
--- a/docs/pi.md
+++ b/docs/pi.md
@@ -135,7 +135,7 @@ directories instead of under `src/agents/tools`, for example:
 - the Telegram plugin action runtime file
 - the WhatsApp plugin action runtime file
 
-## Core Integration Flow
+## Core integration flow
 
 ### 1. Running an Embedded Agent
 
@@ -285,7 +285,7 @@ export function splitSdkTools(options: { tools: AnyAgentTool[]; sandboxEnabled:
 
 This ensures OpenClaw's policy filtering, sandbox integration, and extended toolset remain consistent across providers.
 
-## System Prompt Construction
+## System prompt construction
 
 The system prompt is built in `buildAgentSystemPrompt()` (`system-prompt.ts`). It assembles a full prompt with sections including Tooling, Tool Call Style, Safety guardrails, OpenClaw CLI reference, Skills, Docs, Workspace, Sandbox, Messaging, Reply Tags, Voice, Silent Replies, Heartbeats, Runtime metadata, plus Memory and Reactions when enabled, and optional context files and extra system prompt content. Sections are trimmed for minimal prompt mode used by subagents.
 
diff --git a/docs/tools/plugin.md b/docs/tools/plugin.md
index a3dd676bce4..fa0e03bb029 100644
--- a/docs/tools/plugin.md
+++ b/docs/tools/plugin.md
@@ -208,7 +208,7 @@ OpenClaw scans for plugins in this order (first match wins):
   app-server plugin is selected by `embeddedHarness.runtime: "codex"` or legacy
   `codex/*` model refs
 
-## Troubleshooting Runtime Hooks
+## Troubleshooting runtime hooks
 
 If a plugin appears in `plugins list` but `register(api)` side effects or hooks
 do not run in live chat traffic, check these first: