Merge pull request #216374 from msjasteppe/iot-deploy-updates-2

Iot deploy updates 2

Author: LJSpiller

articles/healthcare-apis/iot/deploy-02-new-button.md

@@ -5,15 +5,15 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 10/10/2022
+ms.date: 10/28/2022
 ms.author: jasteppe
 ---
 
 # Deploy the MedTech service with an Azure Resource Manager Quickstart template
 
-In this article, you'll learn how to deploy the MedTech service in the Azure portal using an Azure Resource Manager (ARM) Quickstart template. This template will be used with the **Deploy to Azure** button to make it easy to provide the information you need to automatically set up the infrastructure and configuration of your deployment. For more information about Azure ARM templates, see [What are ARM templates?](../../azure-resource-manager/templates/overview.md).
+In this article, you'll learn how to deploy the MedTech service in the Azure portal using an Azure Resource Manager (ARM) Quickstart template. This template will be used with the **Deploy to Azure** button to make it easy to provide the information you need to automatically create the infrastructure and configuration of your deployment. For more information about Azure Resource Manager (ARM) templates, see [What are ARM templates?](../../azure-resource-manager/templates/overview.md).
 
-If you need to see a diagram with information on the MedTech service deployment, there is an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
+If you need to see a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
 
 There are four simple tasks you need to complete in order to deploy MedTech service with the ARM template **Deploy to Azure** button. They are:
 
