PR review fixes

Author: shellyhaverkamp

articles/healthcare-apis/dicom/change-feed-overview.md

@@ -1,11 +1,11 @@
 ---
 title:  Change feed overview for the DICOM service in Azure Health Data Services
-description: Learn how to use the change feed in the DICOM service to access the logs of all the changes that occur in your orgganization's medical imaging data. The change feed allows you to query, process, and act upon the change events in a scalable and efficient way.
+description: Learn how to use the change feed in the DICOM service to access the logs of all the changes that occur in your organization's medical imaging data. The change feed allows you to query, process, and act upon the change events in a scalable and efficient way.
 author: mmitrik
 ms.service: healthcare-apis
 ms.subservice: dicom
 ms.topic: conceptual
-ms.date: 1/17/2024
+ms.date: 1/18/2024
 ms.author: mmitrik
 ---
 
@@ -48,12 +48,12 @@ Metadata            | object    | Optionally, the current DICOM metadata if the
 State    | Description
 :------- | :---
 current  | This instance is the current version.
-replaced | This instance has been replaced by a new version.
-deleted  | This instance has been deleted and is no longer available in the service.
+replaced | This instance is replaced with a new version.
+deleted  | This instance is deleted and is no longer available in the service.
 
 ## Change feed
 
-The change feed resource is a collection of events that have occurred within the DICOM server.
+The change feed resource is a collection of events that occurred within the DICOM server.
 
 ### Version 2
 
@@ -152,7 +152,7 @@ limit           | int      | The maximum value of the sequence number relative t
 includeMetadata | bool     | Indicates whether or not to include the DICOM metadata | `true` | | |
 
 ## Latest change feed
-The latest change feed resource represents the latest event that has occurred within the DICOM Server.
+The latest change feed resource represents the latest event that occurred within the DICOM server.
 
 ### Request
 ```http
@@ -208,15 +208,15 @@ includeMetadata | bool | Indicates whether or not to include the metadata | `tru
 2. On some regular polling interval, the application performs the following actions:
     * Fetches the latest sequence number from the `/changefeed/latest` endpoint
     * Fetches the next set of changes for processing by querying the change feed with the current offset
-        * For example, if the application has currently processed up to sequence number 15 and it only wants to process at most 5 events at once, then it should use the URL `/changefeed?offset=15&limit=5`
+        * For example, if the application processed up to sequence number 15 and it only wants to process at most five events at once, then it should use the URL `/changefeed?offset=15&limit=5`
     * Processes any entries return by the `/changefeed` resource
     * Updates its current sequence number to either:
         1. The maximum sequence number returned by the `/changefeed` resource
         2. The `offset` + `limit` if no change events were returned from the `/changefeed` resource, but the latest sequence number returned by `/changefeed/latest` is greater than the current sequence number used for `offset`
 
 ### Other potential usage patterns
 
-Change feed support is well suited for scenarios that process data based on objects that have changed. For example, it can be used to:
+Change feed support is well-suited for scenarios that process data based on objects that are changed. For example, it can be used to:
 
 * Build connected application pipelines like ML that react to change events or schedule executions based on created or deleted instance.
 * Extract business analytics insights and metrics, based on changes that occur to your objects.

articles/healthcare-apis/dicom/dicom-services-conformance-statement-v2.md

@@ -6,7 +6,7 @@ author: mmitrik
 ms.service: healthcare-apis
 ms.subservice: dicom
 ms.topic: reference
-ms.date: 1/17/2024
+ms.date: 1/18/2024
 ms.author: mmitrik
 ---
 
@@ -271,7 +271,7 @@ An example response with `Accept` header `application/dicom+json` with a FailedA
 | `272`   | The store transaction didn't store the instance because of a general failure in processing the operation. |
 | `43264` | The DICOM instance failed the validation. |
 | `43265` | The provided instance `StudyInstanceUID` didn't match the specified `StudyInstanceUID` in the store request. |
-| `45070` | A DICOM instance with the same `StudyInstanceUID`, `SeriesInstanceUID`, and `SopInstanceUID` was already stored stored. If you want to update the contents, delete this instance first. |
+| `45070` | A DICOM instance with the same `StudyInstanceUID`, `SeriesInstanceUID`, and `SopInstanceUID` was already stored. If you want to update the contents, delete this instance first. |
 | `45071` | A DICOM instance is being created by another process, or the previous attempt to create failed and the cleanup process isn't complete. Delete the instance first before attempting to create again. |
 
 #### Store warning reason codes

articles/healthcare-apis/dicom/pull-dicom-changes-from-change-feed.md

@@ -5,7 +5,7 @@ author: mmitrik
 ms.service: healthcare-apis
 ms.subservice: dicom
 ms.topic: how-to
-ms.date: 1/17/2024
+ms.date: 1/18/2024
 ms.author: mmitrik
 ---
 

articles/healthcare-apis/dicom/toc.yml

@@ -45,6 +45,8 @@ items:
       href: dicom-configure-azure-rbac.md
     - name: Enable audit and diagnostic logging
       href: enable-diagnostic-logging.md
+    - name: Access DICOM Change Feed logs 
+      href: pull-dicom-changes-from-change-feed.md
     - name: Import DICOM files
       href: import-files.md
     - name: Export DICOM files

articles/healthcare-apis/dicom/update-files.md

@@ -1,11 +1,11 @@
 ---
-title: Update DICOM files in the DICOM service
+title: Update files in the DICOM service in Azure Health Data Services
 description: Learn how to use the bulk update API in Azure Health Data Services to modify DICOM attributes for multiple files in the DICOM service. This article explains the benefits, requirements, and steps of the bulk update operation.
 author: mmitrik
 ms.service: healthcare-apis
 ms.subservice: dicom
 ms.topic: how-to
-ms.date: 10/27/2023
+ms.date: 1/18/2024
 ms.author: mmitrik
 ---
 
@@ -164,7 +164,7 @@ Any attributes in the [Patient Identification Module](https://dicom.nema.org/dic
 | Patient's Name   | (0010,0010)   | Patient's full name   |
 | Patient ID       | (0010,0020)   | Primary hospital identification number or code for the patient. |
 | Other Patient IDs| (0010,1000) | Other identification numbers or codes used to identify the patient. 
-| Type of Patient ID| (0010,0022) |  The type of identifier in this item. Enumerated Values: TEXT RFID BARCODE Note The identifier is coded as a string regardless of the type, not as a binary value. 
+| Type of Patient ID| (0010,0022) |  The type of identifier in this item. Enumerated Values: TEXT RFID BARCODE Note that the identifier is coded as a string regardless of the type, not as a binary value. 
 | Other Patient Names| (0010,1001) | Other names used to identify the patient. 
 | Patient's Birth Name| (0010,1005) | Patient's birth name. 
 | Patient's Mother's Birth Name| (0010,1060) | Birth name of patient's mother. 
@@ -197,7 +197,7 @@ Any attributes in the [Patient Identification Module](https://dicom.nema.org/dic
 | Patient Species Description | (0010,2201) | The species of the patient. |
 | Patient Breed Description | (0010,2292) | The breed of the patient. See Section C.7.1.1.1.1. |
 | Breed Registration Number | (0010,2295) | Identification number of a veterinary patient within the registry. |
-| Issuer of Patient ID | (0010,0021) | Identifier of the Assigning Authority (system, organization, agency, or department) that issued the Patient ID. ```
+| Issuer of Patient ID | (0010,0021) | Identifier of the Assigning Authority (system, organization, agency, or department) that issued the Patient ID.
 
 #### General study module
 | Attribute Name   | Tag           | Description           |