Addressing PR reviewer feedback.

Author: msjasteppe

articles/healthcare-apis/events/events-consume-logic-apps.md

@@ -344,4 +344,4 @@ For more information about FHIR events, see
 >[!div class="nextstepaction"]
 >[What are Events?](./events-overview.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-deploy-portal.md

@@ -88,4 +88,4 @@ To learn how to export Event Grid system diagnostic logs and metrics, see
 >[!div class="nextstepaction"]
 >[How to export Events diagnostic logs and metrics](./events-display-metrics.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-disable-delete-workspace.md

@@ -1,5 +1,5 @@
 ---
-title: Disable Events and delete workspaces - Azure Health Data Services
+title: Disable events and delete workspaces - Azure Health Data Services
 description: This article provides resources on how to disable Events and delete workspaces.
 services: healthcare-apis
 author: msjasteppe
@@ -10,13 +10,13 @@ ms.date: 07/06/2022
 ms.author: jasteppe
 ---
 
-# Disable Events and delete workspaces
+# Disable events and delete workspaces
 
 In this article, you'll learn how to disable the Events feature and delete workspaces in the Azure Health Data Services.
 
-## Disable Events
+## Disable events
 
-To disable Events from sending event messages for a single Event Subscription, the Event Subscription must be deleted.
+To disable events from sending event messages for a single Event Subscription, the Event Subscription must be deleted.
 
 1. Select the Event Subscription to be deleted. In this example, we'll be selecting an Event Subscription named **fhir-events**.
 
@@ -51,4 +51,4 @@ For more information about how to troubleshoot Events, see
 >[!div class="nextstepaction"]
 >[Troubleshoot Events](./events-troubleshooting-guide.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-display-metrics.md

@@ -42,4 +42,4 @@ To learn how to export Events Azure Event Grid system diagnostic logs and metric
 >[!div class="nextstepaction"]
 >[Configure Events diagnostic logs and metrics exporting](./events-export-logs-metrics.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-export-logs-metrics.md

@@ -35,4 +35,4 @@ To learn how to display Events metrics in the Azure portal, see
 >[!div class="nextstepaction"]
 >[How to display Events metrics](./events-display-metrics.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-faqs.md

@@ -52,7 +52,7 @@ You can use the Event Grid filtering feature. There are unique identifiers in th
 
 ### Can I use the same subscriber for multiple workspaces or multiple FHIR accounts?
 
-Yes. We recommend that you use different subscribers for each individual FHIR accounts to process in isolated scopes.
+Yes. We recommend that you use different subscribers for each individual FHIR account to process in isolated scopes.
 
 ### Is Event Grid compatible with HIPAA and HITRUST compliance obligations?
 
@@ -77,4 +77,4 @@ Generally, we recommend that developers ensure idempotency for the event subscri
 
 [FAQs about Azure Health Data Services MedTech service](../iot/iot-connector-faqs.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-message-structure.md

@@ -177,4 +177,4 @@ For more information about deploying Events, see
 >[!div class="nextstepaction"]
 >[Deploying Events in the Azure portal](./events-deploy-portal.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-overview.md

@@ -53,7 +53,7 @@ Use Events to send FHIR resource change messages to services like [Azure Event H
 
 ## Secure
 
-Built on a platform that supports protected health information (PHI) and personal identifiable information (PII) data compliance with privacy, safety, and security in mind, the Events messages do not transmit sensitive data as part of the message payload.
+Built on a platform that supports protected health information and personally identifiable information data compliance with privacy, safety, and security in mind, the Events messages do not transmit sensitive data as part of the message payload.
 
 Use [Azure Managed identities](../../active-directory/managed-identities-azure-resources/overview.md) to provide secure access from your Event Grid system topic to the Events message receiving endpoints of your choice. 
 
@@ -74,4 +74,4 @@ For Events troubleshooting resources, see
 >[!div class="nextstepaction"]
 >[Events troubleshooting guide](./events-troubleshooting-guide.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/events-troubleshooting-guide.md

@@ -61,4 +61,4 @@ To learn about frequently asked questions (FAQs) about Events, see
 >[!div class="nextstepaction"]
 >[Frequently asked questions about Events](./events-faqs.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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/events/index.yml

@@ -1,7 +1,7 @@
 ### YamlMime:Landing
 
 title: Events
-summary: Events documentation page for Azure Health Data Services . 
+summary: Events documentation page for Azure Health Data Services. 
 
 metadata:
   title: Azure Health Data Services MedTech service