adding links and small edits

Author: mcevoy-building7

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

@@ -13,6 +13,8 @@ ms.author: v-smcevoy
 
 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).
 
+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 Resource (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:
 
 ## Prerequisites

articles/healthcare-apis/iot/deploy-08-new-ps-cli.md

@@ -13,8 +13,6 @@ ms.author: v-smcevoy
 
 In this quickstart article, you'll learn how to use Azure PowerShell and Azure CLI to deploy the MedTech service using an Azure Resource Manager (ARM) template. For more information about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md). Calling the template from PowerShell or CLI provides automation that enables you to distribute your deployment to large numbers of developers. Using PowerShell and CLI allows for modifiable automation capabilities that will speed up your deployment configuration more efficiently in enterprise environments.
 
-The ARM template used in this article is available from the [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/iotconnectors/) site using the **azuredeploy.json** file located on [GitHub](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/azuredeploy.json).
-
 ## Resources provided by the ARM template
 
 The ARM template will help you automatically configure and deploy the following resources. Each one can be modified to meet your deployment requirements.
@@ -29,17 +27,21 @@ The ARM template will help you automatically configure and deploy the following
   - system-assigned managed identity access roles needed to read and write to the FHIR service (named **FHIR Data Writer**)
 - An output file containing the ARM template deployment results (named **medtech_service_ARM_template_deployment_results.txt**). The file is located in the directory from which you ran the script.
 
+The ARM template used in this article is available from the [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/iotconnectors/) site using the **azuredeploy.json** file located on [GitHub](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/azuredeploy.json).
+
+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 Resource (FHIR) Observation.
+
 ## Azure PowerShell prerequisites
 
-You need to have the following prerequisites if you're using Azure PowerShell:
+When you begin, you need to have the following prerequisites if you're using Azure PowerShell:
 
 - An Azure account with an active subscription. If you don't have an Azure subscription, see [Subscription decision guide](/azure/cloud-adoption-framework/decision-guides/subscriptions/).
 
 - If you want to run the code locally, use [Azure PowerShell](/powershell/azure/install-az-ps).
 
 ## Azure CLI prerequisites
 
-You need to have the following prerequisites if you're using Azure CLI:
+When you begin, you need to have the following prerequisites if you're using Azure CLI:
 
 - An Azure account with an active subscription. If you don't have an Azure subscription, see [Subscription decision guide](/azure/cloud-adoption-framework/decision-guides/subscriptions/).