diff --git a/content/rancher/v2.x/en/installation/ha/helm-init/_index.md b/content/rancher/v2.x/en/installation/ha/helm-init/_index.md
index 73cfec3a0e6..1377e477c35 100644
--- a/content/rancher/v2.x/en/installation/ha/helm-init/_index.md
+++ b/content/rancher/v2.x/en/installation/ha/helm-init/_index.md
@@ -23,9 +23,14 @@ kubectl create clusterrolebinding tiller \
   --serviceaccount=kube-system:tiller
 
 helm init --service-account tiller
-```
 
-> **Users in China:** The latest version of tiller image queries a specific address (i.e. `https://dev.aliyun.com/detail.html?spm=5176.1972343.2.18.ErFNgC&repoId=62085`). In order to initialize tiller, you'll need to specify a specific tiller image. `helm init --service-account tiller  --tiller-image registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:<tag>`
+# Note: If you are in China, you'll need to specify a specific tiller-image in order to initialize tiller. 
+# The list of tiller image tags are available here: https://dev.aliyun.com/detail.html?spm=5176.1972343.2.18.ErFNgC&repoId=62085. 
+# When initializing tiller, you'll need to pass in --tiller-image
+
+helm init --service-account tiller |
+--tiller-image registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:<tag>
+```
 
 > **Note:** This `tiller` install has full cluster access, which should be acceptable if the cluster is dedicated to Rancher server. Check out the [helm docs](https://docs.helm.sh/using_helm/#role-based-access-control) for restricting `tiller` access to suit your security requirements.