From 625871b2956570ab8309b19b0c789820c4f0c1e5 Mon Sep 17 00:00:00 2001
From: TrekkieCoder <111065900+TrekkieCoder@users.noreply.github.com>
Date: Fri, 20 Oct 2023 17:44:11 +0900
Subject: [PATCH] Update ha-deploy.md

---
 docs/ha-deploy.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/ha-deploy.md b/docs/ha-deploy.md
index 33ec0030..1b9d4717 100644
--- a/docs/ha-deploy.md
+++ b/docs/ha-deploy.md
@@ -18,8 +18,8 @@ For this deployment scenario, kubernetes and loxilb are setup as follows:
 Kubernetes uses a cluster with 2 Master Nodes and 2 Worker Nodes, all the nodes use the same 192.168.80.0/24 subnet. In this scenario, loxilb will be deployed as a DaemonSet in all the master nodes. And, kube-loxilb will be deployed as Deployment.    
 
 ### Ideal for use when
-  1. Clients and end-points need to be in same-subnet.   
-  2. Clients and svc VIP need to be in same-subnet  (end-points may be in different networks).   
+  1. Clients and services need to be in same-subnet.    
+  2. End-points may or may not be in same subnet.      
   3. Simpler deployment is desired.   
       
 ### Roles and Responsiblities for kube-loxilb: