fixed warnings

Author: PriskeyJeronika-MS

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/create-user-assigned-identity.md

@@ -112,4 +112,4 @@ To grant permission on the key vault that you created in [step 4](create-key-vau
 
 ## Next steps
 
-- [Create a gMSA account](create-gmsa-account.md)
+- [Create a gMSA account](create-group-managed-service-account.md)

articles/azure-monitor/scom-manage-instance/index.yml

@@ -43,7 +43,7 @@ landingContent:
       - linkListType: how-to-guide
         links:  
           - text: Create reports on power BI
-            url: create-reports-on-power-bi.md
+            url: create-reports-power-bi.md
           - text: Dashboards on Azure Managed Grafana
             url: dashboards-on-azure-managed-grafana.md
   - title: Troubleshooting

articles/azure-monitor/scom-manage-instance/overview.md

@@ -107,12 +107,12 @@ Operations Manager Management server and monitored agents are connected through
    - [Step 3. Create a SQL Managed Instance](create-sql-managed-instance.md).
    - [Step 4. Create a Key vault](create-key-vault.md).
    - [Step 5. Create a user assigned identity](create-user-assigned-identity.md).
-   - [Step 6. Create a computer group and gMSA account](create-gmsa-account.md).
-   - [Step 7. Store domain credentials in Key vault](store-domain-credentials-in-key-vault.md).
+   - [Step 6. Create a computer group and gMSA account](create-group-managed-service-account.md).
+   - [Step 7. Store domain credentials in Key vault](store-domain-credentials-key-vault.md).
    - [Step 8. Create a static IP](create-static-ip.md).
    - [Step 9. Configure the network firewall](configure-network-firewall.md).
    - [Step 10. Verify Azure and internal GPO policies](verify-azure-and-internal-gpo-policies.md).
-   - [Step 11. SCOM Managed Instance self-verification of steps](self-verification-of-steps.md).
+   - [Step 11. SCOM Managed Instance self-verification of steps](self-verification-steps.md).
    - [Step 12. Create a SCOM Managed Instance](create-operations-manager-managed-instance.md).
 
 [Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance](migrate-to-operations-manager-managed-instance.md).

articles/azure-monitor/scom-manage-instance/toc.yml

@@ -35,17 +35,17 @@
     - name: Step 5. Create a user assigned identity
       href: create-user-assigned-identity.md
     - name: Step 6. Create a computer group and gMSA account
-      href: create-gmsa-account.md
+      href: create-group-managed-service-account.md
     - name: Step 7. Store domain credentials in Key vault
-      href: store-domain-credentials-in-key-vault.md
+      href: store-domain-credentials-key-vault.md
     - name: Step 8. Create a static IP
       href: create-static-ip.md
     - name: Step 9. Configure the network firewall
       href: configure-network-firewall.md
     - name: Step 10. Verify Azure and internal GPO policies
       href: verify-azure-and-internal-gpo-policies.md
     - name: Step 11. SCOM Managed Instance self-verification of steps
-      href: self-verification-of-steps.md
+      href: self-verification-steps.md
     - name: Step 12. Create a SCOM Managed Instance
       href: create-operations-manager-managed-instance.md
   - name: Post Deployment
@@ -57,7 +57,7 @@
     - name: Patch SCOM Managed Instance
       href: patch-scom-managed-instance.md
     - name: Report using Power BI
-      href: create-reports-on-power-bi.md
+      href: create-reports-power-bi.md
     - name: Dashboards on Azure Managed Grafana
       href: dashboards-on-azure-managed-grafana.md
     - name: Query SCOM Managed Instance data on Azure Managed Grafana