From 67956506810e0d615b70af7911c48667723db47b Mon Sep 17 00:00:00 2001
From: Trekkie <111065900+TrekkieCoder@users.noreply.github.com>
Date: Tue, 5 Nov 2024 11:47:03 +0900
Subject: [PATCH] Update https.md

---
 docs/https.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/https.md b/docs/https.md
index 3e3b2edd..85ce4af3 100644
--- a/docs/https.md
+++ b/docs/https.md
@@ -1,7 +1,7 @@
 
 # HTTPS guide for loxilb 
 
-By default loxilb uses plain loxilb for its API operation. Please refere to the arch [guide](https://docs.loxilb.io/latest/kube-loxilb/#overall-topology) for more info. This guide will detail the steps needed to enable https in both loxilb (server-mode) and kube-loxilb (client-mode). For enabling https, we need to have proper certificate and keys in place. We will use popular tool [mkcert](https://github.com/FiloSottile/mkcert) to configure locally-trusted development certificates. One could also use tools like [letsencrypt](https://letsencrypt.org) for production grade certificates. Nonetheless overall process is the same.
+By default loxilb uses plain http for its API operation. Please refere to the arch [guide](https://docs.loxilb.io/latest/kube-loxilb/#overall-topology) for more info. This guide will detail the steps needed to enable https in both loxilb (server-mode) and kube-loxilb (client-mode). For enabling https, we need to have proper certificate and keys in place. We will use popular tool [mkcert](https://github.com/FiloSottile/mkcert) to configure locally-trusted development certificates. One could also use tools like [letsencrypt](https://letsencrypt.org) for production grade certificates. Nonetheless, overall process is the same.
 
 ## Generate the certificates