Merge pull request #193968 from rboucher/patch-3

correcting  Azure Monitor autoscale branding in title

Author: PRMerger-2

articles/azure-monitor/autoscale/autoscale-troubleshoot.md

@@ -1,13 +1,13 @@
 ---
-title: Troubleshooting Azure autoscale
-description: Tracking down problems with Azure autoscaling used in Service Fabric, Virtual Machines, Web Apps, and cloud services.
+title: Troubleshooting Azure Monitor autoscale
+description: Tracking down problems with Azure Monitor autoscaling used in Service Fabric, Virtual Machines, Web Apps, and cloud services.
 ms.topic: conceptual
 ms.date: 11/4/2019
 ms.subservice: autoscale
 ---
 
 
-# Troubleshooting Azure autoscale
+# Troubleshooting Azure Monitor autoscale
 
 Azure Monitor autoscale helps you to have the right amount of resources running to handle the load on your application. It enables you to add resources to handle increases in load and also save money by removing resources that are sitting idle. You can scale based on a schedule,  fixed date-time, or resource metric you choose. For more information, see [Autoscale Overview](autoscale-overview.md).
 
@@ -202,4 +202,4 @@ Create alert rules to get notified of autoscale actions or failures. You can als
 For more information, see [autoscale resource logs](autoscale-resource-log-schema.md)
 
 ## Next steps
-Read information on [autoscale best practices](autoscale-best-practices.md).
+Read information on [autoscale best practices](autoscale-best-practices.md).