edits

Author: Michael Burke

nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc

@@ -72,18 +72,18 @@ Before installing this version of the Custom Metrics Autoscaler Operator, remove
 [id="nodes-pods-autoscaling-custom-rn-2172-new-features_{context}"]
 === New features and enhancements
 
-[id="nodes-pods-autoscaling-custom-rn-2172-new-features-token_{context}"]
+[id="nodes-pods-autoscaling-custom-rn-2172-new-features-controller_{context}"]
 ==== The Keda Controller is now created upon installation of the Custom Metrics Autoscaler Operator
 
-With this update, when you install the Custom Metrics Autoscaler Operator, the installation process automatically creates the `KedaController` custom resource. The Keda Controller creates several required custom resource definitions. After installation, you can modify the KedaController` CR as needed, to modify logging, the namespaces where the Custom Metrics Autoscaler operates, and other configurations. For more information, see 
+With this update, when you install the Custom Metrics Autoscaler Operator, the installation program automatically creates the `KedaController` custom resource (CR), which creates several required custom resource definitions. Previously, you needed to manually create the `KedaController` CR. After installation, you can modify the KedaController` CR as needed, to change logging settings, the namespaces where the Custom Metrics Autoscaler operates, and other configurations. For more information, see 
 
 [id="nodes-pods-autoscaling-custom-rn-2172-new-features-token_{context}"]
 ==== Bound service account token support
 
-With this update, you can now use bound service account tokens with trigger and cluster trigger authentications the Custom Metrics Autoscaler. Bound service account tokens are audience- and time-bound, making them more secure than legacy service account tokens. 
+With this update, you can now use bound service account tokens with trigger authentications and cluster trigger authentications. Bound service account tokens are audience- and time-bound, making them more secure than legacy service account tokens. 
 
 [id="nodes-pods-autoscaling-custom-rn-2172-bugs_{context}"]
 === Bug fixes
 
-* Before this update, you were mount a volume to a Custom Metrics Autoscaler pod, because the Keda Controller did not support the `volumeMount` and `volume` parameters. With this update, the Keda Controller now supports these fields. You can inject volumes into Custom Metrics Autoscaler pods as needed. (link:https://issues.redhat.com/browse/OCPBUGS-42559[*OCPBUGS-42559*])
+* Before this update, you were unable mount a volume to a Custom Metrics Autoscaler pod, because the Keda Controller did not support the `volumeMount` and `volume` parameters. With this update, the Keda Controller now supports these fields and you can inject volumes into Custom Metrics Autoscaler pods, if needed. (link:https://issues.redhat.com/browse/OCPBUGS-42559[*OCPBUGS-42559*])