Merge pull request #5475 from EnterpriseDB/docs/ba/fix/DOCS-278-ba-pg…

…d-known-issues-list-leadership-election-cha

DOCS-278 and DOCS-262

product_docs/docs/biganimal/release/known_issues/known_issues_pgd.mdx

@@ -39,18 +39,12 @@ This cannot be changed, either at initialization or after the cluster is created
 
 ## Replication
 
-### A PGD replication slot may fail to transition cleanly from disconnect to catch up 
-As part of fault injection testing with PGD on BigAnimal, you may decide to delete VMs. 
-Your cluster will recover if you do so, as expected. 
-However, if you're testing in a bring-your-own-account (BYOA) deployment, in some cases, as the cluster is recovering, a replication slot may remain disconnected. 
-This will persist for a few hours until the replication slot recovers automatically.  
-
 ### Replication speed is slow during a large data migration
 During a large data migration, when migrating to a PGD cluster, you may experience a replication rate of 20 MBps. 
 
 ### PGD leadership change on healthy cluster
 PGD clusters that are in a healthy state may experience a change in PGD node leadership, potentially resulting in failover. 
-No intervention is needed as a new leader will be appointed.  
+The client applications will need to reconnect when a leadership change occurs.
 
 ### Extensions which require alternate roles are not supported
 Where an extension requires a role other than the default role (`streaming_replica`) used for replication, it will fail when attempting to replicate.