Acrolinx cleanup

Author: DCtheGeek

articles/governance/policy/concepts/definition-structure.md

@@ -6,7 +6,12 @@ ms.topic: conceptual
 ---
 # Azure Policy definition structure
 
-Azure Policy establishes conventions for resources. Policy definitions describe resource compliance [conditions](#conditions) and the effect to take if a condition is met. A condition compares a resource property [field](#fields) to a required value. Resource property fields are accessed by using [aliases](#aliases). A resource property field is either a single-valued field or an [array](#understanding-the--alias) of multiple values. Condition evaluation is different on arrays. Learn more about [conditions](#conditions).
+Azure Policy establishes conventions for resources. Policy definitions describe resource compliance
+[conditions](#conditions) and the effect to take if a condition is met. A condition compares a
+resource property [field](#fields) to a required value. Resource property fields are accessed by
+using [aliases](#aliases). A resource property field is either a single-valued field or an
+[array](#understanding-the--alias) of multiple values. Condition evaluation is different on arrays.
+Learn more about [conditions](#conditions).
 
 By defining conventions, you can control costs and more easily manage your resources. For example,
 you can specify that only certain types of virtual machines are allowed. Or, you can require that
@@ -74,8 +79,9 @@ are:
 - `all`: evaluate resource groups and all resource types
 - `indexed`: only evaluate resource types that support tags and location
 
-For example, resource `Microsoft.Network/routeTables` supports tags and location and would be evaluated in both modes.
-However, resource `Microsoft.Network/routeTables/routes` cannot be tagged, and would not be evaluated in `Indexed` mode.
+For example, resource `Microsoft.Network/routeTables` supports tags and location and is evaluated in
+both modes. However, resource `Microsoft.Network/routeTables/routes` can't be tagged isn't evaluated
+in `Indexed` mode.
 
 We recommend that you set **mode** to `all` in most cases. All policy definitions created through
 the portal use the `all` mode. If you use PowerShell or Azure CLI, you can specify the **mode**
@@ -312,9 +318,9 @@ are case-insensitive. Case-insensitive alternatives are available in **matchInse
 **notMatchInsensitively**. For examples, see
 [Allow several name patterns](../samples/allow-multiple-name-patterns.md).
 
-In an **\[\*\] alias** array field value, every element in the
-array is evaluated individually, with logical AND between elements. For more information, see
-[Evaluating the \[\*\] alias](../how-to/author-policies-for-arrays.md#evaluating-the--alias).
+In an **\[\*\] alias** array field value, each element in the array is evaluated individually with
+logical **and** between elements. For more information, see [Evaluating the \[\*\]
+alias](../how-to/author-policies-for-arrays.md#evaluating-the--alias).
 
 ### Fields
 

articles/governance/policy/how-to/author-policies-for-arrays.md

@@ -163,9 +163,9 @@ expression. To resolve this error message, change `equals` to either `in` or `no
 
 Aliases that have **\[\*\]** attached to their name indicate the **type** is an _array_. Instead of
 evaluating the value of the entire array, **\[\*\]** makes it possible to evaluate each element of
-the array individually, with logical AND between them. There are three standard scenarios this per 
-item evaluation is useful in: _None_, _Any_, or _All_ elements match.
-For complex scenarios, use [count](../concepts/definition-structure.md#count).
+the array individually, with logical AND between them. There are three standard scenarios this per
+item evaluation is useful in: _None_, _Any_, or _All_ elements match. For complex scenarios, use
+[count](../concepts/definition-structure.md#count).
 
 The policy engine triggers the **effect** in **then** only when the **if** rule evaluates as true.
 This fact is important to understand in context of the way **\[\*\]** evaluates each individual