updates author metadata

Author: davidsmatlak

includes/policy/standards/intro-warning.md

@@ -1,9 +1,9 @@
 ---
-author: davidsmatlak
 ms.service: azure-policy
 ms.topic: include
-ms.date: 09/04/2020
-ms.author: davidsmatlak
+ms.date: 03/25/2025
+ms.author: jasongroce
+author: jasongroce
 ms.custom: generated
 ---
 
@@ -13,4 +13,4 @@ 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](/azure/governance/policy/overview) definitions. These policies might help you [assess compliance](/azure/governance/policy/how-to/get-compliance-data) 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.
-> 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.
+> 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.