updates

Author: ProfessorKendrick

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

@@ -10,7 +10,7 @@ ms.date: 1/31/2024
 
 This document contains information about troubleshooting your solutions that use Apache Kafka® & Apache Flink® on Confluent Cloud™ - An Azure Native ISV Service.
 
-If you don't find an answer or can't resolve a problem, [create a request through the Azure portal](get-support.md) or contact [Confluent support](https://support.confluent.io).
+If you don't find an answer or can't fix a problem, [create a request through the Azure portal](get-support.md) or contact [Confluent support](https://support.confluent.io).
 
 ## Can't find offer in the Marketplace
 

articles/partner-solutions/datadog/troubleshoot.md

@@ -25,7 +25,7 @@ To set up the Azure Datadog integration, you must have **Owner** access on the A
 - **Unable to save Single sign-on settings** 
    - This error happens where there's another Enterprise app that is using the Datadog SAML identifier. To find which app is using it, select **Edit** on the Basic SAML Configuration section.
 
-   To resolve this issue, either disable the other app or use the other app as the Enterprise app to set up SAML SSO with Datadog. If you decide to use the other app, ensure the app has the [required settings](create.md#single-sign-on-tab-optional).
+   To fix this issue, either disable the other app or use the other app as the Enterprise app to set up SAML SSO with Datadog. If you decide to use the other app, ensure the app has the [required settings](create.md#single-sign-on-tab-optional).
 
 - **App not showing in Single sign-on setting page** 
    - First, search for the application ID. If no result is shown, check the SAML settings of the app. The grid only shows apps with correct SAML settings. 
@@ -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 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.
+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 fix 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.
 
 [!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
 

articles/partner-solutions/dynatrace/troubleshoot.md

@@ -36,7 +36,7 @@ If those options don't solve the problem, contact [Dynatrace support](https://s
 - **Single sign-on configuration indicates lack of permissions**
   - Occurs when the user that is trying to configure single sign-on doesn't have Manage users permissions for the Dynatrace account. For a description of how to configure this permission, see [here](https://www.dynatrace.com/support/help/shortlink/azure-native-integration#setup).
 - **Unable to save single sign-on settings**
-  - Error happens when there's another Enterprise app that is using the Dynatrace SAML identifier. To find which app is using it, select **Edit** on the Basic **SAML** configuration section. To resolve this issue, either disable the other app or use the other app as the Enterprise app to set up SAML SSO.
+  - Error happens when there's another Enterprise app that is using the Dynatrace SAML identifier. To find which app is using it, select **Edit** on the Basic **SAML** configuration section. To fix this issue, either disable the other app or use the other app as the Enterprise app to set up SAML SSO.
 
 - **App not showing in Single sign-on settings page**
   - First, search for application ID. If no result is shown, check the SAML settings of the app. The grid only shows apps with correct SAML settings.
@@ -47,7 +47,7 @@ If those options don't solve the problem, contact [Dynatrace support](https://s
 
 ## Diagnostic settings are active even after disabling the Dynatrace resource or applying necessary tag rules
 
-If logs are being emitted and diagnostic settings remain active on monitored resources even after the Dynatrace 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 Dynatrace 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 Dynatrace 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 fix this, remove the delete lock from the resource or the resource group. If the lock is removed after the Dynatrace resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
 
 [!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
 

articles/partner-solutions/elastic/troubleshoot.md

@@ -32,7 +32,7 @@ Only users who have *Owner* or *Contributor* access on the Azure subscription ca
 
 ## Diagnostic settings are active even after disabling the Elastic resource or applying necessary tag rules
 
-If logs are being emitted and diagnostic settings remain active on monitored resources even after the Elastic 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 Elastic 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 Elastic 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 fix this, remove the delete lock from the resource or the resource group. If the lock is removed after the Elastic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
 
 [!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
 

articles/partner-solutions/includes/marketplace-purchase-errors.md

@@ -7,7 +7,7 @@ ms.author: kkendrick
 
 |Error message |Details |
 |---------|---------|
-|"The Microsoft.SaaS RP is not registered on the Azure subscription."     |Before you use a resource provider, you must make sure that your Azure subscription is registered for it. For more information, see [Register a resource provider](../../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider) and [Resolve errors for resource provider registration](../../azure-resource-manager/troubleshooting/error-register-resource-provider.md).         |
+|"The Microsoft.SaaS RP is not registered on the Azure subscription."     |Before you use a resource provider, you must make sure that your Azure subscription is registered for it. For more information, see [Register a resource provider](../../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider) and [fix errors for resource provider registration](../../azure-resource-manager/troubleshooting/error-register-resource-provider.md).         |
 |"Plan cannot be purchased on a free subscription, please upgrade your account."     |You can't make Azure Marketplace purchases on a free Azure subscription. For more information, see the [Azure free account FAQ]( https://azure.microsoft.com/free/free-account-faq) and [Purchase a SaaS offer in the Azure portal](/marketplace/purchase-saas-offer-in-azure-portal#common-error-messages-and-solutions).         |
 |"Purchase has failed because we couldn't find a valid payment method associated with your Azure subscription."    |Use a different Azure subscription, or add or update credit card or payment method information for this subscription. For more information, see [Purchase a SaaS offer in the Azure portal](/marketplace/purchase-saas-offer-in-azure-portal#common-error-messages-and-solutions).         |
 |"The Publisher does not make available Offer, Plan in your Subscription/Azure account's region."    |The offer or the specific plan isn't available to the billing account market that's connected to the Azure subscription.          |

articles/partner-solutions/includes/review-create.md

@@ -7,7 +7,7 @@ ms.author: kkendrick
 
 If the review finds no errors, the **Create** button is enabled. Select it.
 
-If the review identifies errors, a red dot appears next to each section where errors exist. To resolve errors:
+If the review identifies errors, a red dot appears next to each section where errors exist. To fix errors:
 
 1. Open each section that has errors and fix the errors.
 

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

@@ -42,7 +42,7 @@ New Relic manages the APIs for creating and managing resources, and for the stor
 
 ## Diagnostic settings are active even after disabling the New Relic resource or applying necessary tag rules
 
-If logs are being emitted and diagnostic settings remain active on monitored resources even after the New Relic resource is disabled or tag rules were 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 the issue, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic 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 New Relic resource is disabled or tag rules were 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 fix the issue, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
 
 [!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]