diff --git a/content/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/_index.md b/content/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/_index.md
index 952cd721134..dc96db26d41 100644
--- a/content/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/_index.md
+++ b/content/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/_index.md
@@ -131,7 +131,12 @@ deployment "rancher" successfully rolled out
 
 This option uses `cert-manager` to automatically request and renew [Let's Encrypt](https://letsencrypt.org/) certificates. This is a free service that provides you with a valid certificate as Let's Encrypt is a trusted CA. This configuration uses HTTP validation (`HTTP-01`) so the load balancer must have a public DNS record and be accessible from the internet.
 
-- Set `hostname` to the public DNS record, set `ingress.tls.source` to `letsEncrypt`, `letsEncrypt.email` to the email address used for communication about your certificate (for example, expiry notices), and `letsEncrypt.ingress.class` to whatever your ingress controlller is (`traefik`, `nginx`, `haproxy`).
+In the following command,
+
+- Set `hostname` to the public DNS record that resolves to your load balancer.
+- Set `ingress.tls.source` to `letsEncrypt`.
+- Set `letsEncrypt.email` to the email address used for communication about your certificate (for example, expiry notices).
+- Set `letsEncrypt.ingress.class` to whatever your ingress controller is, e.g., `traefik`, `nginx`, `haproxy`, etc.
 - If you are installing an alpha version, Helm requires adding the `--devel` option to the command. 
 
 ```