Merge pull request #223299 from AbbyMSFT/dt-troubleshoot

Dynamic thresholds troubleshooting question edit

Author: prmerger-automator[bot]

articles/azure-monitor/alerts/alerts-dynamic-thresholds.md

@@ -107,12 +107,12 @@ To identify weekly seasonality, the Dynamic Thresholds model requires at least t
 
 ## Dynamic Thresholds is showing values that are not within the range of expected values
 
-When a metric exhibits large fluctuation, Dynamic Thresholds builds a wider model around the metric values. This model can result in a lower border below zero when the metric only has positive values, or in an upper border above 100% when the metric can't exceed 100%. This scenario can happen when:
+When a metric value exhibits large fluctuations, dynamic thresholds may build a wide model around the metric values, which can result in a lower or higher boundary than expected. This scenario can happen when:
 
 - The sensitivity is set to low.
 - The metric exhibits an irregular behavior with high variance, which appears as spikes or dips in the data.
 
-When the lower bound has a negative value, it's plausible for the metric to reach a zero value given the metric's irregular behavior. Consider choosing a higher sensitivity or a larger **Aggregation granularity (Period)** to make the model less sensitive. Or, use the **Ignore data before** option to exclude a recent irregularity from the historical data used to build the model.
+Consider making the model less sensitive by choosing a higher sensitivity or selecting a larger **Aggregation granularity (Period)**.  You can also use the **Ignore data before** option to exclude a recent irregularity from the historical data used to build the model.
 
 ## The Dynamic Thresholds alert rule is too noisy or fires too much