updates

Author: ProfessorKendrick

articles/partner-solutions/apache-kafka-confluent-cloud/troubleshoot.md

@@ -54,13 +54,13 @@ This error could be an intermittent problem with the Azure portal. Try to deploy
 
 ## Unable to delete
 
-If you're unable to delete Confluent resources, verify you have permissions to delete the resource. You must be allowed to take Microsoft.Confluent/*/Delete actions. For information about viewing permissions, see [List Azure role assignments using the Azure portal](../../role-based-access-control/role-assignments-list-portal.yml).
+If you're unable to delete Confluent resources, check you have permissions to delete the resource. You must be allowed to take Microsoft.Confluent/*/Delete actions. For information about viewing permissions, see [List Azure role assignments using the Azure portal](../../role-based-access-control/role-assignments-list-portal.yml).
 
 If you have the correct permissions but still can't delete the resource, contact [Confluent support](https://support.confluent.io). This condition might be related to Confluent's retention policy. Confluent support can delete the organization and email address for you.
 
 ## Unable to use single sign-on
 
-If SSO isn't working for the Confluent Cloud SaaS portal, verify you're using the correct Microsoft Entra ID email. You must also have consented to allow access for the Confluent Cloud software as a service (SaaS) portal. 
+If SSO isn't working for the Confluent Cloud SaaS portal, check you're using the correct Microsoft Entra ID email. You must also have consented to allow access for the Confluent Cloud software as a service (SaaS) portal. 
 
 If the problem persists, contact [Confluent support](https://support.confluent.io).
 

articles/partner-solutions/astronomer/troubleshoot.md

@@ -49,7 +49,7 @@ If the deployment fails and the Astro resource has a status of `Failed`, delete
 
 ### Unable to use Single sign-on
 
-If SSO isn't working for the Astronomer portal, verify you're using the correct Microsoft Entra email. You must also have consented to allow access for the Astronomer Software as a service (SaaS) portal.
+If SSO isn't working for the Astronomer portal, check you're using the correct Microsoft Entra email. You must also have consented to allow access for the Astronomer Software as a service (SaaS) portal.
 
 > [!NOTE]
 > If you are seeing an Admin consent screen along with the User consent during your first-time login using the SSO Url, then please check your [tenant consent settings](/azure/active-directory/manage-apps/configure-user-consent?pivots=portal).

articles/partner-solutions/datadog/troubleshoot.md

@@ -45,11 +45,11 @@ To set up the Azure Datadog integration, you must have **Owner** access on the A
 
 - Only resources listed in the Azure Monitor resource log categories emit logs to Datadog. 
 
-    To verify whether the resource is emitting logs to Datadog: 
+    To check whether the resource is emitting logs to Datadog: 
 
     1. Navigate to Azure diagnostic setting for the specific resource. 
 
-    1. Verify that there's a Datadog diagnostic setting.
+    1. check that there's a Datadog diagnostic setting.
 
 - Resource doesn't support sending logs. Only resource types with monitoring log categories can be configured to send logs. For more information, see [supported categories](/azure/azure-monitor/essentials/resource-logs-categories).
 
@@ -61,7 +61,7 @@ To set up the Azure Datadog integration, you must have **Owner** access on the A
 
 The Datadog resource is assigned a **Monitoring Reader** role in the appropriate Azure subscription. This role enables the Datadog resource to collect metrics and send those metrics to Datadog.
 
-To verify the resource has the correct role assignment, open the Azure portal and select the subscription. In the left pane, select **Access Control (IAM)**. Search for the Datadog resource name. Confirm that the Datadog resource has the **Monitoring Reader** role assignment.
+To check the resource has the correct role assignment, open the Azure portal and select the subscription. In the left pane, select **Access Control (IAM)**. Search for the Datadog resource name. Confirm that the Datadog resource has the **Monitoring Reader** role assignment.
 
 ## Datadog agent installation fails
 

articles/partner-solutions/elastic/troubleshoot.md

@@ -17,12 +17,12 @@ Only users who have *Owner* or *Contributor* access on the Azure subscription ca
 
 ## Logs not being emitted to Elastic
 
-- Only resources listed in [Azure Monitor resource log categories](/azure/azure-monitor/essentials/resource-logs-categories) emit logs to Elastic. To verify whether the resource is emitting logs to Elastic:
+- Only resources listed in [Azure Monitor resource log categories](/azure/azure-monitor/essentials/resource-logs-categories) emit logs to Elastic. To check whether the resource is emitting logs to Elastic:
 
    1. Navigate to [Azure diagnostic setting](/azure/azure-monitor/essentials/diagnostic-settings) for the resource.
-   1. Verify that there's a diagnostic setting option available.
+   1. check that there's a diagnostic setting option available.
 
-   :::image type="content" source="media/troubleshoot/check-diagnostic-setting.png" alt-text="Screenshot of verify diagnostic setting.":::
+   :::image type="content" source="media/troubleshoot/check-diagnostic-setting.png" alt-text="Screenshot of check diagnostic setting.":::
 
 - Resource doesn't support sending logs. Only resource types with monitoring log categories can be configured to send logs. For more information, see [supported categories](/azure/azure-monitor/essentials/resource-logs-categories).
 

articles/partner-solutions/neon/manage.md

@@ -35,7 +35,7 @@ Single sign-on (SSO) is already enabled when you create your Neon resource.
 [!INCLUDE [sso](../includes/sso.md)]
 
 > [!NOTE] 
-> The first time you access this URL, depending on your Azure tenant settings, you might be asked to verify your email address on the Neon portal. Once the email address is verified, you can access the Neon portal.
+> The first time you access this URL, depending on your Azure tenant settings, you might be asked to check your email address on the Neon portal. Once the email address is verified, you can access the Neon portal.
 
 ## Projects
 
@@ -94,7 +94,7 @@ To generate a connection string, open your project or branch in the working pane
 
 1. Select **Connect to database** from the menu bar in the working pane. 
 
-1. Verify the default values or select new values from each dropdown.
+1. check the default values or select new values from each dropdown.
 
 1. Select the copy icon next to the connection string.
 

articles/partner-solutions/new-relic/troubleshoot.md

@@ -24,7 +24,7 @@ To register the resource provider from a command line, enter `az provider regist
 
 ## Logs aren't being sent to New Relic
 
-Only resource types in [supported categories](/azure/azure-monitor/essentials/resource-logs-categories) send logs to New Relic through the integration. To check whether the resource is set up to send logs to New Relic, go to the [Azure diagnostic settings](/azure/azure-monitor/platform/diagnostic-settings) for that resource. Then, verify that there's a New Relic diagnostic setting.
+Only resource types in [supported categories](/azure/azure-monitor/essentials/resource-logs-categories) send logs to New Relic through the integration. To check whether the resource is set up to send logs to New Relic, go to the [Azure diagnostic settings](/azure/azure-monitor/platform/diagnostic-settings) for that resource. Then, check that there's a New Relic diagnostic setting.
 
 ## Can't install or uninstall an extension on a virtual machine