updates

Author: ProfessorKendrick

articles/partner-solutions/datadog/overview.md

@@ -3,7 +3,7 @@ title: Datadog overview
 description: Discover Datadog, a monitoring and analytics platform for large-scale applications integrated with Azure for streamlined management and enhanced performance.
 
 ms.topic: conceptual
-ms.date: 12/09/2024
+ms.date: 12/11/2024
 ms.custom:
   - ai-gen-docs-bap
   - ai-gen-desc

articles/partner-solutions/datadog/troubleshoot.md

@@ -55,7 +55,7 @@ To set up the Azure Datadog integration, you must have **Owner** access on the A
 
 - Limit of five diagnostic settings reached. Each Azure resource can have a maximum of five diagnostic settings. For more information, see [diagnostic settings](/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal).
 
-- Export of Metrics data isn't supported currently by the partner solutions under Azure Monitor diagnostic settings. 
+- Export of Metrics data isn't supported under Azure Monitor diagnostic settings by partner solutions. 
 
 ## Metrics not being emitted
 
@@ -71,7 +71,7 @@ If the Datadog agent is configured with an incorrect key, navigate to the API ke
 
 ## Diagnostic settings are active even after disabling the Datadog resource or applying necessary tag rules
 
-If logs are being emitted and diagnostic settings remain active on monitored resources even after the Datadog resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve this, remove the delete lock from the resource or the resource group. If the lock is removed after the Datadog resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
+If logs are being emitted and diagnostic settings remain active on monitored resources even after the Datadog resource is disabled or tag rules are modified to exclude certain resources, it's likely that there's a delete lock applied to the resources or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve this issue, remove the delete lock from the resource or the resource group. If the lock is removed after the Datadog resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
 
 ## Next steps