Fix blocking issues

Author: dksimpson

articles/public-multi-access-edge-compute-mec/considerations-for-deployment.md

@@ -72,18 +72,18 @@ Applications you deploy in the Azure public MEC can be made available and resili
 
 - Deploy resources in active/standby, with primary resources in the Azure public MEC and standby resources in the parent Azure region. If there's a failure in the Azure public MEC, the resources in the parent region become active.
 
-- Use the [Azure backup and disaster recover solution](/azure/architecture/framework/resiliency/backup-and-recovery), which provides [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) and Azure Backup features. This solution:
+- Use the [Azure backup and disaster recovery solution](/azure/architecture/framework/resiliency/backup-and-recovery), which provides [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) and Azure Backup features. This solution:
   - Actively replicates VMs from the Azure public MEC to the parent region and makes them available to fail over and fail back if there's an outage.
   - Backs up VMs to prevent data corruption or lost data.
 
    > [!NOTE]
-   > The Azure Azure backup and disaster recover solution for Azure public MEC supports only Azure Virtual Machines.
+   > The Azure backup and disaster recovery solution for Azure public MEC supports only Azure Virtual Machines.
 
 A trade-off exists between availability and latency. Failing over the application from the Azure public MEC to the Azure region ensures that the application is available, but might increase the latency to the application.
 
 ## Next steps
 
-To deploy a virtual machine in Azure public MEC using an ARM template, advance to the following article:
+To deploy a virtual machine in Azure public MEC using an Azure Resource Manager template, advance to the following article:
 
 > [!div class="nextstepaction"]
-> [Quickstart: Deploy a virtual machine in Azure public MEC using an ARM template](quickstart-create-vm-arm-template.md)
+> [Quickstart: Deploy a virtual machine in Azure public MEC using an Azure Resource Manager template](quickstart-create-vm-azure-resource-manager-template.md)

articles/public-multi-access-edge-compute-mec/index.yml

@@ -38,7 +38,7 @@ landingContent:
       - linkListType: quickstart
         links:
           - text: Create VM using ARM template
-            url: quickstart-create-vm-arm-template.md
+            url: quickstart-create-vm-azure-resource-manager-template.md
           - text: Create VM using Azure CLI
             url: quickstart-create-vm-cli.md
 
@@ -47,7 +47,7 @@ landingContent:
     linkLists:
       - linkListType: tutorial
         links:
-          - text: Create VM using GO SDK
+          - text: Create VM using Go SDK
             url: tutorial-create-vm-using-go-sdk.md
           - text: Create VM using Python SDK
             url: tutorial-create-vm-using-python-sdk.md

articles/public-multi-access-edge-compute-mec/key-concepts.md

@@ -27,7 +27,7 @@ SDKs for services supported in Azure public MEC have been updated. For informati
 
 ## ARM templates
 
-You can use ARM Templates to deploy resources in the Azure public MEC. Here's' an example of how `extendedLocation` is used in an Azure Resource Manager (ARM) template to deploy a virtual machine (VM):
+You can use ARM Templates to deploy resources in the Azure public MEC. Here's an example of how `extendedLocation` is used in an Azure Resource Manager (ARM) template to deploy a virtual machine (VM):
 
 ```json
 {
@@ -84,7 +84,7 @@ Resource Groups should  be created in the parent Azure region, and then can be a
 
 ### Storage Services
 
-Azure public MEC only supports creating Standard SSD Managed DiskS. All other storage services are currently not supported in the public MEC.
+Azure public MEC only supports creating Standard SSD Managed Disks. All other storage services are currently not supported in the public MEC.
 
 ### Default outbound access
 

articles/public-multi-access-edge-compute-mec/overview.md

@@ -66,8 +66,7 @@ The following diagram explains how services are deployed at the Azure public MEC
 
 Azure public MEC solutions are available in partnership with mobile network operators. The current operator partnerships are as follows:
 
-- AT&T: Atlanta, Dallas (more sites to follow)
-- Singtel: Coming soon
+- AT&T: Atlanta, Dallas
 
 ## Next steps
 

articles/public-multi-access-edge-compute-mec/quickstart-create-vm-arm-template.md renamed to articles/public-multi-access-edge-compute-mec/quickstart-create-vm-azure-resource-manager-template.md

@@ -17,7 +17,7 @@ items:
   expanded: true
   items:
   - name: Create VM using ARM template
-    href: quickstart-create-vm-arm-template.md
+    href: quickstart-create-vm-azure-resource-manager-template.md
   - name: Create VM using Azure CLI
     href: quickstart-create-vm-cli.md
     displayName: az login, az account, az group, az vm, az network, jump server, SSH, Azure Virtual Network, VNet

articles/public-multi-access-edge-compute-mec/toc.yml

@@ -226,7 +226,7 @@ func main() {
 
 ## Clean up resources
 
-In this tutorial, you created a VM in Azure public MEC by using the Python SDK. If you don't expect to need these resources in the future, use the Azure portal to delete the resource group that you created.
+In this tutorial, you created a VM in Azure public MEC by using the Go SDK. If you don't expect to need these resources in the future, use the Azure portal to delete the resource group that you created.
 
 ## Next steps
 

articles/public-multi-access-edge-compute-mec/tutorial-create-vm-using-go-sdk.md

@@ -232,7 +232,7 @@ In this tutorial, you learn how to:
 
 ## Run the script in your development environment
 
-1. Run the python script you copied from the previous section.
+1. Run the Python script you copied from the previous section.
 
    ```python
    python provision_vm_edge.py
@@ -278,7 +278,7 @@ To use SSH to connect to the VM in the Azure public MEC, the best method is to d
    ssh azureuser@<python-example-ip-edge>
    ```
 
-1. Ensure the Azure network security groups allow port 22 access to the VMs you create
+1. Ensure the Azure network security groups allow port 22 access to the VMs you create.
 
 ## Clean up resources