PM feedback

Author: curtand

articles/active-directory/enterprise-users/groups-dynamic-rule-streamline.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: enterprise-users
 ms.workload: identity
 ms.topic: overview
-ms.date: 03/25/2022
+ms.date: 03/29/2022
 ms.author: curtand
 ms.reviewer: jordandahl
 ms.custom: it-pro
@@ -26,58 +26,53 @@ The team for Azure Active Directory (Azure AD) sees numerous incidents related t
 
 Minimize the usage of the 'match' operator in rules as much as possible. Instead, explore if it's possible to use the `contains`, `startswith`, or `-eq` operators. Considering using other properties that allow you to write rules to select the users you want to be in the group without using the `-match` operator. For example, if you want a rule for the group for all users whose city is Lagos, then instead of using rules like:
 
-```powershell
-user.city -match "ago" or user.city -match ".*?ago.*"
-```
+- `user.city -match "ago"`
+- `user.city -match ".*?ago.*"`
 
 It's better to use rules like:
 
-`user.city -contains "ago,"` or
-`user.city -startswith "Lag,"` or
-best of all, `user.city -eq "Lagos"`
+- `user.city -contains "ago,"`
+- `user.city -startswith "Lag,"` 
+
+Or, best of all:
+
+- `user.city -eq "Lagos"`
 
 ## Use fewer OR operators
 
 In your rule, identify when it uses various values for the same property linked together with `-or` operators. Instead, use the `-in` operator to group them into a single criterion to make the rule easier to evaluate. For example, instead of having a rule like this:
 
-```powershell
+```
 (user.department -eq "Accounts" -and user.city -eq "Lagos") -or 
 (user.department -eq "Accounts" -and user.city -eq "Ibadan") -or 
 (user.department -eq "Accounts" -and user.city -eq "Kaduna") -or 
 (user.department -eq "Accounts" -and user.city -eq "Abuja") -or 
 (user.department -eq "Accounts" -and user.city -eq "Port Harcourt")
 ```
 
-it's better to have a rule like this:
+It's better to have a rule like this:
+
+- `user.department -eq "Accounts" -and user.city -in ["Lagos", "Ibadan", "Kaduna", "Abuja", "Port Harcourt"]`
 
-```powershell
-user.department -eq "Accounts" -and user.city -in ["Lagos", "Ibadan", "Kaduna", "Abuja", "Port Harcourt"]
-```
 
 Conversely, identify similar sub criteria with the same property not equal to various values, that are linked with `-and` operators. Then use the `-notin` operator to group them into a single criterion to make the rule easier to understand and evaluate. For example, instead of using a rule like this:
 
-```powershell
-(user.city -ne "Lagos") -and (user.city -ne "Ibadan") -and (user.city -ne "Kaduna") -and (user.city -ne "Abuja") -and (user.city -ne "Port Harcourt")
-```
+- `(user.city -ne "Lagos") -and (user.city -ne "Ibadan") -and (user.city -ne "Kaduna") -and (user.city -ne "Abuja") -and (user.city -ne "Port Harcourt")`
 
 It's better to use a rule like this:
 
-```powershell
-user.city -notin ["Lagos", "Ibadan", "Kaduna", "Abuja", "Port Harcourt"]
-```
+- `user.city -notin ["Lagos", "Ibadan", "Kaduna", "Abuja", "Port Harcourt"]`
 
 ## Avoid redundant criteria
 
 Ensure that you aren't using redundant criteria in your rule. For example, instead of using a rule like this:
 
-```powershell
-user.city -eq "Lagos" or user.city -startswith "Lag"
-```
+- `user.city -eq "Lagos" or user.city -startswith "Lag"`
+
 It's better to use a rule like this:
 
-```powershell
-user.city -startswith "Lag"
-```
+- `user.city -startswith "Lag"`
+
 
 ## Next steps