fixed blocking issues

Author: PriskeyJeronika-MS

articles/azure-monitor/scom-manage-instance/create-separate-subnet-in-vnet.md

@@ -22,7 +22,7 @@ This article describes how to create a separate subnet in a virtual network for
 
 For more information on how to create a virtual network, see [Quickstart: Use the Azure portal to create a virtual network](/azure/virtual-network/quick-create-portal).
 
-After a SCOM Managed Instance subnet is created, we need a NAT gateway for outbound internet access from the SCOM Managed Instance subnet. Edit the subnet to add a NAT gateway. In Azure, add a NAT gateway to the subnet where the SCOM managed instance is created. A NAT gateway is needed for outbound internet access from the SCOM Managed Instance subnet. For more information, see [What is Virtual Network NAT?](/azure/virtual-network/nat-gateway/nat-overview).
+After a SCOM Managed Instance subnet is created, we need a NAT gateway for outbound internet access from the SCOM Managed Instance subnet. Edit the subnet to add a NAT gateway. In Azure, add a NAT gateway to the subnet where the SCOM Managed Instance is created. A NAT gateway is needed for outbound internet access from the SCOM Managed Instance subnet. For more information, see [What is Virtual Network NAT?](/azure/virtual-network/nat-gateway/nat-overview).
 
 >[!NOTE]
 >The SCOM Managed Instance requires outbound Internet access for communication with dependent endpoints. We recommend to use a NAT Gateway for this purpose. However, if there is an already established outbound internet access through a firewall, you can skip the creation of a NAT Gateway.

articles/azure-monitor/scom-manage-instance/customizations-on-scom-managed-instance-management-servers.md

@@ -47,3 +47,7 @@ Here's an example of a command to run the script (replace the parameters in quot
 If the script runs successfully, deployment gets successful and displays **Deployment finished Successfully** message.
 
 If there's an error in the script, you see **An error occurred during deployment. Please check the above logs for debugging** message.
+
+## Next step
+
+[Register the Azure Monitor SCOM Managed Instance resource provider](register-scom-managed-instance-resource-provider.md)

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

@@ -29,7 +29,7 @@
     - name: Step 2. Create separate subnet in a VNet
       href: create-separate-subnet-in-vnet.md
     - name: Step 3. Create a SQL MI
-      herf: create-sql-managed-instance.md
+      href: create-sql-managed-instance.md
     - name: Step 4. Create a Key vault
       href: create-key-vault.md
     - name: Step 5. Create a user assigned identity