From 0446c740e075a60d93821467aa7b030484e511b9 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Thu, 5 Dec 2024 11:51:51 +0000
Subject: [PATCH] Added clarity to subscriber-only node purpose.

---
 .../docs/pgd/5/node_management/subscriber_only.mdx        | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/node_management/subscriber_only.mdx b/product_docs/docs/pgd/5/node_management/subscriber_only.mdx
index 2a2348d7604..281eda8c191 100644
--- a/product_docs/docs/pgd/5/node_management/subscriber_only.mdx
+++ b/product_docs/docs/pgd/5/node_management/subscriber_only.mdx
@@ -2,6 +2,9 @@
 title: Subscriber-only nodes and groups
 ---
 
+Subscriber-only nodes provide a means to scale up the handling of read-only
+requests in PGD. 
+
 ## Subscriber-only nodes
 
 As the name suggests, a subscriber-only node subscribes only to replication
@@ -25,7 +28,10 @@ this topology, a small number of fully active nodes are replicating changes in
 all directions. A large number of subscriber-only nodes receive only changes
 but never send any changes to any other node in the cluster. This topology
 avoids connection explosion due to a large number of nodes yet provides an
-extremely large number of `leaf` nodes that you can use to consume the data.
+extremely large number of `leaf` nodes that you can use to service a large 
+number read-only requests without adding load to the replicating cluster.
+
+
 ## Subscriber-only groups
 
 To make use of subscriber-only nodes, first create a PGD group of type