Update how-to-managed-cluster-autoscale.md

Author: meenasaravanan02

articles/service-fabric/how-to-managed-cluster-autoscale.md

@@ -17,8 +17,9 @@ ms.date: 10/25/2021
 * Only [Azure Monitor published metrics](../azure-monitor/essentials/metrics-supported.md) are supported.
 
 >[!NOTE] 
-> Autoscale of the node type is done based on the managed cluster VMSS CPU host metrics. 
-> VMSS resource is autoresolved in the template. 
+> If using an OS Image "-with-containers” memory metrics from Azure Monitor will not be available. 
+
+
 A common scenario where autoscaling is useful is when the load on a particular service varies over time. For example, a service such as a gateway can scale based on the amount of resources necessary to handle incoming requests. Let's take a look at an example of what those scaling rules could look like and we'll use them later in the article:
 * If all instances of my gateway are using more than 70% on average, then scale the gateway service out by adding two more instance. Do this every 30 minutes, but never have more than twenty instances in total.
 * If all instances of my gateway are using less than 40% cores on average, then scale the service in by removing one instance. Do this every 30 minutes, but never have fewer than three instances in total.
@@ -30,7 +31,8 @@ This example will walk through:
 * Adding autoscale rules to the secondary node type, `NT2`.
 
 >[!NOTE] 
-> If using an OS Image "-with-containers” memory metrics from Azure Monitor will not be available.
+> Autoscale of the node type is done based on the managed cluster VMSS CPU host metrics. 
+> VMSS resource is autoresolved in the template. 
 
 
 The following will take you step by step through setup of a cluster with autoscale configured.