fix warnings

Author: asergaz

articles/iot-operations/manage-layered-network/howto-configure-aks-edge-essentials-layered-network.md

@@ -81,7 +81,7 @@ Follow the steps in [Quickstart: Deploy Azure IoT Operations Preview to an Arc-e
 
 - In earlier steps, you completed the [prerequisites](../get-started/quickstart-deploy.md#prerequisites) and [connected your cluster to Azure Arc](../get-started/quickstart-deploy.md#connect-a-kubernetes-cluster-to-azure-arc) for Azure IoT Operations. You can review these steps to make sure nothing is missing. 
 
-- Start from the [Configure cluster and deploy Azure IoT Operations](../get-started/quickstart-deploy.md#configure-cluster-and-deploy-azure-iot-operations) and complete all the further steps.
+- Start from the [Configure cluster and deploy Azure IoT Operations](../get-started/quickstart-deploy.md#configure-cluster-and-deploy-azure-iot-operations-preview) and complete all the further steps.
 
 
 ## Next steps

articles/iot-operations/manage-mqtt-connectivity/howto-configure-tls-auto.md

@@ -42,7 +42,7 @@ With automatic certificate management, you use cert-manager to manage the TLS se
 The cert-manager Issuer resource defines how certificates are automatically issued. Cert-manager [supports several Issuers types natively](https://cert-manager.io/docs/configuration/). It also supports an [external](https://cert-manager.io/docs/configuration/external/) issuer type for extending functionality beyond the natively supported issuers. Azure IoT MQ Preview can be used with any type of cert-manager issuer.
 
 > [!IMPORTANT]
-> During initial deployment, Azure IoT Operations is installed with a default Issuer for TLS server certificates. You can use this issuer for development and testing. For more information, see [Default root CA and issuer with Azure IoT Operations](#default-root-ca-and-issuer-with-azure-iot-operations). The steps below are only required if you want to use a different issuer.
+> During initial deployment, Azure IoT Operations is installed with a default Issuer for TLS server certificates. You can use this issuer for development and testing. For more information, see [Default root CA and issuer with Azure IoT Operations](#default-root-ca-and-issuer-with-azure-iot-operations-preview). The steps below are only required if you want to use a different issuer.
 
 The approach to create the issuer is different depending on your scenario. The following sections list examples to help you get started.
 

articles/iot-operations/troubleshoot/troubleshoot.md

@@ -148,7 +148,7 @@ If your cluster is behind an outbound proxy server, please ensure that you have
 #### Other types of Arc-enablement failures
 
 1. Add the `--debug` parameter when running the `connectedk8s` command.
-1. Capture and investigate a network packet trace. For more information, see [capture Layered Network Management packet trace](#capture-layered-network-management-packet-trace).
+1. Capture and investigate a network packet trace. For more information, see [capture Layered Network Management packet trace](#capture-layered-network-management-preview-packet-trace).
 
 ### Can't install IoT Operations on the isolated cluster
 
@@ -163,8 +163,8 @@ You can't install IoT Operations components on nested layers. For example, Layer
 
     DNS should respond with the IP address of the Layered Network Management service.
 
-1. If the domain is being resolved correctly, verify the domain is added to the allowlist. For more information, see [Check the allowlist of Layered Network Management](#check-the-allowlist-of-layered-network-management).
-1. Capture and investigate a network packet trace. For more information, see [capture Layered Network Management packet trace](#capture-layered-network-management-packet-trace).
+1. If the domain is being resolved correctly, verify the domain is added to the allowlist. For more information, see [Check the allowlist of Layered Network Management](#check-the-allowlist-of-layered-network-management-preview).
+1. Capture and investigate a network packet trace. For more information, see [capture Layered Network Management packet trace](#capture-layered-network-management-preview-packet-trace).
 
 ### A pod fails when installing IoT Operations on an isolated cluster