Merge pull request #265848 from netapp-manishc/patch-21

Update azure-netapp-files-metrics.md

Author: prmerger-automator[bot]

articles/azure-netapp-files/azure-netapp-files-metrics.md

@@ -43,7 +43,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
 
 - *Percentage Volume Consumed Size*    
     The percentage of the volume consumed, including snapshots.  
-    Aggregation metrics (for example, min, max) are not supported for percentage volume consumed size.
+    Aggregation metrics (for example, min, max) aren't supported for percentage volume consumed size.
 - *Volume Allocated Size*   
     The provisioned size of a volume
 - *Volume Quota Size*    
@@ -55,7 +55,10 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
    The size of all snapshots in a volume.  
 - *Throughput limit reached*
 
-    Throughput limit reached is a boolean metric that denotes the volume is hitting its QoS limits. The value 1 means that the volume has reached its maximum throughput, and throughput for this volume will be throttled. The value 0 means this limit has not yet been reached. 
+    Throughput limit reached is a boolean metric that denotes the volume is hitting its QoS limits. The value 1 means that the volume has reached its maximum throughput, and throughput for this volume will be throttled. The value 0 means this limit hasn't yet been reached.
+
+     > [!NOTE] 
+     > The Throughput limit reached metrics is collected every 5 minutes and is displayed as a hit if it has been collected in the last 5 minutes.
     
     If the volume is hitting the throughput limit, it's not sized appropriately for the application's demands. To resolve throughput issues: