fixup

Author: geoffcline

latest/ug/automode/automode-learn-instances.adoc

@@ -67,9 +67,10 @@ The following functionality works for both Managed instances and Standard EC2 in
 
 With EKS Auto Mode, {aws} determines the image (AMI) used for your compute nodes. {aws} monitors the rollout of new EKS Auto Mode AMI versions. If you experience workload issues related to an AMI version, create a support case. For more information, see link:awssupport/latest/user/case-management.html["Creating support cases and case management",type="documentation"] in the {aws} Support User Guide.
 
-== Supported instance reference
+[#auto-supported-instances]
+== EKS Auto Mode supported instance reference
 
-EKS Auto Mode only supports certain instance types. 
+EKS Auto Mode only creates instances of supported types, and that meet a minimum size requirement. 
 
 EKS Auto Mode supports the following instance types: 
 

latest/ug/automode/create-node-pool.adoc

@@ -74,8 +74,7 @@ spec:
     memory: 1000Gi
 ----
 
-[#auto-supported-instances]
-== EKS Auto Mode Supported Instances
+== EKS Auto Mode Supported Labels
 
 EKS Auto Mode supports the following well known labels.
 
@@ -171,7 +170,7 @@ EKS Auto Mode supports the following well known labels.
 
 NOTE: EKS Auto Mode only supports certain instances, and has minimum size requirements. For more information, see <<auto-supported-instances>>.
 
-== EKS Auto Mode Not Supported
+== EKS Auto Mode Not Supported Labels
 
 EKS Auto Mode does not support the following labels. 
 

latest/ug/clusters/update-cluster.adoc

@@ -25,12 +25,9 @@ The update process consists of Amazon EKS launching new API server nodes with th
 
 To update the cluster, Amazon EKS requires up to five available IP addresses from the subnets that you specified when you created your cluster. Amazon EKS creates new cluster elastic network interfaces (network interfaces) in any of the subnets that you specified. The network interfaces may be created in different subnets than your existing network interfaces are in, so make sure that your security group rules allow <<sec-group-reqs,required cluster communication>> for any of the subnets that you specified when you created your cluster. If any of the subnets that you specified when you created the cluster don't exist, don't have enough available IP addresses, or don't have security group rules that allows necessary cluster communication, then the update can fail.
 
-[NOTE]
-====
-
 To ensure that the API server endpoint for your cluster is always accessible, Amazon EKS provides a highly available [.noloc]`Kubernetes` control plane and performs rolling updates of API server instances during update operations. In order to account for changing IP addresses of API server instances supporting your [.noloc]`Kubernetes` API server endpoint, you must ensure that your API server clients manage reconnects effectively. Recent versions of `kubectl` and the [.noloc]`Kubernetes` client https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/#programmatic-access-to-the-api[libraries] that are officially supported, perform this reconnect process transparently.
 
-====
+NOTE: To learn more about what goes into a cluster update, see link:eks/latest/best-practices/cluster-upgrades.html["Best Practices for Cluster Upgrades",type="documentation"] in the EKS Best Practices Guide. This resource helps you plan an upgrade, and understand the strategy of upgrading a cluster. 
 
 == Considerations for Amazon EKS Auto Mode