diff --git a/product_docs/docs/pgd/5/overview/basic-architecture.mdx b/product_docs/docs/pgd/5/overview/basic-architecture.mdx
index ec33b5de30c..ccc6c92eb8f 100644
--- a/product_docs/docs/pgd/5/overview/basic-architecture.mdx
+++ b/product_docs/docs/pgd/5/overview/basic-architecture.mdx
@@ -11,7 +11,7 @@ EDB Postgres Distributed (PGD) is a distributed database solution that extends P
 PGD provides data distribution with advanced conflict management, data-loss protection, high availability up to five 9’s, and throughput up to 5X faster than native logical replication.
 
 PGD is built on a multi-master foundation (Bi-directional replication, or BDR) which is then optimized for performance and availability through PGD Proxy. 
-You can run PGD without PGD proxy if you need a custom deployment better utilizing the multi-master functionality. When running without PGD Proxy, writes will be distributed amongst the nodes, replicated to one another, and conflict resolution is relied upon for maintaining consistency.
+You can run PGD without PGD proxy if you need a custom deployment better utilizing the multi-master functionality. When running without PGD Proxy, writes are distributed amongst the nodes, replicated to one another, and conflict resolution is relied upon for maintaining consistency.
 This can be more efficient depending on your architectural needs, however, PGD proxy ensures lower contention and conflict through the use of a write leader, and for each proxy instance a single endpoint automatically addresses all the data nodes in a group, removing the need for clients to round robin multi-host connection strings. 
 [Raft](https://en.wikipedia.org/wiki/Raft_(algorithm)) is implemented to help the system make important decisions, like deciding which node is the Raft election leader and which node is the write leader.