writing edits

Author: curtand

articles/active-directory/enterprise-users/groups-assign-sensitivity-labels.md

@@ -75,10 +75,10 @@ To apply published labels to groups, you must first enable the feature. These st
 If you’re receiving a Request_BadRequest error, it's because the settings already exist in the tenant, so when you try to create a new property:value pair, the result is an error. In this case, take the following steps:
 
 1. Repeat steps 1-4 from [Enable sensitivity label support in PowerShell](#enable-sensitivity-label-support-in-powershell).
-1. Issue a `Get-AzureADDirectorySetting | FL` cmdlet and check the ID. If several ID values are present, use the one where you see the EnableMIPLabels property on the Values settings in step 4.
+1. Issue a `Get-AzureADDirectorySetting | FL` cmdlet and check the ID. If several ID values are present, use the one where you see the EnableMIPLabels property on the Values settings. You will need the ID in step 4.
 1. Set the EnableMIPLabels property variable as instructed: `$Setting["EnableMIPLabels"] = "True"`
-1. Do NOT issue the `New-AzureADDirectorySetting -DirectorySetting $setting` cmdlet, but instead use `Set-AzureADDirectorySetting -DirectorySetting $Setting -ID, Use the ID that you retrieved in step 2.
-1. Confirm the value has been correctly updated by issuing `$Setting.Values` again.
+1. Don;t issue the `New-AzureADDirectorySetting -DirectorySetting $setting` cmdlet, but instead use `Set-AzureADDirectorySetting -DirectorySetting $Setting -ID`. Use the ID that you retrieved in step 2.
+1. Ensure that the value is now correctly updated by issuing `$Setting.Values` again.
 
 You will also need to synchronize your sensitivity labels to Azure AD. For instructions, see [How to enable sensitivity labels for containers and synchronize labels](/microsoft-365/compliance/sensitivity-labels-teams-groups-sites#how-to-enable-sensitivity-labels-for-containers-and-synchronize-labels).