From 9d329d23d7a81fff1f5b02fb3a5eb9074b06af60 Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Thu, 19 Oct 2023 13:27:32 -0400
Subject: [PATCH] small edits to terminology

mostly contractions
---
 product_docs/docs/pgd/5/terminology.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/product_docs/docs/pgd/5/terminology.mdx b/product_docs/docs/pgd/5/terminology.mdx
index 2f62c12b15b..5f0fde74b0d 100644
--- a/product_docs/docs/pgd/5/terminology.mdx
+++ b/product_docs/docs/pgd/5/terminology.mdx
@@ -116,11 +116,11 @@ A multi-step process for achieving consistency across multiple database nodes.
 The first phase sees a transaction prepared on an originating node and sent to
 all participating nodes. Each participating node validates that it can apply the
 transaction and signals its readiness to the originating node. This is the
-prepare phase. In the second phase, if all the participating nodes signal they
-are ready, the originating node proceeds to commit the transaction and signals
+prepare phase. In the second phase, if all the participating nodes signal they're
+ready, the originating node proceeds to commit the transaction and signals
 the participating nodes to commit, too. This is the commit phase. If, in the
-prepare phase, any node signals it is not ready, the entire transaction is
-aborted. It's this process that ensures all nodes get the same changes.
+prepare phase, any node signals it isn't ready, the entire transaction is
+aborted. This process ensures all nodes get the same changes.
 
 #### Vertical scaling or scale up