Merge remote-tracking branch 'github/mainline' into mainline

Author: BrianS99

latest/ug/automode/automode-get-started-cli.adoc

@@ -275,7 +275,7 @@ aws eks create-cluster \
       \"accessConfig\": {
         \"authenticationMode\": \"API\"
       }
-    }
+    }"
 ----
 
 === Check Cluster Status
@@ -306,4 +306,4 @@ kubectl get nodepools
 
 == Next Steps
 
-* Learn how to <<automode-workload,deploy a sample workload>> to your new EKS Auto Mode cluster.
+* Learn how to <<automode-workload,deploy a sample workload>> to your new EKS Auto Mode cluster.

latest/ug/clusters/create-cluster.adoc

@@ -229,7 +229,7 @@ The following are optional settings that, if required, must be added to the prev
 +
 If you'd like to disable the installation of these default networking add-ons, use the parameter below. This may be used for alternate CNIs, such as Cilium. Review the link:eks/latest/APIReference/API_CreateCluster.html[EKS API reference,type="documentation"] for more information. 
 +
-`aws eks create-cluster --bootstrapSelfManagedAddons false`
+`aws eks create-cluster --no-bootstrap-self-managed-addons ...`
 ** If you want to specify which `IPv4` Classless Inter-domain Routing (CIDR) block Kubernetes assigns service IP addresses from, you must specify it by adding the `--kubernetes-network-config serviceIpv4Cidr=<cidr-block>` to the following command.
 +
 Specifying your own range can help prevent conflicts between Kubernetes services and other networks peered or connected to your VPC. Enter a range in CIDR notation. For example: `10.2.0.0/16`.

latest/ug/clusters/eks-provisioned-control-plane-introduction.adoc

@@ -224,7 +224,7 @@ the updates on the cluster to see a new update of type
 occurs. The error field in the update indicates the reason for failure.
 There are no restrictions on how frequently you can switch between
 tiers. Changing the control plane tier takes several minutes to
-complete.
+complete. There is no API server downtime during this process, as EKS brings up new API servers before terminating old ones.
 * *Selecting optimal tier* – To determine the optimal Provisioned Control Plane scaling tier for your cluster, you can perform load testing by provisioning your cluster on the highest tier (4XL). Then perform a load
 test to simulate peak demand on your cluster's control plane. Observe
 the control plane tier utilization metrics at peak load, and use these