From cd584b79dfe19c17ae85d3fbbbf2cf9c5bafa944 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Tue, 2 Jun 2026 12:37:55 +0000
Subject: [PATCH] docs: align heading capitalization to title case

---
 configuration/source-db/postgres-maintenance.mdx | 2 +-
 maintenance-ops/self-hosting/diagnostics.mdx     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/configuration/source-db/postgres-maintenance.mdx b/configuration/source-db/postgres-maintenance.mdx
index 4ea4a124..8c90cea3 100644
--- a/configuration/source-db/postgres-maintenance.mdx
+++ b/configuration/source-db/postgres-maintenance.mdx
@@ -34,7 +34,7 @@ select slot_name, pg_drop_replication_slot(slot_name) from pg_replication_slots
 
 Postgres prevents active slots from being dropped. If an active slot is somehow dropped while a PowerSync instance is disconnected, PowerSync will automatically recreate the slot when it reconnects and restart replication.
 
-### Recovering from an invalidated slot
+### Recovering from an Invalidated Slot
 
 A replication slot becomes invalidated when its `wal_status` is `lost`. This happens when the WAL data needed by the slot has been removed, typically because the replication lag exceeded `max_slot_wal_keep_size`.
 
diff --git a/maintenance-ops/self-hosting/diagnostics.mdx b/maintenance-ops/self-hosting/diagnostics.mdx
index 7f2d735a..02370aaa 100644
--- a/maintenance-ops/self-hosting/diagnostics.mdx
+++ b/maintenance-ops/self-hosting/diagnostics.mdx
@@ -39,7 +39,7 @@ curl -X POST http://localhost:8080/api/admin/v1/diagnostics \
   -H "Authorization: Bearer YOUR_API_TOKEN"
 ```
 
-### Response structure
+### Response Structure
 
 The response `data` object contains:
 
@@ -60,7 +60,7 @@ Each connection in `active_sync_rules.connections[]` includes:
 | `safe_wal_size` | Remaining WAL budget in bytes before the slot risks invalidation. |
 | `max_slot_wal_keep_size` | The configured `max_slot_wal_keep_size` value on the source Postgres database. |
 
-### Errors and warnings
+### Errors and Warnings
 
 Warnings and errors appear in the `errors[]` array at the sync rules level (`active_sync_rules.errors[]` or `deploying_sync_rules.errors[]`). This includes: