diff --git a/modules/machine-api-overview.adoc b/modules/machine-api-overview.adoc
index c72728932c..59755ea166 100644
--- a/modules/machine-api-overview.adoc
+++ b/modules/machine-api-overview.adoc
@@ -38,16 +38,16 @@ deletes it, and, on supported platforms, makes a new machine.
 `ClusterAutoscaler`:: This resource is based on the upstream
 link:https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler[ClusterAutoscaler]
 project. In the {product-title} implementation, it is integrated with the
-Cluster API by extending the `MachineSet` API.
-////
-`ClusterAutoscalerOperator`:: Instead of interacting with the `ClusterAutoscaler`
-itself, you use its Operator. The `ClusterAutoscalerOperator` manages
-the `ClusterAutoscaler` deployment. With this Operator, you can set cluster-wide
-scaling limits for resources such as cores, nodes, memory, and GPU.
+Cluster API by extending the `MachineSet` API. You can set cluster-wide
+scaling limits for resources such as cores, nodes, memory, GPU,
 and so on. You can set the priority so that the cluster prioritizes pods so that
 new nodes are not brought online for less important pods. You can also set the
 ScalingPolicy so you can scale up nodes but not scale them down.
 ////
+`ClusterAutoscalerOperator`:: Instead of interacting with the `ClusterAutoscaler`
+itself, you use its Operator. The `ClusterAutoscalerOperator` manages
+the `ClusterAutoscaler` deployment.
+////
 
 
 In {product-title} version 3.11, you could not roll out a multi-zone architecture easily because the cluster