@@ -25,15 +25,15 @@ In order to begin deployment, you need to have the following prerequisites:
 
 - Two resource providers registered with your Azure subscription: **Microsoft.HealthcareApis** and **Microsoft.EventHub**. To learn more about registering resource providers, see [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
 
-When you've fulfilled these two prerequisites, you are ready to begin the second task.
+When you've fulfilled these two prerequisites, you're ready to begin the second task.
 
 ## Deploy to Azure button
 
 Next, you need to select the ARM template **Deploy to Azure** button here:
 
  [![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).
 
-This button will call a template from the Azure ARM QuickStart template library to get information from your Azure subscription environment and begin deploying the MedTech service.
+This button will call a template from the Azure Resource Manager (ARM) Quickstart template library to get information from your Azure subscription environment and begin deploying the MedTech service.
 
 After you select the **Deploy to Azure** button, it may take a few minutes to implement the following resources and roles:
 
@@ -73,7 +73,7 @@ When the Azure portal screen appears, your next task is to fill out five fields
 
 Don't change the **Device Mapping** and **Destination Mapping** default values at this time.
 
-Select the **Review + create** button after all the fields are filled out. This will review your input and check to see if all your values are valid.
+Select the **Review + create** button after all the fields are filled out. This selection will review your input and check to see if all your values are valid.
 
 When the validation is successful, select the **Create** button to begin the deployment. After a brief wait, a message will appear telling you that your deployment is complete.
 
@@ -100,13 +100,13 @@ Now that the MedTech service is successfully deployed, there are three post-depl
 
 In this article, you learned how to deploy the MedTech service in the Azure portal using a Quickstart ARM template with a **Deploy to Azure** button. To learn more about other methods of deployment, see
 
->[!div class="nextstepaction"]
->[Choosing a method of deployment for MedTech service in Azure](deploy-iot-connector-in-azure.md)
+> [!div class="nextstepaction"]
+> [Choosing a method of deployment for MedTech service in Azure](deploy-iot-connector-in-azure.md)
 
->[!div class="nextstepaction"]
->[How to manually deploy MedTech service with Azure portal](deploy-03-new-manual.md)
+> [!div class="nextstepaction"]
+> [How to manually deploy MedTech service with Azure portal](deploy-03-new-manual.md)
 
->[!div class="nextstepaction"]
->[How to deploy MedTech service using an ARM template and Azure PowerShell or Azure CLI](deploy-08-new-ps-cli.md)
+> [!div class="nextstepaction"]
+> [How to deploy MedTech service using an ARM template and Azure PowerShell or Azure CLI](deploy-08-new-ps-cli.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/deploy-03-new-manual.md

@@ -5,21 +5,21 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 10/10/2022
+ms.date: 10/28/2022
 ms.author: jasteppe
 ---
 
 # How to manually deploy MedTech service using the Azure portal
 
-You may prefer to manually deploy MedTech service if you need to track every step of the developmental process. This might be necessary if you have to customize or troubleshoot your deployment. Manual deployment will help you by providing all the details for implementing each task.
+You may prefer to manually deploy MedTech service if you need to track every step of the developmental process. Manual deployment might be necessary if you have to customize or troubleshoot your deployment. Manual deployment will help you by providing all the details for implementing each task.
 
 The explanation of MedTech service manual deployment using the Azure portal is divided into three parts that cover each of key tasks required:
 
 - Part 1: Prerequisites (see Prerequisites below)
-- Part 2: Configuration (see [Configure for manual deployment](./deploy-05-new-config.md))
-- Part 3: Deployment and Post Deployment (see [Manual deployment and post-deployment](./deploy-06-new-deploy.md))
+- Part 2: Configuration (see [Configure for manual deployment](deploy-05-new-config.md))
+- Part 3: Deployment and Post Deployment (see [Manual deployment and post-deployment](deploy-06-new-deploy.md))
 
-If you need a diagram with information on the MedTech service deployment, there is an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
+If you need a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
 
 ## Part 1: Prerequisites
 
@@ -37,11 +37,11 @@ The first thing you need to do is determine if you have a valid Azure subscripti
 
 ## Deploy a resource group in the Azure portal
 
-When you log in to your Azure account, go to Azure portal and select the Create a resource button. Then enter "Azure Health Data Services" in the "Search services and marketplace" box. This should take you to the Azure Health Data Services page.
+When you sign in to your Azure account, go to the Azure portal and select the **Create a resource** button. Enter "Azure Health Data Services" in the "Search services and marketplace" box. This step should take you to the Azure Health Data Services page.
 
 ## Deploy a workspace in Azure Health Data Services
 
-The first resource you must create is a workspace to contain your Azure Health Data Services resources. Start by selecting Create from the Azure Health Data Services resource page. This will take you to the first page of Create Azure Health Data Services workspace, when you need to do the following 8 steps:
+The first resource you must create is a workspace to contain your Azure Health Data Services resources. Start by selecting Create from the Azure Health Data Services resource page. This step will take you to the first page of Create Azure Health Data Services workspace, when you need to do the following eight steps:
 
 1. Fill in the resource group you want to use or create a new one.
 
@@ -53,13 +53,13 @@ The first resource you must create is a workspace to contain your Azure Health D
 
 5. Choose whether you want a public or private endpoint. 
 
-6. Create tags if you want to use them. They are optional.
+6. Create tags if you want to use them. They're optional.
 
-7. When you are ready to continue, select the Review + create tab.
+7. When you're ready to continue, select the Review + create tab.
 
 8. Select the Create button to deploy your workspace. 
 
-After a short delay, you will start to see information about your new workspace. Make sure you wait until all parts of the screen are displayed. If your initial deployment was successful, you should see:
+After a short delay, you'll start to see information about your new workspace. Make sure you wait until all parts of the screen are displayed. If your initial deployment was successful, you should see:
 
 - "Your deployment is complete"
 - Deployment name
@@ -68,7 +68,7 @@ After a short delay, you will start to see information about your new workspace.
 
 ## Deploy an event hub in the Azure portal using a namespace
 
-An event hub is the next prerequisite you need to create. It is important because it receives the data flow from a medical device and stores it there until MedTech can pick up the data and translate it into a FHIR service Observation resource. Because Internet propagation times are indeterminate, the event hub is needed to buffer the data and store it for as much as 24 hours before expiring.
+An event hub is the next prerequisite you need to create. It's an important step because the event hub receives the data flow from a device and stores it until the MedTech service picks up the device data. Once the MedTech service picks up the device data, it can begin the transformation of the device data into a FHIR service Observation resource. Because Internet propagation times are indeterminate, the event hub is needed to buffer the data and store it for as much as 24 hours before expiring.
 
 Before you can create an event hub, you must create a namespace in Azure portal to contain it. For more information on how To create a namespace and an event hub, see [Azure Event Hubs namespace and event hub deployed in the Azure portal](../../event-hubs/event-hubs-create.md).
 
@@ -92,9 +92,9 @@ After your prerequisites are successfully completed, you can go on to Part 2: Co
 
 ## Next steps
 
-When you are ready to begin Part 2 of Manual Deployment, see
+When you're ready to begin Part 2 of Manual Deployment, see
 
->[!div class="nextstepaction"]
->[Part 2: Configure the MedTech service for manual deployment using the Azure portal](deploy-05-new-config.md)
+> [!div class="nextstepaction"]
+> [Part 2: Configure the MedTech service for manual deployment using the Azure portal](deploy-05-new-config.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.