From a0aac897702c75529ad54be08d1ab74cdcb838af Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 6 Oct 2023 17:11:16 +0100 Subject: [PATCH] Update product_docs/docs/pgd/5/node_management/node_recovery.mdx Co-authored-by: Josh Heyer <63653723+josh-heyer@users.noreply.github.com> --- product_docs/docs/pgd/5/node_management/node_recovery.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/node_management/node_recovery.mdx b/product_docs/docs/pgd/5/node_management/node_recovery.mdx index 7767f45dd38..86cc535114e 100644 --- a/product_docs/docs/pgd/5/node_management/node_recovery.mdx +++ b/product_docs/docs/pgd/5/node_management/node_recovery.mdx @@ -50,7 +50,7 @@ issues arise. Don't manually remove replication slots created by PGD. If you do, the cluster becomes damaged and the node that was using the -slot must be parted from the cluster, as described in [Replication slots created by PGD](#replication-slots-created-by-pgd). +slot must be parted from the cluster, as described in [Replication slots created by PGD](replication-slots/). While a node is offline, the other nodes might not yet have received the same set of data from the offline node, so this might appear as a slight