Merge pull request #295461 from b-ahibbard/metrics

metrics clean up

Author: prmerger-automator[bot]

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

@@ -10,7 +10,7 @@ ms.author: anfdocs
 ---
 # Metrics for Azure NetApp Files
 
-Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume IOPS, and latency. By analyzing these metrics, you can gain a better understanding on the usage pattern and volume performance of your NetApp accounts.  
+Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume I/OPS, and latency. By analyzing these metrics, you can gain a better understanding on the usage pattern and volume performance of your NetApp accounts.  
 
 ## Definitions 
 
@@ -166,10 +166,10 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
 
 - *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 hasn't yet been reached.
+    Throughput limit reached is a boolean metric that denotes the volume is hitting its QoS limits. If the metric displays 1, the volume has reached its 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.
+     > The Throughput limit reached metrics is collected every 5 minutes. If the limit has been reached in the five-minute window, it means the limit has been reached in that window. 
     
     If the volume is hitting the throughput limit, it's not sized appropriately for the application's demands. To resolve throughput issues:
 
@@ -189,7 +189,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
 ## Performance metrics for volumes
 
 > [!NOTE] 
-> Volume latency for *Average Read Latency* and *Average Write Latency* is measured within the storage service and does not include network latency.
+> Volume latency for *Average Read Latency* and *Average Write Latency* is measured within the storage service and doesn't include network latency.
 
 - *Average Read Latency*   
     The average roundtrip time (RTT) for reads from the volume in milliseconds.
@@ -199,9 +199,11 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
     The number of read operations to the volume per second.
 - *Write IOPS*   
     The number of write operations to the volume per second.
-- ***Other IOPS*** 
+- *Other IOPS* 
+
     The number of [other operations](#about-storage-performance-operation-metrics) to the volume per second. 
-- *Total IOPS* 
+- *Total IOPS*
+
     A sum of the write, read, and other operations to the volume per second. 
 
 ## <a name="replication"></a>Volume replication metrics
@@ -220,7 +222,7 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
     Lag time is the actual amount of time the replication lags behind the source. It indicates the age of the replicated data in the destination volume relative to the source volume.
 
 > [!NOTE]
-> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume will not catch up to the source. To resolve this issue, adjust the replication speed or the replication schedule. 
+> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume won't catch up to the source. To resolve this issue, adjust the replication speed or the replication schedule. 
 
 - *Volume replication last transfer duration*   
     The amount of time in seconds it took for the last transfer to complete. 
@@ -246,41 +248,52 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
 ## Throughput metrics for volumes   
 
 * *Read throughput*   
+
     Read throughput in bytes per second.
 
 * *Total throughput*   
     Sum of all throughput in bytes per second.
 
 * *Write throughput*    
+
     Write throughput in bytes per second.
 
 * *Other throughput*   
+
     Other throughput (that isn't read or write) in bytes per second.
 
 * *Total throughput*
+
     Sum of all throughput (read, write, and other) in bytes per second.
 
 ## Volume backup metrics  
 
 * *Is Volume Backup Enabled*   
+
     Shows whether backup is enabled for the volume. `1` is enabled. `0` is disabled.
 
 * *Is Volume Backup Operation Complete*   
+
     Shows whether the last volume backup or restore operation is successfully completed.  `1` is successful. `0` is unsuccessful.
 
 * *Is Volume Backup Suspended*   
-    Shows whether the backup policy is suspended for the volume.  `1` isn't suspended. `0` is suspended.
+
+    Shows whether the backup policy is suspended for the volume. A value of  `1` means it's not suspended. A value of `0` means it's suspended.
 
 * *Volume Backup Bytes*   
+
     The total bytes backed up for this volume.
 
 * *Volume Backup Last Transferred Bytes*   
+
     The total bytes transferred for the last backup or restore operation.  
 
 * *Volume Backup Operation Last Transferred Bytes*   
+
     Total bytes transferred for last backup operation.
 
 * *Volume Backup Restore Operation Last Transferred Bytes*   
+
     Total bytes transferred for last backup restore operation.
 
 ## Cool access metrics