Merge pull request #267149 from steved0x/patch-1

Update cache-how-to-monitor.md - small typo

Author: prmerger-automator[bot]

articles/azure-cache-for-redis/cache-how-to-monitor.md

@@ -119,7 +119,7 @@ Under normal conditions, **Average** and **Max** are similar because only one no
 
 Generally, **Average** shows you a smooth chart of your desired metric and reacts well to changes in time granularity. **Max** and **Min** can hide large changes in the metric if the time granularity is large but can be used with a small time granularity to help pinpoint exact times when large changes occur in the metric.
 
-The types **Count** and **“Sum** can be misleading for certain metrics (connected clients included). Instead, we suggest you look at the **Average** metrics and not the **Sum** metrics.
+The types **Count** and **Sum** can be misleading for certain metrics (connected clients included). Instead, we suggest you look at the **Average** metrics and not the **Sum** metrics.
 
 > [!NOTE]
 > Even when the cache is idle with no connected active client applications, you might see some cache activity, such as connected clients, memory usage, and operations being performed. The activity is normal in the operation of cache.