Edits fixing issues

Author: Brenduns

memdocs/intune/fundamentals/whats-new.md

@@ -68,9 +68,9 @@ You can use RSS to be notified when this page is updated. For more information,
 
 We’ve begun to release new [endpoint security profile templates](../protect/endpoint-security-policy.md) that use the settings format as found in the Settings Catalog. Each new profile template includes the same settings as the older profile it replaces, while bringing the following improvements:
 
-- **Setting names match the Windows CSP name**: In most cases, each setting name in the new profiles is a mtach to the name of the CSP that the setting configures. However, in the Intune UI we’ve added spaces to that name to make the setting name easier to read. For example, a setting in the Intune UI that’s named *Allow USB Connection* configures the CSP named [AllowUSBConnection](/windows/client-management/mdm/policy-csp-connectivity#connectivity-allowusbconnection).
+- **Setting names match the Windows CSP name**: In most cases, each setting name in the new profiles is a match to the name of the CSP that the setting configures. However, in the Intune UI we’ve added spaces to that name to make the setting name easier to read. For example, a setting in the Intune UI that’s named *Allow USB Connection* configures the CSP named [AllowUSBConnection](/windows/client-management/mdm/policy-csp-connectivity#connectivity-allowusbconnection).
 
-- **Setting options align to those of the Windows CSP**: Options for settings now align directly to those options as described and supported by the Windows CSP, with one addition. The addition is that we’ve included the option of Not configured. When a setting is set to Not configured, that Intune profile does not actively manage that setting. When a profiles is    changed to go from active configuration of  setting Not configured, Intune stops actively enforcing the configuration for that setting on the device.
+- **Setting options align to those of the Windows CSP**: Options for settings now align directly to those options as described and supported by the Windows CSP, with one addition. The addition is that we’ve included the option of Not configured. When a setting is set to Not configured, that Intune profile does not actively manage that setting. When a profile is changed to go from active configuration of  setting Not configured, Intune stops actively enforcing the configuration for that setting on the device.
 
 - **Setting guidance is taken from the Windows CSP**: The information about the setting found in the Intune UI is taken directly from the Windows CSP content, with Learn more links opening the documentation for the relevant CSP, or the content page that includes that CSP. The CSP defines and manages the settings behavior.
 

memdocs/intune/protect/endpoint-security-antivirus-policy.md

@@ -144,7 +144,7 @@ The following profiles are supported for devices you manage with Intune:
 
     These CSPs for antivirus exclusion are also managed by *Microsoft Defender Antivirus* policy, which includes identical settings for exclusions. Settings from both policy types  (*Antivirus* and *Antivirus exclusions*) are subject to [policy merge](#policy-merge-for-settings), and create a super set of exclusions for applicable devices and users.
 
-  - Profile: **Windows Security experience**-  Manage the Windows Security app settings that end users can view in the Microsoft Defender Security center and the notifications they receive.
+  - Profile: **Windows Security experience** - Manage the Windows Security app settings that end users can view in the Microsoft Defender Security center and the notifications they receive.
 
     The Windows security app is used by a number of Windows security features to provide notifications about the health and security of the machine. Security app notifications include firewalls, antivirus products, Windows Defender SmartScreen, and others.
 

memdocs/intune/protect/endpoint-security-asr-policy.md

@@ -137,7 +137,7 @@ Device control profiles support policy merge for USB Device IDs. The profile set
 
 Policy merge applies to the configuration of each setting across the different profiles that apply that specific setting to a device. The result is a single list for each of the supported settings being applied to a device. For example:
 
-- Policy merge evaluates the lists of *setup classes* that were configured in each instance of *Allow hardware device installation by setup classes* that applies to a device. The into a single allowlist where any duplicate setup classes are removed.
+- Policy merge evaluates the lists of *setup classes* that were configured in each instance of *Allow hardware device installation by setup classes* that applies to a device. The lists are merged into a single allowlist where any duplicate setup classes are removed.
 
   Removal of duplicates from the list is done to remove the common source of conflicts. The combined allowlist is then delivered to the device.
 

memdocs/intune/protect/endpoint-security-asr-profile-settings.md

@@ -223,7 +223,7 @@ Supported platforms and profiles:
 
   - **Not configured** (default) – The setting returns to the Windows default, which is off and persistence is not blocked.
   - **Block** – Persistence through WMI is blocked.
-  - **Audit** – Evaluate how this rule affects your organization if its enabled (set to Block).
+  - **Audit** – Evaluate how this rule affects your organization if it's enabled (set to Block).
   - **Disable** - Turn this rule off. Persistence is not blocked.
 
   To learn more about this setting, see [Block persistence through WMI event subscription](/windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction?WT.mc_id=Portal-fx#block-persistence-through-wmi-event-subscription).