Fixed link and acrolinx.

Author: flang-msft

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md

@@ -37,22 +37,24 @@ This document contains information about troubleshooting your solutions that use
 
 - To set up the Azure Native Dynatrace Service, you must have **Owner** or **Contributor** access on the Azure subscription. Ensure you have the appropriate access before starting the setup.
 
-- Create fails because Last Name is empty. This happens when the user info in Azure AD is incomplete and doesn't contain Last Name. Contact your Azure tenant's global administrator to rectify this and try again.
+- Create fails because Last Name is empty. The issue happens when the user info in Azure AD is incomplete and doesn't contain Last Name. Contact your Azure tenant's global administrator to rectify the issue and try again.
 
 ### Logs not being emitted
 
 - 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).
 
 - 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 is not supported currently by the partner solutions under Azure Monitor diagnostic settings. 
+- Export of Metrics data isn't supported currently by the partner solutions under Azure Monitor diagnostic settings. 
 
 
 ### Single sign-on errors
 
-- **Single sign-on configuration indicates lack of permissions** - This 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** - This 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.
+- **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.
 
 - **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.
 

articles/partner-solutions/logzio/troubleshoot.md

@@ -15,7 +15,7 @@ This article describes how to troubleshoot the Logz.io integration with Azure.
 
 ## Owner role needed to create resource
 
-To set up Logz.io, you must be assigned the [Owner role](/azure/role-based-access-control/rbac-and-directory-admin-roles.md#azure-roles) in the Azure subscription. Before you begin this integration, [check your access](/azure/role-based-access-control/check-access).
+To set up Logz.io, you must be assigned the [Owner role](/azure/role-based-access-control/rbac-and-directory-admin-roles#azure-roles) in the Azure subscription. Before you begin this integration, [check your access](/azure/role-based-access-control/check-access).
 
 ## Single sign-on errors
 
@@ -42,16 +42,16 @@ Use the following patterns to add new values:
 
 ### Logs not being sent to Logz.io
 
-- Only resources listed in [Azure Monitor resource log categories](/azure/azure-monitor/essentials/resource-logs-categories.md) send logs to Logz.io.  To verify whether a resource is sending logs to Logz.io:
+- Only resources listed in [Azure Monitor resource log categories](/azure/azure-monitor/essentials/resource-logs-categories) send logs to Logz.io.  To verify whether a resource is sending logs to Logz.io:
 
    1. Go to [Azure diagnostic setting](/azure/azure-monitor/essentials/diagnostic-settings.md) for the specific resource.
    1. Verify that there's a Logz.io diagnostic setting.
 
    :::image type="content" source="media/troubleshoot/diagnostics.png" alt-text="Screenshot of the Azure monitoring diagnostic settings for Logz.io.":::
 
-- 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.md?tabs=portal).
+- 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 is not supported currently by the partner solutions under Azure Monitor diagnostic settings. 
+- Export of Metrics data isn't supported currently by the partner solutions under Azure Monitor diagnostic settings. 
 
 ## Register resource provider
 
@@ -76,7 +76,7 @@ Purchase fails because a valid credit card isn't connected to the Azure subscrip
 To resolve a purchase error:
 
 - Use a different Azure subscription.
-- Add or update the subscription's credit card or payment method. For more information, see [Add or update a credit card for Azure](/azure/cost-management-billing/manage/change-credit-card.md).
+- Add or update the subscription's credit card or payment method. For more information, see [Add or update a credit card for Azure](/azure/cost-management-billing/manage/change-credit-card).
 
 You can view the error's output from the resource's deployment page, by selecting **Operation Details**.