More edits

Author: msjasteppe

articles/healthcare-apis/iot/deploy-new-choose.md

@@ -1,6 +1,6 @@
 ---
 title: Choose a deployment method for the MedTech service - Azure Health Data Services
-description: In this article, you'll learn about the different methods for deploying the MedTech service.
+description: In this article, learn about the different methods for deploying the MedTech service.
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
@@ -15,14 +15,20 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages that will allow you to customize your deployment to suit your needs and use cases.
+The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages allow you to customize your deployment to suit your needs and use cases.
 
-In this quickstart, you'll learn about these deployment methods:
+In this quickstart, learn about these deployment methods:
 
-- Azure Resource Manager template (ARM template) including an Azure Iot Hub using the **Deploy to Azure** button. 
-- ARM template using the **Deploy to Azure** button.
-- ARM template using Azure PowerShell or the Azure CLI.
-- Manually in the Azure portal. 
+* Azure Resource Manager template (ARM template) including an Azure Iot Hub using the **Deploy to Azure** button. 
+* ARM template using the **Deploy to Azure** button.
+* ARM template using Azure PowerShell or the Azure CLI.
+* Manually in the Azure portal. 
+
+## Deployment overview
+
+The following diagram outlines the basic steps of the MedTech service deployment. These basic steps may help you analyze the deployment options and determine which deployment method is best for you.
+
+:::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
 
 ## ARM template including an Azure Iot Hub using the Deploy to Azure button
 
@@ -34,30 +40,24 @@ To learn more about deploying the MedTech service including an Azure IoT Hub usi
 
 ## ARM template using the Deploy to Azure button
 
-Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal. The deployed MedTech service will still require conforming and valid device and FHIR destination mappings to be fully functional.
+Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal. The deployed MedTech service requires conforming and valid device and FHIR destination mappings to be fully functional.
 
  [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.healthcareapis%2Fworkspaces%2Fiotconnectors%2Fazuredeploy.json).
 
 To learn more about deploying the MedTech service using an ARM template and the **Deploy to Azure** button, see [Deploy the MedTech service using an Azure Resource Manager template](deploy-new-arm.md).
 
 ## ARM template using Azure PowerShell or the Azure CLI
 
-Using an ARM template with Azure PowerShell or the Azure CLI is a more advanced deployment method. This deployment method can be useful for adding automation and repeatability so that you can scale and customize your deployments. The deployed MedTech service will still require conforming and valid device and FHIR destination mappings to be fully functional.
+Using an ARM template with Azure PowerShell or the Azure CLI is a more advanced deployment method. This deployment method can be useful for adding automation and repeatability so that you can scale and customize your deployments. The deployed MedTech service requires conforming and valid device and FHIR destination mappings to be fully functional.
 
 To learn more about deploying the MedTech service using an ARM template and Azure PowerShell or the Azure CLI, see [Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md).
 
 ## Manually in the Azure portal
 
-Using the Azure portal manual deployment will allow you to see the details of each deployment step. The manual deployment has many steps, but it provides valuable technical information that may be useful for customizing and troubleshooting your MedTech service.
+Using the Azure portal manual deployment allows you to see the details of each deployment step. The manual deployment has many steps, but it provides valuable technical information that may be useful for customizing and troubleshooting your MedTech service.
 
 To learn more about deploying the MedTech service manually using the Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
 
-## Deployment overview
-
-The following diagram outlines the basic steps of the MedTech service deployment and shows how these steps fit together with its data processing procedures. These basic steps may help you analyze the deployment options and determine which deployment method is best for you.
-
-:::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
-
 > [!IMPORTANT]
 > If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group.
 >

articles/healthcare-apis/iot/get-started.md

@@ -15,16 +15,19 @@ ms.custom: mode-api
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-This article outlines the basic steps to get started with the MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md).
+This article and diagram outlines the basic steps to get started with the MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md). These basic steps may help you analyze the MedTech service deployment options and determine which deployment method is best for you.
 
 :::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing the MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
 
+> [!TIP]
+> See the MedTech service article, [Quickstart: Choose a deployment method for the MedTech service](deploy-new-choose.md), for a description of the different deployment methods that can help to simply and automate the deployment of the MedTech service. 
+
 ## Subscription prerequisites
 
 To begin the deployment, you need to determine if you have:
 
 * An active Azure subscription.
-* Azure role-based access control (Azure RBAC) role assignments at the subscription level for deploying resources and granting access permissions. The roles required for you to complete the deployment are: **Contributor and User Access Administrator** or **Owner**. The **Contributor** role allows you to provision resources, and the **User Access Administrator** role allows you to grant access between resources. The **Owner** role can perform both actions.  
+* Azure role-based access control (Azure RBAC) role assignments at the subscription level for deploying resources and granting access permissions. The roles required for you to complete the deployment are: **Contributor and User Access Administrator** or **Owner**. The **Contributor** role allows you to deploy resources, and the **User Access Administrator** role allows you to grant access between resources. The **Owner** role can perform both actions.  
 
 If you already have the appropriate active subscription and Azure RBAC role assignments, you can skip this section.
 
@@ -33,13 +36,6 @@ If you already have the appropriate active subscription and Azure RBAC role assi
 
 ## Deploy resources
 
-> [!TIP]
-> See these MedTech service articles that will help to simply and automate the deployment of the MedTech service. 
->
-> * [Tutorial: Receive device messages through Azure IoT Hub](device-messages-through-iot-hub.md).
->
-> * [Quickstart: Deploy the MedTech service using an Azure Resource Manager template](deploy-new-arm.md).
-
 After you obtain the required subscription prerequisites, the first step is to deploy the MedTech service prerequisite resources:
 
 * Azure resource group.
@@ -80,10 +76,14 @@ To learn about methods of deploying the MedTech service, see
 > [!div class="nextstepaction"]
 > [Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
-> For an overview of the MedTech service device mapping, see
+For an overview of the MedTech service device mapping, see
+
+> [!div class="nextstepaction"]
 > [Overview of the MedTech service device mapping](overview-of-device-mapping.md)
 
-> For an overview of the MedTech service FHIR destination mapping, see
+For an overview of the MedTech service FHIR destination mapping, see
+
+> [!div class="nextstepaction"]
 > [Overview of the MedTech service FHIR destination mapping](overview-of-fhir-destination-mapping.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.