typo

Author: MandiOhlinger

memdocs/intune/configuration/settings-catalog.md

@@ -201,8 +201,8 @@ Device and user groups are used when you assign your policies. Device and user s
 
 When deploying policy from Intune, you can assign user scope or device scope to any type of target group. Behavior of the policy per user depends on the scope of the setting:
 
-- User scoped policy writes to `HKEY Current User (HKCU)`. 
-- Device scoped policy writes to `HKEY Local Machine (HKLM)`.
+- User scoped policy writes to `HKEY_CURRENT_USER (HKCU)`. 
+- Device scoped policy writes to `HKEY_LOCAL_MACHINE (HKLM)`.
 
 When a device checks-in to Intune, the device always presents a `deviceID`. The device may or may not present a `userID`, depending on the check-in timing and if a user is signed in.
 
@@ -211,7 +211,7 @@ These are some possible combinations of scope, assignment, and the expected beha
 - If a device scope policy is assigned to a device, then all users on that device have that setting applied.
 - If a user scope policy is assigned to a device, then all users on that device have that setting applied. This behavior is like a [loopback set to merge](/troubleshoot/windows-server/group-policy/loopback-processing-of-group-policy).
 - If a user scoped policy is assigned to a user, then only that user has that setting applied.
-- If a device scoped policy is assigned to a user, once that user signs in and an Intune sync occurs, then the device scope settings applies to all users on the device.
+- If a device scoped policy is assigned to a user, once that user signs in and an Intune sync occurs, then the device scope settings apply to all users on the device.
 
 If there is no [user hive](/windows/win32/sysinfo/registry-hives) during initial check-ins, then you may see some user scope settings marked as not applicable. This behavior happens in the early moments of a device before a user is present.