From 45787128251c00d18dcde2785c8a1e6812cf433b Mon Sep 17 00:00:00 2001
From: davidvancina-mulesoft
 <41162967+davidvancina-mulesoft@users.noreply.github.com>
Date: Mon, 5 Jan 2026 15:13:03 -0600
Subject: [PATCH] Update ch2-clustering.adoc

I removed what appears to have been an editing error.
---
 cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc b/cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc
index fed490d92..9d351c2a6 100644
--- a/cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc
+++ b/cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc
@@ -39,7 +39,7 @@ Replica scale-out also adds additional reliability.
 Mule runtime engine (Mule) automatically distributes multiple replicas for the same application across two or more data centers for maximum reliability.
 
 When deploying your application to two or more replicas, you can distribute workloads across these instances of Mule.
-CloudHub provides the following an HTTP load balancing service that automatically distributes HTTP requests among your assigned replicas.
+CloudHub provides an HTTP load balancing service that automatically distributes HTTP requests among your assigned replicas.
 
 Batch jobs only run on a single replica at a time, and cannot be distributed across multiple replicas.
 If Mule restarts in the same deployment, the status persists and the batch continues processing.