From f7e72384bca5deb2df0d49b3e7828f9c82d99103 Mon Sep 17 00:00:00 2001
From: April M <36110273+aimurphy@users.noreply.github.com>
Date: Mon, 16 Mar 2026 13:41:22 -0700
Subject: [PATCH] DOC-5702

---
 modules/operations/pages/astream-georeplication.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/operations/pages/astream-georeplication.adoc b/modules/operations/pages/astream-georeplication.adoc
index 8ecec92..4b8c5b4 100644
--- a/modules/operations/pages/astream-georeplication.adoc
+++ b/modules/operations/pages/astream-georeplication.adoc
@@ -1,8 +1,8 @@
 = Georeplication
 
-A key feature of {pulsar-reg} is how it handles georeplication. While other pub-sub messaging systems require additional processes to mirror messages between data centers, {pulsar-short} has multi-datacenter replication as an integrated feature.
+A key feature of {pulsar-reg} is how it handles georeplication. While other pub-sub messaging systems require additional processes to mirror messages between datacenters, {pulsar-short} has multi-datacenter replication as an integrated feature.
 
-{pulsar-short}'s serving layer (brokers) and storage layer (bookies) are decoupled in {pulsar-short} architecture, allowing seamless message replication across data centers in different regions.
+{pulsar-short}'s serving layer (brokers) and storage layer (bookies) are decoupled in {pulsar-short} architecture, allowing seamless message replication across datacenters in different regions.
 
 Georeplication typically provides redundancy in the event of datacenter outages, but can also be used for any application where {pulsar-short} messages are produced and consumed across regions.