acrolinx fixes

Author: rpsqrd

articles/azure-arc/servers/agent-release-notes.md

@@ -20,12 +20,12 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
 
 ### New features
 
-- The agent can now be configured to operate in [monitoring mode](security-overview.md#agent-modes) which simplifies configuration of the agent for scenarios where you only want to use Arc for monitoring and security scenarios. This mode disables other agent functionality and prevents use of extensions that could make changes to the system (for example, the Custom Script Extension).
+- The agent can now be configured to operate in [monitoring mode](security-overview.md#agent-modes), which simplifies configuration of the agent for scenarios where you only want to use Arc for monitoring and security scenarios. This mode disables other agent functionality and prevents use of extensions that could make changes to the system (for example, the Custom Script Extension).
 - VMs and hosts running on Azure Stack HCI now report the cloud provider as "HCI" when [Azure benefits are enabled](/azure-stack/hci/manage/azure-benefits#enable-azure-benefits).
 
 ### Fixed
 
-- `systemd` is now an official prerequisite on Linux. This has always been the case, however the package manager is now aware of the dependency and can alert you if you try to install the agent on a system that does not support `systemd`.
+- `systemd` is now an official prerequisite on Linux and your package manger will alert you if you try to install the Azure Connected Machine agent on a server without systemd.
 - Guest configuration policies no longer create unnecessary files in the `/tmp` directory on Linux servers
 - Improved reliability when extracting extensions and guest configuration policy packages
 - Improved reliability for guest configuration policies that have child processes

articles/azure-arc/servers/security-overview.md

@@ -160,7 +160,7 @@ sudo azcmagent config set guestconfiguration.enabled true
 
 ## Agent modes
 
-A simpler way to configure local security controls for monitoring and security scenarios is to use the *monitor mode*, available with agent verison 1.18 and newer. Modes are pre-defined configurations of the extension allow lists and guest configuration agent maintained by Microsoft. As new extensions become available that enable monitoring scenarios, Microsoft will update the allow lists and agent configuration to include or exclude the new functionality, as appropriate.
+A simpler way to configure local security controls for monitoring and security scenarios is to use the *monitor mode*, available with agent version 1.18 and newer. Modes are pre-defined configurations of the extension allowlist and guest configuration agent maintained by Microsoft. As new extensions become available that enable monitoring scenarios, Microsoft will update the allowlist and agent configuration to include or exclude the new functionality, as appropriate.
 
 There are two modes to choose from:
 
@@ -179,7 +179,7 @@ You can check the current mode of the agent and allowed extensions with the foll
 azcmagent config list
 ```
 
-While in monitor mode, you cannot modify the extension allow or block list. If you need to change either list, change the agent back to full mode and specify your own allow and block lists.
+While in monitor mode, you cannot modify the extension allowlist or blocklist. If you need to change either list, change the agent back to full mode and specify your own allowlist and blocklist.
 
 To change the agent back to full mode, run the following command: