docs: normalize frontmatter titles to sentence case

docs/automation/auth-monitoring.md

@@ -1,6 +1,6 @@
 ---
 summary: "Redirect to /gateway/authentication"
-title: "Auth Monitoring"
+title: "Auth monitoring"
 ---
 
 This page moved to [Authentication](/gateway/authentication). See [Authentication](/gateway/authentication) for auth monitoring documentation.

docs/automation/cron-jobs.md

@@ -4,7 +4,7 @@ read_when:
   - Scheduling background jobs or wakeups
   - Wiring external triggers (webhooks, Gmail) into OpenClaw
   - Deciding between heartbeat and cron for scheduled tasks
-title: "Scheduled Tasks"
+title: "Scheduled tasks"
 ---
 
 # Scheduled Tasks (Cron)

docs/automation/cron-vs-heartbeat.md

@@ -1,6 +1,6 @@
 ---
 summary: "Redirect to /automation"
-title: "Cron vs Heartbeat"
+title: "Cron vs heartbeat"
 ---
 
 This page moved to [Automation & Tasks](/automation). See [Automation & Tasks](/automation) for the decision guide comparing cron and heartbeat.

docs/automation/index.md

@@ -4,7 +4,7 @@ read_when:
   - Deciding how to automate work with OpenClaw
   - Choosing between heartbeat, cron, hooks, and standing orders
   - Looking for the right automation entry point
-title: "Automation & Tasks"
+title: "Automation & tasks"
 ---
 
 OpenClaw runs work in the background through tasks, scheduled jobs, event hooks, and standing instructions. This page helps you choose the right mechanism and understand how they fit together.

docs/automation/standing-orders.md

@@ -4,7 +4,7 @@ read_when:
   - Setting up autonomous agent workflows that run without per-task prompting
   - Defining what the agent can do independently vs. what needs human approval
   - Structuring multi-program agents with clear boundaries and escalation rules
-title: "Standing Orders"
+title: "Standing orders"
 ---
 
 Standing orders grant your agent **permanent operating authority** for defined programs. Instead of giving individual task instructions each time, you define programs with clear scope, triggers, and escalation rules — and the agent executes autonomously within those boundaries.

docs/automation/taskflow.md

@@ -4,7 +4,7 @@ read_when:
   - You want to understand how Task Flow relates to background tasks
   - You encounter Task Flow or openclaw tasks flow in release notes or docs
   - You want to inspect or manage durable flow state
-title: "Task Flow"
+title: "Task flow"
 ---
 
 Task Flow is the flow orchestration substrate that sits above [background tasks](/automation/tasks). It manages durable multi-step flows with their own state, revision tracking, and sync semantics while individual tasks remain the unit of detached work.

docs/automation/tasks.md

@@ -4,7 +4,7 @@ read_when:
   - Inspecting background work in progress or recently completed
   - Debugging delivery failures for detached agent runs
   - Understanding how background runs relate to sessions, cron, and heartbeat
-title: "Background Tasks"
+title: "Background tasks"
 ---
 
 > **Looking for scheduling?** See [Automation & Tasks](/automation) for choosing the right mechanism. This page covers **tracking** background work, not scheduling it.

docs/automation/troubleshooting.md

@@ -1,6 +1,6 @@
 ---
 summary: "Redirect to /automation/cron-jobs"
-title: "Automation Troubleshooting"
+title: "Automation troubleshooting"
 ---
 
 This page moved to [Scheduled Tasks](/automation/cron-jobs#troubleshooting). See [Scheduled Tasks](/automation/cron-jobs#troubleshooting) for troubleshooting documentation.