Merge pull request #222755 from timwarner-msft/timwarner-dcthegeek

Update author field to my name

Author: 19BMG00

articles/governance/blueprints/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.service: blueprints
   ms.topic: landing-page
   ms.collection: collection
-  author: DCtheGeek
+  author: timwarner-msft
   ms.author: dacoulte
   ms.date: 08/27/2020
 

articles/governance/management-groups/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.service: governance
   ms.topic: landing-page
   ms.collection: collection
-  author: DCtheGeek
+  author: timwarner-msft
   ms.author: dacoulte
   ms.date: 09/30/2020
 

articles/governance/policy/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.service: azure-policy
   ms.topic: landing-page
   ms.collection: collection
-  author: DCtheGeek
+  author: timwarner-msft
   ms.author: dacoulte
   ms.date: 06/02/2021
 

articles/governance/resource-graph/index.yml

@@ -9,7 +9,7 @@ metadata:
   ms.service: resource-graph
   ms.topic: landing-page
   ms.collection: collection
-  author: DCtheGeek
+  author: timwarner-msft
   ms.author: dacoulte
   ms.date: 06/29/2020
 

articles/industry/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.service: azure-industry
   ms.topic: hub-page
   ms.collection: collection
-  author: DCtheGeek
+  author: timwarner-msft
   ms.author: dacoulte
   ms.date: 11/04/2019
 

includes/policy/standards/intro-warning.md

@@ -1,5 +1,5 @@
 ---
-author: DCtheGeek
+author: timwarner-msft
 ms.service: azure-policy
 ms.topic: include
 ms.date: 09/04/2020
@@ -12,5 +12,5 @@ The title of each built-in policy definition links to the policy definition in t
 
 > [!IMPORTANT]
 > Each control is associated with one or more [Azure Policy](../../../articles/governance/policy/overview.md) definitions. These policies might help you [assess compliance](../../../articles/governance/policy/how-to/get-compliance-data.md) with the control.
-> However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, **Compliant** in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. 
+> However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, **Compliant** in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time.
 > Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time.