Update versioned_docs/version-2.8/how-to-guides/new-user-guides/kuber…

…netes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md
rancher · Nov 28, 2023 · 3955520 · 3955520
1 parent b4371cf
commit 3955520
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...er-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md b/...er-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md
@@ -508,7 +508,7 @@ kubectl rollout status daemonset -n kube-system aws-cloud-controller-manager
 
 ### Using Out-of-tree AWS Cloud Provider for RKE2
 
-1. [Node name conventions and other prerequisites](https://cloud-provider-aws.sigs.k8s.io/prerequisites/) must be followed for cloud provider to find the instance correctly.
+1. [Node name conventions and other prerequisities ](https://cloud-provider-aws.sigs.k8s.io/prerequisites/) must be followed so that the cloud provider can find the instance.
 
 2. Rancher managed RKE2/K3s clusters don't support configuring `providerID`. However, the engine will set the node name correctly if the following configuration is set on the provisioning cluster object: