fixed warnings

Author: PriskeyJeronika-MS

articles/azure-monitor/scom-manage-instance/configure-network-firewall.md

@@ -100,8 +100,8 @@ To function properly, SCOM Managed Instance must have access to the following po
 |*.azuremonitor-scommiconnect.azure.com|443|Outbound| |Bridge Service|
 
 > [!IMPORTANT]
-> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-of-steps.md). The article outlines the procedures that the Active Directory admin and the network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
+> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-steps.md). The article outlines the procedures that the Active Directory admin and the network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
 
 ## Next steps
 
-- [Verify Azure and internal GPO policies](verify-azure-and-internal-gpo-policies.md)
+- [Verify Azure and internal GPO policies](verify-azure-internal-group-policy-object-policies.md)

articles/azure-monitor/scom-manage-instance/create-group-managed-service-account.md

@@ -73,8 +73,8 @@ Add-KdsRootKey -EffectiveTime ((get-date).addhours(-10))
 Ensure that the created gMSA account is a local admin account. If there are any Group Policy Object policies on the local admins at the Active Directory level, ensure that they have the gMSA account as the local admin.
 
 > [!IMPORTANT]
-> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-of-steps.md). The article outlines the procedures that the Active Directory admin and network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
+> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-steps.md). The article outlines the procedures that the Active Directory admin and network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
 
 ## Next steps
 
-[Store domain credentials in Azure Key Vault](store-domain-credentials-in-key-vault.md)
+[Store domain credentials in Azure Key Vault](store-domain-credentials-key-vault.md)

articles/azure-monitor/scom-manage-instance/create-static-ip.md

@@ -13,7 +13,7 @@ ms.topic: how-to
 
 # Create a static IP for Azure Monitor SCOM Managed Instance
 
-This article describes how to create a static IP for a load balancer in a dedicated subnet of Azure Monitor SCOM Managed Instance. Additionally, insert an entry into the Domain Name System (DNS) server, and ensure that the DNS name resolves to the DNS name (`DNSHostName`) of the group managed service account (gMSA). Get the DNS host name of the gMSA account from [step 6](create-gmsa-account.md).
+This article describes how to create a static IP for a load balancer in a dedicated subnet of Azure Monitor SCOM Managed Instance. Additionally, insert an entry into the Domain Name System (DNS) server, and ensure that the DNS name resolves to the DNS name (`DNSHostName`) of the group managed service account (gMSA). Get the DNS host name of the gMSA account from [step 6](create-group-managed-service-account.md).
 
 >[!NOTE]
 > To learn about the SCOM Managed Instance architecture, see [Azure Monitor SCOM Managed Instance](overview.md).
@@ -38,7 +38,7 @@ Create the forward lookup entry in DNS by creating an association between the IP
 :::image type="DNS manager" source="media/create-static-ip/dns-manager.png" alt-text="Screenshot that shows host information in DNS Manager.":::
 
 > [!IMPORTANT]
-> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-of-steps.md). The article outlines the procedures that the Active Directory admin and the network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
+> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-steps.md). The article outlines the procedures that the Active Directory admin and the network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
 
 ## Next steps
 

articles/azure-monitor/scom-manage-instance/verify-azure-internal-group-policy-object-policies.md

@@ -41,8 +41,8 @@ The following policies could potentially influence the local administrator group
    - Assess whether any policies are obstructing remote logins to the local administrator group.
 
 > [!IMPORTANT]
-> To minimize the need for extensive communication with both your Active Directory admin and network admin, see [Self-verification](self-verification-of-steps.md). The article outlines the procedures that the Active Directory admin and network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
+> To minimize the need for extensive communication with both your Active Directory admin and network admin, see [Self-verification](self-verification-steps.md). The article outlines the procedures that the Active Directory admin and network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
 
 ## Next step
 
-- [SCOM Managed Instance self-verification of steps](self-verification-of-steps.md)
+- [SCOM Managed Instance self-verification of steps](self-verification-steps.md)