diff --git a/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md b/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md
index 09010da2d31..47449969b51 100644
--- a/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md
+++ b/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md
@@ -38,7 +38,7 @@ For RKE, RKE2 and K3s installations, you don't have to install the Ingress contr
 
 For distributions that do not include an Ingress Controller by default, like a hosted Kubernetes cluster, such as EKS, GKE, or AKS, you have to deploy an Ingress controller first. Note, that the Rancher Helm chart does not set an ingressClassName on the ingress by default. Because of this, you have to configure the Ingress controller to also watch ingresses without an ingressClassName.
 
-Examples are included in the **Amazon EKS**, **AKS** and **GKE** tutorials above.
+Examples are included in the **Amazon EKS**, **AKS**, and **GKE** tutorials above.
 
 ### CLI Tools