From 83a63cb055b0baf081e1add3ea25ef18eaf0d0cd Mon Sep 17 00:00:00 2001
From: TrekkieCoder <111065900+TrekkieCoder@users.noreply.github.com>
Date: Thu, 18 Jan 2024 23:59:17 +0900
Subject: [PATCH] Fixed typo

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 77606855a..0c3ea7f29 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ Kubernetes defines many service constructs like cluster-ip, node-port, load-bala
 
 All these services are provided by load-balancers/proxies operating at Layer4/Layer7. Since Kubernetes's is highly modular,  these services can be provided by different software modules. For example, kube-proxy is used by default to provide cluster-ip and node-port services. 
 
-Service type load-balancer is usually provided by public cloud-provider(s) as a managed entity. But for on-prem and self-managed clusers, there are only a few good options available. <b>loxilb provides service type load-balancer as its main use-case</b>. loxilb can be run in-cluster or ext-to-cluster as per user need.  
+Service type load-balancer is usually provided by public cloud-provider(s) as a managed entity. But for on-prem and self-managed clusters, there are only a few good options available. <b>loxilb provides service type load-balancer as its main use-case</b>. loxilb can be run in-cluster or ext-to-cluster as per user need.  
 
 Additionally, loxilb can also support cluster-ip and node-port services, thereby providing end-to-end connectivity for Kubernetes.