diff --git a/contents/docs/release-notes/1.9.mdx b/contents/docs/release-notes/1.9.mdx
index 9babdfd2..1e34fb69 100644
--- a/contents/docs/release-notes/1.9.mdx
+++ b/contents/docs/release-notes/1.9.mdx
@@ -16,7 +16,6 @@ Zero 1.9 improves query/mutation correctness and contains numerous reliability i
 ## Features
 
 - [`zero_sync_e2e_serving_lag`](/docs/otel#zerosync) measures completed replicated work from the upstream transaction commit through view-syncer poke. [`zero_replication_upstream_clock_skew`](/docs/otel#zeroreplication) tries to identify measurements biased by clock differences. ([#6312](https://github.com/rocicorp/mono/pull/6312))
-- Zero's replication-stream inbound timeout can now be [configured separately from PostgreSQL's `wal_sender_timeout`](/docs/connecting-to-postgres#wal-sender-timeout), avoiding unnecessary reconnects during long gaps in WAL output. ([#6351](https://github.com/rocicorp/mono/pull/6351), thanks [@gerardatkonvo](https://github.com/gerardatkonvo)!)
 
 ## Performance
 
@@ -71,3 +70,4 @@ Before running mutations, Zero Server fetches and caches PostgreSQL schema metad
 - [Fatal replica-writer failures now surface as replication errors and cause `zero-cache` to exit with a failure instead of silently stopping replication.](https://github.com/rocicorp/mono/pull/6326)
 - [Replication now recovers from upstream disconnects](https://github.com/rocicorp/mono/pull/6346) or [stalled PostgreSQL writes](https://github.com/rocicorp/mono/pull/6348) while flow control is blocked.
 - [Mutations from multiple tabs in the same client group are no longer skipped or sent out of order.](https://github.com/rocicorp/mono/pull/6340)
+- Zero's replication-stream inbound timeout can now be [configured separately from PostgreSQL's `wal_sender_timeout`](https://github.com/rocicorp/mono/pull/6351), avoiding unnecessary reconnects during long gaps in WAL output (thanks [@gerardatkonvo](https://github.com/gerardatkonvo)!)