diff --git a/product_docs/docs/pgd/5/overview/index.mdx b/product_docs/docs/pgd/5/overview/index.mdx
index b04e983e7b9..cb12aafb0ba 100644
--- a/product_docs/docs/pgd/5/overview/index.mdx
+++ b/product_docs/docs/pgd/5/overview/index.mdx
@@ -96,7 +96,10 @@ These combined mechanisms ensure continuous availability and robust disaster rec
 
 #### Connection management
 
-In PGD, connection management aims to optimize performance by reducing potential data conflicts. PGD uses a Raft-based [consensus-driven quorum](../routing/raft/04_raft_elections_in_depth/) to determine the correct connection endpoint—the write leader. This approach reduces potential data conflicts by ensuring that writes are directed to a single node. The [PGD Proxy](../routing) manages application connections, routing read-heavy queries to replicas and writes to the write leaders, thereby optimizing performance and maintaining data consistency across the distributed environment. 
+In PGD, connection management aims to optimize performance by reducing potential data conflicts.
+PGD uses a Raft-based [consensus-driven quorum](../routing/raft/04_raft_elections_in_depth/) to determine the correct connection endpoint—the write leader. 
+This approach reduces potential data conflicts by ensuring that writes are directed to a single node. 
+The [PGD Proxy](../routing) manages application connections, routing read-heavy queries to replicas and writes to the write leaders, thereby optimizing performance and maintaining data consistency across the distributed environment. 
 
 ## Architectural options and performance