Clarify remediation scope and updating initiatives

Author: DCtheGeek

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

@@ -1,7 +1,7 @@
 ---
 title: Details of the policy definition structure
 description: Describes how policy definitions are used to establish conventions for Azure resources in your organization.
-ms.date: 11/26/2019
+ms.date: 02/26/2020
 ms.topic: conceptual
 ---
 # Azure Policy definition structure
@@ -852,6 +852,10 @@ management because you work with a group as a single item. For example, you can
 tagging policy definitions into a single initiative. Rather than assigning each policy individually,
 you apply the initiative.
 
+> [!NOTE]
+> Once an initiative is assigned, initative level parameters can't be altered. Due to this, the
+> recommendation is to set a **defaultValue** when defining the parameter.
+
 The following example illustrates how to create an initiative for handling two tags: `costCenter`
 and `productName`. It uses two built-in policies to apply the default tag value.
 
@@ -866,13 +870,15 @@ and `productName`. It uses two built-in policies to apply the default tag value.
                 "type": "String",
                 "metadata": {
                     "description": "required value for Cost Center tag"
-                }
+                },
+                "defaultValue": "DefaultCostCenter"
             },
             "productNameValue": {
                 "type": "String",
                 "metadata": {
                     "description": "required value for product Name tag"
-                }
+                },
+                "defaultValue": "DefaultProduct"
             }
         },
         "policyDefinitions": [{

articles/governance/policy/how-to/remediate-resources.md

@@ -1,16 +1,17 @@
 ---
 title: Remediate non-compliant resources
 description: This guide walks you through the remediation of resources that are non-compliant to policies in Azure Policy.
-ms.date: 09/09/2019
+ms.date: 02/26/2020
 ms.topic: how-to
 ---
 # Remediate non-compliant resources with Azure Policy
 
 Resources that are non-compliant to a **deployIfNotExists** or **modify** policy can be put into a
 compliant state through **Remediation**. Remediation is accomplished by instructing Azure Policy to
 run the **deployIfNotExists** effect or the tag **operations** of the assigned policy on your
-existing resources. This article shows the steps needed to understand and accomplish remediation
-with Azure Policy.
+existing resources, whether that assignment is to a management group, a subscription, a resource
+group, or an individual resource. This article shows the steps needed to understand and accomplish
+remediation with Azure Policy.
 
 ## How remediation security works