More edits

Author: msjasteppe

articles/healthcare-apis/iot/concepts-power-bi.md

@@ -15,7 +15,7 @@ In this article, learn about using the MedTech service and Microsoft Power Busin
 
 ## The MedTech service and Power BI reference architecture
 
-This reference architecture shows the basic components of using the Microsoft cloud services to enable Power BI on top of Internet of Things (IoT) and FHIR data.
+This reference architecture shows the basic components of using the Microsoft cloud services to enable Power BI on top of Internet of Things (IoT) and FHIR® data.
 
 You can even embed Power BI dashboards inside the Microsoft Teams client to further enhance care team coordination. For more information on embedding Power BI in Teams, see [Embed Power BI content in Microsoft Teams](/power-bi/collaborate-share/service-embed-report-microsoft-teams).
 

articles/healthcare-apis/iot/concepts-teams.md

@@ -15,7 +15,7 @@ In this article, learn about using the MedTech service and Microsoft Teams for n
 
 ## The MedTech service and Teams notifications reference architecture
 
-When combining the MedTech service, the FHIR service, and Teams, you can enable multiple care solutions.
+When combining the MedTech service, the FHIR® service, and Teams, you can enable multiple care solutions.
 
 The diagram is a MedTech service to Teams notifications conceptual architecture for enabling the MedTech service, the FHIR service, and the Teams Patient App.
 

articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md

@@ -170,7 +170,7 @@ When deployment is completed, the following resources and access roles are creat
 
 * Health Data Services workspace.
 
-* Health Data Services FHIR service.
+* Health Data Services FHIR® service.
 
 * Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles:
 

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

@@ -30,7 +30,7 @@ The following diagram outlines the basic steps of the MedTech service deployment
 
 ## ARM template including an Azure Iot Hub 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 and Azure IoT Hub are fully functional including conforming and valid device and FHIR destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
+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 and Azure IoT Hub are fully functional including conforming and valid device and FHIR® destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
 
 [![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-with-iothub%2Fazuredeploy.json)
 

articles/healthcare-apis/iot/deploy-json-powershell-cli.md

@@ -165,7 +165,7 @@ When deployment is completed, the following resources and access roles are creat
 
 * Health Data Services workspace.
 
-* Health Data Services FHIR service.
+* Health Data Services FHIR® service.
 
 * Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles:
 

articles/healthcare-apis/iot/deploy-manual-portal.md

@@ -31,7 +31,7 @@ The first step is to deploy the MedTech service prerequisite resources:
 * Azure resource group
 * Azure Event Hubs namespace and event hub
 * Azure Health Data services workspace
-* Azure Health Data Services FHIR service
+* Azure Health Data Services FHIR® service
 
 Once the prerequisite resources are available, deploy:
 

articles/healthcare-apis/iot/device-messages-through-iot-hub.md

@@ -13,7 +13,7 @@ ms.author: jasteppe
 
 # Tutorial: Receive device messages through Azure IoT Hub
 
-The MedTech service can receive messages from devices you create and manage through an IoT hub in [Azure IoT Hub](../../iot-hub/iot-concepts-and-iot-hub.md). This tutorial uses an Azure Resource Manager template (ARM template) and a **Deploy to Azure** button to deploy a MedTech service. The template also deploys an IoT hub to create and manage devices, and message routes device messages to an event hub for the MedTech service to read and process. After device data processing, the FHIR resources are persisted in the FHIR service, which is also included in the template.
+The MedTech service can receive messages from devices you create and manage through an IoT hub in [Azure IoT Hub](../../iot-hub/iot-concepts-and-iot-hub.md). This tutorial uses an Azure Resource Manager template (ARM template) and a **Deploy to Azure** button to deploy a MedTech service. The template also deploys an IoT hub to create and manage devices, and message routes device messages to an event hub for the MedTech service to read and process. After device data processing, the FHIR® resources are persisted in the FHIR service, which is also included in the template.
 
 :::image type="content" source="media\device-messages-through-iot-hub\device-message-flow-with-iot-hub.png" border="false" alt-text="Diagram of the IoT device message flow through an IoT hub and event hub, and then into the MedTech service." lightbox="media\device-messages-through-iot-hub\device-message-flow-with-iot-hub.png":::
 

articles/healthcare-apis/iot/frequently-asked-questions.md

@@ -20,7 +20,7 @@ The MedTech service is available in these Azure regions: [Products available by
 
 ## Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
 
-No. The MedTech service currently only supports the Azure Health Data Services FHIR service for the persistence of transformed device data. The open-source version of the MedTech service supports the use of different FHIR services. 
+No. The MedTech service currently only supports the Azure Health Data Services FHIR® service for the persistence of transformed device data. The open-source version of the MedTech service supports the use of different FHIR services. 
 
 To learn about the MedTech service open-source projects, see [Open-source projects](git-projects.md).