Update docs/en/integrations/data-ingestion/clickpipes/postgres/faq.md

Co-authored-by: Kunal Gupta <[email protected]>

docs/en/integrations/data-ingestion/clickpipes/postgres/faq.md

@@ -188,6 +188,6 @@ max_slot_wal_keep_size = 200GB
 
 The only way to recover ClickPipe is by triggering a resync, which you can do in the Settings page.
 
-The most common cause of replication slot invalidation is a low `max_slot_wal_keep_size` setting on your PostgreSQL database (e.g., a few gigabytes). We recommend increasing this value. [Refer to this section](https://clickhouse.com/docs/en/integrations/clickpipes/postgres/faq#recommended-max_slot_wal_keep_size-settings) on tuning `max_slot_wal_keep_size`. Ideally, this should be set to at least 100GB to prevent replication slot invalidation.
+The most common cause of replication slot invalidation is a low `max_slot_wal_keep_size` setting on your PostgreSQL database (e.g., a few gigabytes). We recommend increasing this value. [Refer to this section](https://clickhouse.com/docs/en/integrations/clickpipes/postgres/faq#recommended-max_slot_wal_keep_size-settings) on tuning `max_slot_wal_keep_size`. Ideally, this should be set to at least 200GB to prevent replication slot invalidation.
 
 In rare cases, we have seen this issue occur even when `max_slot_wal_keep_size` is not configured. This could be due to an intricate and a rare bug in PostgreSQL, although the cause remains unclear.