Apply editorial feedback

Author: natasha-moore-elastic

docs/management/admin/endpoint-command-ref.asciidoc

@@ -5,12 +5,12 @@ This page lists the commands for management and troubleshooting of {elastic-endp
 
 [NOTE]
 ====
-* The service is not added to the `PATH` system variable, so you must prepend the commands with the full OS-dependent path:
+* {elastic-endpoint} is not added to the `PATH` system variable, so you must prepend the commands with the full OS-dependent path:
 ** On Windows: `"C:\Program Files\Elastic\Endpoint\elastic-endpoint.exe"`
 ** On macOS: `/Library/Elastic/Endpoint/elastic-endpoint`
 ** On Linux: `/opt/Elastic/Endpoint/elastic-endpoint`
 
-* You must run the commands with elevated privileges—as the root user on POSIX systems, or as Administrator on Windows.
+* You must run the commands with elevated privileges—as the root user on Linux and macOS, or as Administrator on Windows.
 ====
 
 The following {elastic-endpoint} commands are available:
@@ -232,7 +232,7 @@ Fleet server: https://fleet.example.elastic.co:443
 [[elastic-endpoint-top-command]]
 == elastic-endpoint top
 
-Show a breakdown of the executables that triggered {elastic-endpoint} CPU usage within the last interval. This utility displays which {elastic-endpoint} features are resource-intensive for a particular executable.
+Show a breakdown of the executables that triggered {elastic-endpoint} CPU usage within the last interval. This displays which {elastic-endpoint} features are resource-intensive for a particular executable.
 
 NOTE: The meaning and output of this command are similar, but not identical, to the POSIX `top` command. The `elastic-endpoint top` command aggregates multiple processes by executable. The utilization values aren't measured by the OS scheduler but by a wall clock in user mode. The output helps identify outliers causing excessive CPU utilization, allowing you to fine-tune the {elastic-defend} policy and exception lists in your deployment.
 

docs/serverless/edr-manage/endpoint-command-ref.mdx

@@ -13,12 +13,12 @@ This page lists the commands for management and troubleshooting of ((elastic-end
 
 <DocCallOut title="Note">
 
-* The service is not added to the `PATH` system variable, so you must prepend the commands with the full OS-dependent path:
+* ((elastic-endpoint)) is not added to the `PATH` system variable, so you must prepend the commands with the full OS-dependent path:
     * On Windows: `"C:\Program Files\Elastic\Endpoint\elastic-endpoint.exe"`
     * On macOS: `/Library/Elastic/Endpoint/elastic-endpoint`
     * On Linux: `/opt/Elastic/Endpoint/elastic-endpoint`
 
-* You must run the commands with elevated privileges—as the root user on POSIX systems, or as Administrator on Windows.
+* You must run the commands with elevated privileges—as the root user on Linux and macOS, or as Administrator on Windows.
 
 </DocCallOut>
 
@@ -197,7 +197,7 @@ Fleet server: https://fleet.example.elastic.co:443
 
 ## elastic-endpoint top
 
-Show a breakdown of the executables that triggered ((elastic-endpoint)) CPU usage within the last interval. This utility displays which ((elastic-endpoint)) features are resource-intensive for a particular executable.
+Show a breakdown of the executables that triggered ((elastic-endpoint)) CPU usage within the last interval. This displays which ((elastic-endpoint)) features are resource-intensive for a particular executable.
 
 <DocCallOut title="Note">
 The meaning and output of this command are similar, but not identical, to the POSIX `top` command. The `elastic-endpoint top` command aggregates multiple processes by executable. The utilization values aren't measured by the OS scheduler but by a wall clock in user mode. The output helps identify outliers causing excessive CPU utilization, allowing you to fine-tune the ((elastic-defend)) policy and exception lists in your deployment.