Improving language based on Acrolinx

Author: kainawroth

articles/azure-monitor/agents/azure-monitor-agent-data-field-differences.md

@@ -32,16 +32,18 @@ This table collects Events from the Windows Event log. There are two other table
 
 |LAW Field | Difference | Reason| Additional Information |
 |---|---|---|---|
-| UserName | MMA enriches the event with the username prior to sending the event for ingestion. AMA do not do the same enrichment. | The AMA enrichment is not yet implemented. | AMA principles dictate that the event data should remain unchanged by default. Adding and enriched field adds possible processing errors and additional cost for storage. In this case, the customer demand for the field is very high and work is underway to add the username. |
+| UserName | MMA enriches the event with the username before sending the event for ingestion. AMA doesn't do the same enrichment. | The AMA enrichment isn't implemented yet. | AMA principles dictate that the event data should remain unchanged by default. Adding and enriched field adds possible processing errors and additional costs for storage. In this case, the customer demand for the field is very high and work is underway to add the username. |
 
 ### Perf Table for Performance Counters
 
-The Perf table collects performance counters from Windows and Linux agents, offering valuable insights into the performance of hardware components, operating systems, and applications. Below are key differences in how data is reported between OMS and Azure Monitor Agent (AMA).
+The Perf table collects performance counters from Windows and Linux agents. It offers valuable insights into the performance of hardware components, operating systems, and applications. The following table shows key differences in how data is reported between OMS and Azure Monitor Agent (AMA).
 
 | LAW Field    | Difference | Reason | Additional Information |
 |--------------|------------|--------|------------------------|
-| InstanceName | Reported as **_Total** by OMS<br>Reported as **total** by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the InstanceName value is reported as **_Total** for records ingested by the OMS agent, whereas it is reported as **total** for records ingested by the Azure Monitor Agent (AMA).<br>This does not apply to records ingested by the Microsoft Monitoring Agent (MMA) on Windows. |
-| CounterValue | Is rounded to the nearest whole number by OMS but not rounded by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the CounterValue is value is rounded to the nearest whole number for records ingested by the OMS agent but not rounded for records ingested by the Azure Monitor Agent (AMA).<br>This does not apply to records ingested by the Microsoft Monitoring Agent (MMA) on Windows. |
+| InstanceName | Reported as **_Total** by OMS<br>Reported as **total** by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the InstanceName value is reported as **_Total** for records ingested by the OMS agent, whereas it's reported as **total** for records ingested by the Azure Monitor Agent (AMA).\* |
+| CounterValue | Is rounded to the nearest whole number by OMS but not rounded by AMA | | Where `ObjectName == "Logical Disk"` and `CounterName == "% Used Space"`, the CounterValue is value is rounded to the nearest whole number for records ingested by the OMS agent but not rounded for records ingested by the Azure Monitor Agent (AMA).\* |
+
+\* Doesn't apply to records ingested by the Microsoft Monitoring Agent (MMA) on Windows.
 
 ## Next steps