Math correction, 20,000 instead of 2,000

Author: salramirez

articles/azure-monitor/essentials/metrics-custom-overview.md

@@ -211,7 +211,7 @@ To understand the limit of 50,000 on time series, consider the following metric:
 
 > *Server response time* with Dimensions: *Region*, *Department*, *CustomerID*
 
-With this metric, if you have 10 regions, 20 departments, and 100 customers, that gives you 10 x 20 x 100 = 2,000 time series. 
+With this metric, if you have 10 regions, 20 departments, and 100 customers, that gives you 10 x 20 x 100 = 20,000 time series. 
 
 If you have 100 regions, 200 departments, and 2,000 customers, that gives you 100 x 200 x 2,000 = 40 million time series, which is far over the limit just for this metric alone. 
 
@@ -244,4 +244,4 @@ Use custom metrics from various services:
  - [Azure virtual machine (classic)](../essentials/collect-custom-metrics-guestos-vm-classic.md)
  - [Linux virtual machine using the Telegraf agent](../essentials/collect-custom-metrics-linux-telegraf.md)
  - [REST API](./metrics-store-custom-rest-api.md)
- - [Classic cloud service](../essentials/collect-custom-metrics-guestos-vm-cloud-service-classic.md)
+ - [Classic cloud service](../essentials/collect-custom-metrics-guestos-vm-cloud-service-classic.md)