From dbbe03ca96f04b1d7629a6d99692567685f8a161 Mon Sep 17 00:00:00 2001
From: jpgouin <jeanphilippe.gouin@suse.com>
Date: Tue, 25 Feb 2025 10:56:45 +0100
Subject: [PATCH] Update README.md

Co-authored-by: Enrico Candino <enrico.candino@gmail.com>
---
 README.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index d5fb191b..20300c78 100644
--- a/README.md
+++ b/README.md
@@ -94,15 +94,15 @@ To create a new K3k cluster, use the following command:
 ```bash
 k3kcli cluster create mycluster
 ```
-> [!NOTE] 
-> Creating a K3k Cluster from a host cluster accessed through Rancher
+> [!NOTE] Creating a K3k Cluster on a Rancher-Managed Host Cluster
 >
->If your host cluster is accessed throught **Rancher**
->    (e.g the `server` value in the `kubeconfig` looks like `server: "https://<rancher_url>/k8s/clusters/abc"`.).
-> 
->Then use the `--kubeconfig-server` flag while creating the cluster so that the generated kubeconfig use the proper endpoint.
-> 
->`k3kcli cluster create --kubeconfig-server <host_node_ip/host_lb_ip> mycluster`
+> If your *host* Kubernetes cluster is managed by Rancher (e.g., your kubeconfig's `server` address includes a Rancher URL), use the `--kubeconfig-server` flag when creating your K3k cluster:
+>
+>```bash
+>k3kcli cluster create --kubeconfig-server <host_node_IP_or_load_balancer_IP> mycluster
+>```
+>
+> This ensures the generated kubeconfig connects to the correct endpoint.
 
 When the K3s server is ready, `k3kcli` will generate the necessary kubeconfig file and print instructions on how to use it.