Merge pull request #1223 from velkovb/patch-1

Fix typo in view-upgrade-policy.adoc

Author: srhsrhsrhsrh

latest/ug/versioning/view-upgrade-policy.adoc

@@ -15,7 +15,7 @@ You can set the version policy for both new and existing clusters, using the `su
 
 
 
-* `*STANDARD*` -- Your EKS cluster eligible for automatic upgrade at the end of standard support. You will not incur extended support charges with this setting but you EKS cluster will automatically upgrade to the next supported Kubernetes version in standard support.
+* `*STANDARD*` -- Your EKS cluster eligible for automatic upgrade at the end of standard support. You will not incur extended support charges with this setting but your EKS cluster will automatically upgrade to the next supported Kubernetes version in standard support.
 * `*EXTENDED*` -- Your EKS cluster will enter into extended support once the Kubernetes version reaches end of standard support. You will incur extended support charges with this setting. You can upgrade your cluster to a standard supported Kubernetes version to stop incurring extended support charges. Clusters running on extended support will be eligible for automatic upgrade at the end of extended support.
 
 Extended support is enabled by default for new clusters, and existing clusters. You can view if extended support is enabled for a cluster in the {aws-management-console}, or by using the {aws} CLI.  
@@ -49,4 +49,4 @@ aws eks describe-cluster \
 --name <cluster-name> \
 --query "cluster.upgradePolicy.supportType"
 ----
-. If the value is `STANDARD`, your cluster will not enter extended support. If the value is `EXTENDED`, your cluster will enter extended support.
+. If the value is `STANDARD`, your cluster will not enter extended support. If the value is `EXTENDED`, your cluster will enter extended support.