diff --git a/debugging/error-codes.mdx b/debugging/error-codes.mdx
index dfb34850..c6016c4d 100644
--- a/debugging/error-codes.mdx
+++ b/debugging/error-codes.mdx
@@ -150,11 +150,11 @@ This reference documents PowerSync error codes organized by component, with trou
 - **PSYNC_S1146**:
   Replication slot invalidated.
   
-  The replication slot was invalidated by PostgreSQL, typically because WAL retention exceeded `max_slot_wal_keep_size` during a long-running snapshot. Increase `max_slot_wal_keep_size` on the source database, then either redeploy your Sync Config or delete the existing replication slot to recover. PowerSync will create a new slot and restart replication automatically.
+  Postgres invalidated the replication slot, typically because WAL retention exceeded `max_slot_wal_keep_size` during a long-running snapshot. To recover, increase `max_slot_wal_keep_size` on the source database, then either redeploy your Sync Config or delete the existing replication slot. PowerSync creates a new slot and restarts replication automatically.
   
-Other causes: `rows_removed` (catalog rows needed by the slot were removed), `wal_level_insufficient`, or `idle_timeout`. 
-
-`idle_timeout` is a PostgreSQL 18+ slot invalidation, in this case increase `idle_replication_slot_timeout` instead of `max_slot_wal_keep_size`.
+  Other causes: `rows_removed` (catalog rows needed by the slot were removed), `wal_level_insufficient`, or `idle_timeout`.
+  
+  `idle_timeout` is a PostgreSQL 18+ slot invalidation. In this case, increase `idle_replication_slot_timeout` instead of `max_slot_wal_keep_size`.
   
   See [Managing and Monitoring Replication Lag](/maintenance-ops/production-readiness-guide#managing-and-monitoring-replication-lag) for guidance on sizing `max_slot_wal_keep_size`.