Update instrumentation/jmx-metrics/javaagent/README.md

Co-authored-by: Jay DeLuca <[email protected]>

Author: robsunday

instrumentation/jmx-metrics/javaagent/README.md

@@ -309,13 +309,13 @@ For now, only the `lowercase` transformation is supported, other additions might
 
 ### Unit conversions
 
-Sometimes JMX attributes values are reported in units not aligned with semantic conventions.
-For example duration values are usually reported as milliseconds while semantic conventions recommend using seconds.
+Sometimes JMX attribute values are reported in units that are not aligned with semantic conventions.
+For example, duration values are usually reported as milliseconds while semantic conventions recommend using seconds.
 
-This issue can be solved by providing optional `sourceUnit` metric property together with `unit` metric property.
-`sourceUnit` defines native unit of value retrieved from JMX attribute, while `unit` defines the unit of the metric reported to the backend.
-If conversion between `sourceUnit` and `unit` is available then it is automatically applied before reporting the metric.
-If such a conversion is not available then an error is reported during JMX metrics processing.
+This issue can be solved by providing an optional `sourceUnit` metric property together with  the `unit` metric property.
+`sourceUnit` defines the native unit of value retrieved from JMX attribute, while `unit` defines the unit of the metric reported to the backend.
+If a conversion between `sourceUnit` and `unit` is available, then it is automatically applied before reporting the metric.
+If such a conversion is not available, then an error is reported during JMX metrics processing.
 
 Currently available unit conversions: