Edits

Author: dksimpson

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

@@ -23,7 +23,7 @@ Azure public multi-access edge compute (MEC) Preview sites are small-footprint e
 
 For Azure public MEC, follow these best practices:
 
-- Deploy only the components of the application that are latency sensitive or need low latency compute at the Azure public MEC. Deploy all other components of the application that perform control plane and management plane functionalities in the parent region.
+- Deploy in Azure public MEC only those components of the application that are latency sensitive or need low latency compute at the Azure public MEC. Deploy in the parent region those components of the application that perform control plane and management plane functionalities.
 
 - Because Azure public MEC sites are connected to the Telco network, accessing resources deployed in it over the internet isn't allowed. To access VMs deployed in the Azure public MEC, deploy jump box virtual machines (VMs) or Azure Bastion in a virtual network (VNet) in the parent region.
 
@@ -39,7 +39,7 @@ Deploy application components that require ultra-low latencies in the Azure publ
 
 The Azure region should run the components of the application that perform control and management plane functions and aren't latency sensitive.
 
-For example:
+The following sections show some examples.
 
 #### Azure database and storage
 

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

@@ -1,7 +1,7 @@
 ### YamlMime:Landing
 
 title: Azure public multi-access-edge compute documentation # < 60 chars
-summary: Learn how to use an Azure public multi-access-edge compute (MEC) solution to develop and deploy latency-sensitive workloads at the 5G network edge integrated with Azure compute. # < 160 chars
+summary: Learn how to use Azure public multi-access-edge compute (MEC) to develop and deploy latency-sensitive workloads at the 5G network edge integrated with Azure compute. # < 160 chars
 
 metadata:
   title: Azure public multi-access-edge compute documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
@@ -25,11 +25,11 @@ landingContent:
         links:
           - text: What is Azure public MEC?
             url: overview.md
-      - linkListType: concept
+      - linkListType: concepts
         links:
           - text: Considerations for deployment in Azure public MEC
             url: considerations-for-deployment.md
-          - text: Public MEC prerequisites
+          - text: Key concepts for Azure public MEC
             url: key-concepts.md
 
   # Card
@@ -48,6 +48,6 @@ landingContent:
       - linkListType: tutorial
         links:
           - text: Create VM using GO SDK
-            url: quickstart-create-vm-arm-template.md
+            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

@@ -13,19 +13,19 @@ ms.custom: template-concept
 
 This document describes important concepts for Azure public multi-access edge compute (MEC) Preview.
 
-## ExtendedLocation
+## ExtendedLocation field
 
 All resource providers provide an additional field called [extendedLocation](/javascript/api/@azure/arm-compute/extendedlocation), which you use to deploy resources in the Azure public MEC.
 
-### Azure Edge Zone ID
+## Azure Edge Zone ID
 
-Every Azure public MEC site has an Azure Edge Zone ID. This ID is one of the attributes for `extendedLocation` to differentiate sites.
+Every Azure public MEC site has an Azure Edge Zone ID. This ID is one of the attributes that the `extendedLocation` field uses to differentiate sites.
 
-### Azure CLI and SDKs
+## Azure CLI and SDKs
 
-SDKs for services supported in Azure public MEC have been updated. For information about how to use these SDK for deployment, see [Tutorial: Deploy resources in Azure public MEC using the Go SDK](tutorial-create-vm-using-go-sdk.md), [Tutorial: Deploy a virtual machine in Azure public MEC using Python SDK](tutorial-create-vm-using-python-sdk.md), and [Quickstart: Deploy a virtual machine in Azure public MEC using Azure CLI](quickstart-create-vm-cli.md).
+SDKs for services supported in Azure public MEC have been updated. For information about how to use these SDKs for deployment, see [Tutorial: Deploy resources in Azure public MEC using the Go SDK](tutorial-create-vm-using-go-sdk.md), [Tutorial: Deploy a virtual machine in Azure public MEC using Python SDK](tutorial-create-vm-using-python-sdk.md), and [Quickstart: Deploy a virtual machine in Azure public MEC using Azure CLI](quickstart-create-vm-cli.md).
 
-### ARM templates
+## 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):
 
@@ -41,26 +41,26 @@ You can use ARM Templates to deploy resources in the Azure public MEC. Here's' a
 }
 ```
 
-## Parent region
+## Parent regions
 
-Every Azure public MEC site is associated with a parent Azure region. This region hosts all the control plane functions associated with the services running in the Azure public MEC. The following table lists all the active Azure public MEC sites, their Edge Zone ID and associated parent region.
+Every Azure public MEC site is associated with a parent Azure region. This region hosts all the control plane functions associated with the services running in the Azure public MEC. The following table lists active Azure public MEC sites, along with their Edge Zone ID and associated parent region.
 
-Telco Provider | Azure public MEC Name | Edge Zone ID | Parent region
--------------- | --------------------- | ------------ | -------------
-AT&T | ATT Atlanta A | attatlanta1 | East US 2
-AT&T | ATT Dallas A | attdallas1 | South Central US
+| Telco provider | Azure public MEC name | Edge Zone ID | Parent region |
+| -------------- | --------------------- | ------------ | ------------- |
+| AT&T | ATT Atlanta A | attatlanta1 | East US 2 |
+| AT&T | ATT Dallas A | attdallas1 | South Central US |
 
 ## Azure services
 
 ### Azure virtual machines
 
-Azure public MEC supports specific compute and GPU VM SKUs. The table below provides a list of all VM sizes supported:
+Azure public MEC supports specific compute and GPU VM SKUs. The following table lists the supported VM sizes:
 
-Type | Series | VM size
----- | ------ | -------
-VM | D-series | D2s_v3, D4s_v3, D8s_v3
-VM | E-series | E4s_v3, E8s_v3
-GPU | NCasT4_v3-series | Standard_NC4asT4_v3, Standard_NC8asT4_v3
+| Type | Series | VM size |
+| ---- | ------ | ------- |
+| VM | D-series | D2s_v3, D4s_v3, D8s_v3 |
+| VM | E-series | E4s_v3, E8s_v3 |
+| GPU | NCasT4_v3-series | Standard_NC4asT4_v3, Standard_NC8asT4_v3 |
 
 ### Public IP
 
@@ -88,12 +88,10 @@ Azure public MEC only supports creating Standard SSD Managed DiskS. All other st
 
 ### Default outbound access
 
-Because [default outbound access](/azure/virtual-network/ip-services/default-outbound-access) isn't supported on the public MEC, manage your outbound connectivity by using a method in the following table:
+Because [default outbound access](/azure/virtual-network/ip-services/default-outbound-access) isn't supported on the public MEC, manage your outbound connectivity by using one of the following methods:
 
-\# | Method
--- | ------
-1 | Use the frontend IP addresses of a Load Balancer for outbound via outbound rules.
-2 | Assign a public IP to the VM.
+- Use the frontend IP addresses of a Load Balancer for outbound via outbound rules.
+- Assign a public IP to the VM.
 
 ### DNS Resolution
 
@@ -104,4 +102,4 @@ By default, all services running in the Azure public MEC use the DNS infrastruct
 To deploy a virtual machine in Azure public MEC using an ARM 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-using-go-sdk.md)
+> [Quickstart: Deploy a virtual machine in Azure public MEC using an ARM template](quickstart-create-vm-arm-template.md)

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

@@ -13,31 +13,31 @@ ms.custom: template-overview
 
 Azure public multi-access edge compute (MEC) Preview sites are small-footprint extensions of Azure. They're placed in or near mobile operators' data centers in metro areas, and are designed to run workloads that require ultra-low latency while being attached to the mobile network.  Azure public MEC is offered in partnership with the operators. The placement of the infrastructure offers lower latency for applications that are accessed from mobile devices connected to the 5G Mobile network.
 
-Azure public MEC provides secure, reliable, high-bandwidth connectivity between applications that run close to the user while being served by the Microsoft global network. Azure public MEC offers a set of Azure services like Azure Virtual Machines, Azure Load Balancer, and Azure Kubernetes for Edge with the ability to leverage and connect to Azure services available in the Azure region.
+Azure public MEC provides secure, reliable, high-bandwidth connectivity between applications that run close to the user while being served by the Microsoft global network. Azure public MEC offers a set of Azure services like Azure Virtual Machines, Azure Load Balancer, and Azure Kubernetes for Edge, with the ability to leverage and connect to Azure services available in the Azure region.
 
-Some of the industries and use cases where Azure public MEC can provide immense benefits are:
+Some of the industries and use cases where Azure public MEC can provide benefits are:
 
 - Media streaming and content delivery
 - Real-time analytics and inferencing via artificial intelligence and machine learning
 - Rendering for mixed reality
 - Connected automobiles
 - Healthcare
 - Immersive gaming experiences
-- Low latency applications for retail industry
+- Low latency applications for the retail industry
 
 :::image type="content" source="./media/overview/azure-public-mec-benefits.png" alt-text="Diagram showing the benefits of Azure public MEC.":::
 
 ## Benefits of Azure public MEC
 
 Azure public MEC has the following benefits:
 
-- Low latency applications at the 5G network edge.
+- Low latency applications at the 5G network edge:
 
   - Enterprises and developers can run low-latency applications by using the operator’s public 5G network connectivity. This connectivity is architected with a direct, dedicated, and optimized connection to the operator’s mobility core network.
 
 - Access to key Azure services and experiences:
-  - Azure-managed-toolset: Azure Customers can provision and manage their Azure public MEC services and workloads through the Azure portal and other essential Azure tools.
-  - Consistent developer experience: Developing and building applications for the public MEC utilizes the same array of features and tools Azure uses.
+  - Azure-managed toolset: Azure customers can provision and manage their Azure public MEC services and workloads through the Azure portal and other essential Azure tools.
+  - Consistent developer experience: Developing and building applications for the public MEC utilizes the same array of features and tools that Azure uses.
 
 - Access to a rich partner ecosystem:
   - ISVs working on optimized and scalable applications for edge computing can use the Azure public MEC solution for building solutions. These solutions offer low latency and leverage the 5G mobility network and connected scenarios.
@@ -47,25 +47,27 @@ Azure public MEC has the following benefits:
 Azure public MEC enables some key Azure services for customers to deploy. The control plane for these services remains in the region and the data plane is deployed at the edge, resulting in a smaller Azure footprint, fewer dependencies, and the ability to leverage other services deployed at the region.  
 
 The following key services are available in Azure public MEC:
-• Azure Virtual Machines – supported SKUs listed here – link to aboutpublicmec.md
-• Virtual Machine Scale Sets
-• Standard public IP
-• Azure Virtual Networks
-• Virtual network peering
-• Azure Standard Load Balancer
-• Azure Kubernetes for Edge
-• Azure Bastion (must be deployed in a virtual network in the parent Azure region)
-• Azure managed disks (Standard SSD)
+
+- Azure Virtual Machines (Azure public MEC supports these [SKUs](key-concepts.md#azure-virtual-machines))
+- Virtual Machine Scale Sets
+- Standard public IP
+- Azure Virtual Networks
+- Virtual network peering
+- Azure Standard Load Balancer
+- Azure Kubernetes for Edge
+- Azure Bastion (must be deployed in a virtual network in the parent Azure region)
+- Azure managed disks (Azure public MEC supports Standard SSD)
 
 The following diagram explains how services are deployed at the Azure public MEC location. With this capability, enterprises and developers can deploy the customer workloads closer to their users.
 
 :::image type="content" source="./media/overview/azure-public-mec-service-deployment.png" alt-text="Diagram showing Azure public MEC service deployment.":::  
 
-Partnership with operators
-Azure public MEC solutions will be available in partnership with mobile network operators. The current operator partnerships are as follows:
+## Partnership with operators
+
+Azure public MEC solutions is available in partnership with mobile network operators. The current operator partnerships are as follows:
 
-- AT&T (Atlanta, Dallas). More sites to follow
-- Singtel (Singapore)
+- AT&T: Atlanta, Dallas (more sites to follow)
+- Singtel: Singapore.
 
 ## Next steps
 

articles/public-multi-access-edge-compute-mec/quickstart-create-vm-arm-template.md

@@ -11,12 +11,10 @@ ms.custom: template-quickstart, devx-track-azurecli
 
 # Quickstart: Deploy a virtual machine in Azure public MEC Preview using an ARM template
 
-In this quickstart, you learn how to use an Azure Resource Manager template (ARM template) to deploy an Ubuntu Linux virtual machine (VM) in Azure public multi-access edge compute (MEC) Preview.
+In this quickstart, you learn how to use an Azure Resource Manager (ARM) template to deploy an Ubuntu Linux virtual machine (VM) in Azure public multi-access edge compute (MEC) Preview.
 
 [!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-introduction.md)]
 
-An [ARM template](../azure-resource-manager/templates/overview.md) is a JavaScript Object Notation (JSON) file that defines the infrastructure and configuration for your project. The template uses declarative syntax. In declarative syntax, you describe your intended deployment without writing the sequence of programming commands to create the deployment.
-
 ## Prerequisites
 
 - If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
@@ -25,8 +23,8 @@ An [ARM template](../azure-resource-manager/templates/overview.md) is a JavaScri
 
 [!INCLUDE [azure-cli-prepare-your-environment-no-header.md](../../includes/azure-cli-prepare-your-environment-no-header.md)]
 
-> [!NOTE]
-> Azure public MEC deployments are supported in Azure CLI versions 2.26 and later.
+   > [!NOTE]
+   > Azure public MEC deployments are supported in Azure CLI versions 2.26 and later.
 
 ## Review the template
 
@@ -40,7 +38,9 @@ An [ARM template](../azure-resource-manager/templates/overview.md) is a JavaScri
    - Network security group
    - Virtual machine
 
-   Note that the Azure Edge Zone ID in the example ARM template is different from the display name of the Azure public MEC.
+   In this example ARM template:
+   - The Azure Edge Zone ID is different from the display name of the Azure public MEC.
+   - The Azure network security group has an inbound rule that allows SSH and HTTPS access from everywhere.
 
    ```json
    {
@@ -218,9 +218,8 @@ An [ARM template](../azure-resource-manager/templates/overview.md) is a JavaScri
                            "properties": {
                                "addressPrefix": "[variables('subnetPrefix')]",
                                "networkSecurityGroup": {
-                                   "id": "[resourceId('Microsoft.Network/networkSecurityGroups', variables('networkSecurityGroupName') )
-                                ]"
-                               }
+                                   "id": "[resourceId('Microsoft.Network/networkSecurityGroups', variables('networkSecurityGroupName'))]"
+                                }
                            }
                        }
                    ]
@@ -314,9 +313,6 @@ An [ARM template](../azure-resource-manager/templates/overview.md) is a JavaScri
    }
    ```
 
-> [!NOTE]
-> The Azure network security group has an inbound rule that allows SSH and HTTPS access from everywhere.
-
 ## Deploy the ARM template using the Azure CLI
 
 1. Save the contents of the sample ARM template from the previous section in a file named *azurepublicmecDeploy.json*.

articles/public-multi-access-edge-compute-mec/quickstart-create-vm-cli.md

@@ -21,8 +21,8 @@ In this quickstart, you learn how to use Azure CLI to deploy a Linux virtual mac
 
 [!INCLUDE [azure-cli-prepare-your-environment-no-header.md](../../includes/azure-cli-prepare-your-environment-no-header.md)]
 
-> [!NOTE]
-> Azure public MEC deployments are supported in Azure CLI versions 2.26 and later.
+   > [!NOTE]
+   > Azure public MEC deployments are supported in Azure CLI versions 2.26 and later.
 
 ## Sign in to Azure and set your subscription
 

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

@@ -6,10 +6,10 @@ items:
   items:
   - name: What is Azure public MEC?
     href: overview.md
+  - name: Considerations for deployment
+    href: considerations-for-deployment.md    
   - name: Key concepts
     href: key-concepts.md   
-  - name: Considerations for deployment
-    href: considerations-for-deployment.md
 - name: Quickstarts
   expanded: true
   items:

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

@@ -91,7 +91,7 @@ In this tutorial, you learn how to:
 
 ## Create a public IP address
 
-1. Add the latest network Go SDK to your import list:
+1. Add the latest network Go SDK to your import list.
 
    ```go
    import ( 

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

@@ -55,7 +55,7 @@ In this tutorial, you learn how to:
 
 ## Provision a virtual machine
 
-1. Create a Python file named *provision_vm_edge.py* to populate it with the following Python script. The script deploys VM and its associated dependency in Azure public MEC. The comments in the script explain the details.
+1. Create a Python file named *provision_vm_edge.py* and populate it with the following Python script. The script deploys VM and its associated dependency in Azure public MEC. The comments in the script explain the details.
 
    ```Python
    # Import the needed credential and management objects from the libraries.
@@ -290,7 +290,7 @@ az group delete --name PythonAzureExample-VM-rg --yes
 
 ## Next steps
 
-To contact the Azure public MEC product team:
+For questions about Azure public MEC, contact the product team:
 
 > [!div class="nextstepaction"]
 > [Azure public MEC product team](https://aka.ms/azurepublicmec)