docs: audit and fix 4 pages (sentence-case headings + Related links)

docs/concepts/progress-drafts.md

@@ -26,7 +26,7 @@ Shelling...
 Use progress drafts when you want one tidy status message during tool-heavy work
 and the final answer when the turn is done.
 
-## Quick Start
+## Quick start
 
 Enable progress drafts per channel with `streaming.mode: "progress"`:
 
@@ -47,7 +47,7 @@ until work lasts at least five seconds or emits a second work event, add compact
 progress lines while useful work happens, and suppress duplicate standalone
 progress chatter for that turn.
 
-## What Users See
+## What users see
 
 A progress draft has two parts:
 
@@ -67,7 +67,7 @@ The final answer replaces the draft when possible; otherwise
 OpenClaw sends the final answer normally and cleans up or stops updating the
 draft according to the channel's transport.
 
-## Choose A Mode
+## Choose a mode
 
 `channels.<channel>.streaming.mode` controls the visible in-progress behavior:
 
@@ -88,7 +88,7 @@ Discord and Telegram, `streaming.mode: "block"` is still preview streaming, not
 normal block delivery. Use `streaming.block.enabled` or legacy
 `blockStreaming` when you want normal block replies.
 
-## Configure Labels
+## Configure labels
 
 Progress labels live under `channels.<channel>.streaming.progress`.
 
@@ -170,7 +170,7 @@ Hide the label and show only progress lines:
 }
 ```
 
-## Control Progress Lines
+## Control progress lines
 
 Progress lines are enabled by default in progress mode. They come from real run
 events: tool starts, item updates, task plans, approvals, command output, patch
@@ -265,7 +265,7 @@ With `toolProgress: false`, OpenClaw still suppresses the older standalone
 tool-progress messages for that turn. The channel stays visually quiet until the
 final answer, except for the label if one is configured.
 
-## Channel Behavior
+## Channel behavior
 
 Each channel uses the cleanest transport it supports: