Updating to reflect frequency of stateless alert alerts

Updating metric alert rules to reflect frequency of metric alert notifications for stateless metric alerts as created by platform.

Author: jpiyali

articles/azure-monitor/alerts/alerts-troubleshoot-metric.md

@@ -113,7 +113,7 @@ Metric alerts are stateful by default, so other alerts aren't fired if there's a
 - If you create the alert rule programmatically, for example, via [Azure Resource Manager](./alerts-metric-create-templates.md), [PowerShell](/powershell/module/az.monitor/), [REST](/rest/api/monitor/metricalerts/createorupdate), or the [Azure CLI](/cli/azure/monitor/metrics/alert), set the `autoMitigate` property to `False`.
 - If you create the alert rule via the Azure portal, clear the **Automatically resolve alerts** option under the **Alert rule details** section.
 
-<sup>1</sup> For stateless metric alert rules, an alert triggers once every 10 minutes at a minimum, even if the frequency of evaluation is equal or less than 5 minutes and the condition is still being met.
+<sup>1</sup> For stateless metric alert rules, the frequency of alert notifications is derived from the frequency of alert rules. For alert rule with frequency less than 5 minutes, we can expect a notification every 1 minute to maximum 6 minutes while the alert condition is still met. For alert rule with frequency greater than or equal to 5 minutes, we can expect a notification between 1 x frequency to 2 x frequency while the alert condition is still met. For example, for an alert rule with frequency 15 minutes, we can expect a notification between 15 to 30 minutes.
 
 > [!NOTE]
 > Making a metric alert rule stateless prevents fired alerts from becoming resolved. So, even after the condition isn't met anymore, the fired alerts remain in a fired state until the 30-day retention period.