Merge pull request #225848 from msjasteppe/quick-edits

Small edits.

Author: prmerger-automator[bot]

articles/event-grid/event-schema-azure-health-data-services.md

@@ -7,13 +7,13 @@ ms.date: 01/31/2023
 
 # Azure Health Data Services as an Event Grid source
 
-This article provides the properties and schema for Azure Health Data Services events. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md).
+This article provides the properties and schema for Azure Health Data Services Events. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md).
 
 ## Available Event types
 
 ### List of Events for Azure Health Data Services REST APIs
 
-These events are triggered when a Fast Healthcare Interoperability Resources (FHIR®) resource is created, updated, or deleted by calling the FHIR service REST APIs.
+These events are triggered when a Fast Healthcare Interoperability Resources (FHIR®) Observation is created, updated, or deleted by calling the FHIR service REST APIs.
 
  |Event name|Description|
  |----------|-----------|
@@ -29,7 +29,7 @@ These Events are triggered when a DICOM image is created or deleted by calling t
  |**DicomImageDeleted** |The event emitted after a DICOM image is deleted successfully.|
 
 ## Example events
-This section contains examples of what Azure Health Data Services Events message data would look like for each FHIR resource and DICOM image event.
+This section contains examples of what Azure Health Data Services Events message data would look like for each FHIR Observation and DICOM image event.
 
 > [!NOTE]
 > Events data looks similar to these examples with the `metadataVersion` property set to a value of `1`.

articles/healthcare-apis/iot/index.yml

@@ -1,11 +1,11 @@
 ### YamlMime:Landing
 
 title: MedTech service documentation
-summary: MedTech service documentation for the Azure Health Data Services. The MedTech service is a service of the Azure Health Data Services designed to ingest device message data from multiple devices, transform the data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
+summary: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device message data from multiple devices, transform that data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
 
 metadata:
   title: Azure Health Data Services MedTech service
-  description: MedTech service documentation for the Azure Health Data Services. The MedTech service is a service of the Azure Health Data Services designed to ingest device message data from multiple devices, transform the data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. 
+  description: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device message data from multiple devices, transform that data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. 
   services: healthcare-apis
   ms.service: healthcare-apis
   ms.subservice: data-transformation