updated geting started

Author: EdB-MSFT

articles/azure-monitor/autoscale/autoscale-best-practices.md

@@ -2,7 +2,7 @@
 title: Best practices for autoscale
 description: Autoscale patterns in Azure for Web Apps, Virtual Machine Scale sets, and Cloud Services
 ms.topic: conceptual
-ms.date: 04/22/2022
+ms.date: 09/13/2022
 ms.subservice: autoscale
 ms.reviewer: riroloff
 ---

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

@@ -70,14 +70,14 @@ T1|3|1250|417|Scale in|2|
 
 In this case, it looks like autoscale isn't working since no scale event takes place. Check the *Run history* tab on the autoscale setting page to see if there's any flapping.
 
-:::image type="content" source="./media/autoscale-flapping/autoscale-flapping-runhistory-small.png" alt-text="A screenshot showing the autoscale run history tab with records showing flapping" lightbox="./media/autoscale-flapping/autoscale-flapping-runhistory.png":::
+:::image type="content" source="./media/autoscale-flapping/autoscale-flapping-runhistory.png" alt-text="A screenshot showing the autoscale run history tab with records showing flapping" lightbox="./media/autoscale-flapping/autoscale-flapping-runhistory.png":::
 
 Setting an adequate margin between thresholds avoids the above scenario. For example,
 
 * Scale out when thread count >=600
 * Scale in when thread count < 400
 
-:::image type="content" source="./media/autoscale-flapping/autoscale-flapping-example3.png" alt-text="A screenshot showing autoscale rules configured for the example" lightbox:::
+:::image type="content" source="./media/autoscale-flapping/autoscale-flapping-example3.png" alt-text="A screenshot showing autoscale rules configured for the example with scale out when thread count >=600 and scale in when thread count < 400" lightbox:::
 
 If the scale-in thread count is 400, the total thread count would have to drop to below 1200 before a scale event would take place. See the table below.
 

articles/azure-monitor/autoscale/autoscale-get-started.md

@@ -120,7 +120,7 @@ You can make changes in JSON directly, if necessary. These changes will be refle
 
 ### Cool-down period effects
 
-Autoscale uses a cool-down period to prevent "flapping," which is the rapid, repetitive up-and-down scaling of instances. For more information, see [Autoscale evaluation steps](autoscale-understanding-settings.md#autoscale-evaluation). For other valuable information on flapping and understanding how to monitor the autoscale engine, see [Autoscale best practices](autoscale-best-practices.md#choose-the-thresholds-carefully-for-all-metric-types) and [Troubleshooting autoscale](autoscale-troubleshoot.md), respectively.
+Autoscale uses a cool-down period to prevent "flapping," which is the rapid, repetitive up-and-down scaling of instances. For more information, see [Autoscale evaluation steps](autoscale-understanding-settings.md#autoscale-evaluation). For other valuable information on flapping and understanding how to monitor the autoscale engine, see [Flapping in Autoscale](azure/azure-monitor/autoscale/autoscale-flapping) and [Troubleshooting autoscale](autoscale-troubleshoot.md), respectively.
 
 ## Route traffic to healthy instances (App Service)