tweaks

Author: natasha-moore-elastic

docs/release-notes/8.19.asciidoc

@@ -8,15 +8,15 @@
 [discrete]
 [[enhancements-8.19.2]]
 ==== Enhancements
-* Makes {elastic-defend} malware scan queue operate more efficiently by not blocking scan requests when an oplock for the file being scanned cannot be acquired.
-* To help identify which parts of `elastic-endpoint.exe` are using a significant amount of CPU, {elastic-defend} on Windows can now include CPU profiling data in diagnostics. To request CPU profiling data via the command line, refer to the {fleet-guide}/elastic-agent-cmd-options.html#_options[Agent command reference]. To request CPU profiling data via Kibana, check the **Collect additional CPU metrics** box when requesting {agent} diagnostics.  
-* Shortens the time it takes for {elastic-defend} to recover from a DEGRADED status caused by Elastic Agent communication issues.
+* Improves {elastic-defend} malware scan queue efficiency by not blocking scan requests when an oplock for the file being scanned cannot be acquired.
+* To help identify which parts of `elastic-endpoint.exe` are using a significant amount of CPU, {elastic-defend} on Windows can now include CPU profiling data in diagnostics. To request CPU profiling data using the command line, refer to the {fleet-guide}/elastic-agent-cmd-options.html#_options[Agent command reference]. To request CPU profiling data using Kibana, check the **Collect additional CPU metrics** box when requesting {agent} diagnostics.  
+* Shortens the time it takes for {elastic-defend} to recover from a `DEGRADED` status caused by {agent} communication issues.
 * Allows {elastic-defend} to automatically recover in some situations when it loses connectivity with {agent}.
 
 [discrete]
 [[bug-fixes-8.19.2]]
 ==== Fixes
-* Due to an issue in macOS, {elastic-defend} would sometimes send network events without `user.name` populated. {elastic-defend} will now identify these events and populate `user.name` if necessary
+* Due to an issue in macOS, {elastic-defend} would sometimes send network events without `user.name` populated. {elastic-defend} will now identify these events and populate `user.name` if necessary.
 * Fixes an issue in {elastic-defend} performance metrics that resulted in `endpoint_uptime_percent` always being 0 for behavioral rules.
 
 [discrete]