Merge pull request #219175 from msjasteppe/medtech-toc-updates

Medtech toc updates

Author: Court72

articles/healthcare-apis/iot/deploy-05-new-config.md

@@ -5,11 +5,11 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 10/28/2022
+ms.date: 11/21/2022
 ms.author: jasteppe
 ---
 
-# Part 2: Configure the MedTech service for manual deployment using the Azure portal
+# Quickstart: Part 2: Configure the MedTech service for manual deployment using the Azure portal
 
 Before you can manually deploy the MedTech service, you must complete the following configuration tasks:
 

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

@@ -5,11 +5,11 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 10/28/2022
+ms.date: 11/21/2022
 ms.author: jasteppe
 ---
 
-# Part 3: Manual deployment and post-deployment of MedTech service
+# Quickstart: Part 3: Manual deployment and post-deployment of MedTech service
 
 When you're satisfied with your configuration and it has been successfully validated, you can complete the deployment and post-deployment process.
 
@@ -94,13 +94,13 @@ Now that you have granted access to the device message event hub and the FHIR se
 
 ## Next steps
 
-In this article, you learned how to perform the manual deployment and  post-deployment steps to implement your MedTech service. To learn more about other methods of deployment, see
+In this article, you learned how to perform the manual deployment and post-deployment steps to implement your MedTech service. 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"]
-> [Deploy the MedTech service with a QuickStart template](deploy-02-new-button.md)
+> [Deploy the MedTech service with an Azure Resource Manager template](deploy-02-new-button.md)
 
 > [!div class="nextstepaction"]
 > [Using Azure PowerShell and Azure CLI to deploy the MedTech service using Azure Resource Manager templates](deploy-08-new-ps-cli.md)

articles/healthcare-apis/iot/deploy-iot-connector-in-azure.md

@@ -5,33 +5,33 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 11/18/2022
+ms.date: 11/21/2022
 ms.author: jasteppe
 ---
 
 # Quickstart: Choose a deployment method
 
-MedTech service provides multiple methods for deploying it into an Azure Platform as a service (PaaS) configuration. Each method has different advantages that will allow you to customize your development environment to suit your needs.
+MedTech service provides multiple methods for deploying it into an Azure Platform as a Service (PaaS) configuration. Each method has different advantages that will allow you to customize your development environment to suit your needs.
 
 The different deployment methods are:
 
 - Azure Resource Manager (ARM) template with Deploy to Azure button
 - Azure PowerShell and Azure CLI automation
-- Manual deployment
+- Azure portal manual deployment
 
 ## Azure Resource Manager template with Deploy to Azure button
 
 Using an ARM template with Azure portal is the easiest and fastest deployment method because it automates most of your configuration with the touch of a **Deploy to Azure** button. This button automatically generates the following configurations and resources: managed identity Azure role-based access (RBAC) roles, a provisioned workspace and namespace, an Event Hubs instance, a Fast Healthcare Interoperability Resources (FHIR®) service instance, and a MedTech service instance. All you need to add are post-deployment device mapping, destination mapping, and a shared access policy key. This method simplifies your deployment, but doesn't allow for much customization.
 
-For more information about the ARM template and the Deploy to Azure button, see [Quickstart: Deploy MedTech service with Azure Resource Manager template](deploy-02-new-button.md).
+For more information about the ARM template and the Deploy to Azure button, see [Quickstart: Deploy MedTech service with an Azure Resource Manager template](deploy-02-new-button.md).
 
 ## Azure PowerShell and Azure CLI automation
 
 Azure provides Azure PowerShell and Azure CLI to speed up your configurations when used in enterprise environments. Deploying MedTech service with Azure PowerShell or Azure CLI can be useful for adding automation so that you can scale your deployment for a large number of developers. This method is more detailed but provides extra speed and efficiency because it allows you to automate your deployment.
 
 For more information about Using an ARM template with Azure PowerShell and Azure CLI, see [Quickstart: Using Azure PowerShell and Azure CLI to deploy the MedTech service using Azure Resource Manager templates](deploy-08-new-ps-cli.md).
 
-## Manual deployment
+## Azure portal manual deployment
 
 The manual deployment method uses the Azure portal to implement each deployment task individually. Using the manual deployment method will allow you to see all the details of how to complete the sequence of each deployment task. The manual deployment method can be beneficial if you need to customize or troubleshoot your deployment process. The manual deployment is the most complex method, but it provides valuable technical information and developmental options that will enable you to fine-tune your deployment precisely.
 

articles/healthcare-apis/iot/index.yml

@@ -29,7 +29,7 @@ landingContent:
             url: iot-data-flow.md
       - linkListType: quickstart
         links:
-          - text: Get started with the MedTech service
+          - text: Get started with MedTech service
             url: get-started-with-iot.md
 
   - title: Deploy MedTech service
@@ -40,9 +40,9 @@ landingContent:
             url: deploy-iot-connector-in-azure.md
       - linkListType: quickstart
         links:     
-          - text: Azure Resource Manager (ARM) template
+          - text: Azure Resource Manager template
             url: deploy-02-new-button.md
-          - text: Azure PowerShell and CLI
+          - text: Azure PowerShell and Azure CLI
             url: deploy-08-new-ps-cli.md
           - text: Azure portal
             url: deploy-03-new-manual.md

articles/healthcare-apis/iot/toc.yml

@@ -21,15 +21,15 @@ items:
       items:
       - name: Choose a deployment method
         href: deploy-iot-connector-in-azure.md
-      - name: Azure Resource Manager (ARM) template
+      - name: Azure Resource Manager template
         href: deploy-02-new-button.md
-      - name: Azure PowerShell and CLI
+      - name: Azure PowerShell and Azure CLI
         href: deploy-08-new-ps-cli.md
-      - name: Manual deployment - Prerequisites
+      - name: Azure portal - Prerequisites
         href: deploy-03-new-manual.md
-      - name: Manual deployment - Configure
+      - name: Azure portal - Configure
         href: deploy-05-new-config.md
-      - name: Manual deployment - Deploy
+      - name: Azure portal - Deploy
         href: deploy-06-new-deploy.md   
 - name: Tutorials
   expanded: true