cleanup per Acrolinx

Author: KendalBond007

articles/healthcare-apis/dicom/dicom-data-lake.md

@@ -12,7 +12,7 @@ ms.custom: mode-api
 
 #  Manage medical imaging data with the DICOM service and Azure Data Lake Storage
 
-The [DICOM® service](overview.md) provides cloud-scale storage for medical imaging data using the DICOMweb standard. The integration of the DICOM service with Azure Data Lake Storage means you gain full control of your imaging data and increased flexibility for accessing and working with that data through the Azure storage ecosystem and APIs.  
+The [DICOM® service](overview.md) provides cloud-scale storage for medical imaging data using the DICOMweb standard. The integration of the DICOM service with Azure Data Lake Storage means you gain full control of your imaging data. It provides increased flexibility for accessing and working with that data through the Azure storage ecosystem and APIs.  
 
 By using Azure Data Lake Storage with the DICOM service, organizations are able to:
 
@@ -21,7 +21,7 @@ By using Azure Data Lake Storage with the DICOM service, organizations are able
 - **Unlock new analytics and AI/ML scenarios** by using services that natively integrate with Azure Data Lake Storage, including Azure Synapse, Azure Databricks, Azure Machine Learning, and Microsoft Fabric. 
 - **Grant controls to manage storage permissions, access controls, tiers, and rules**. 
 
-Another benefit of Azure Data Lake Storage is that it connects to [Microsoft Fabric](/fabric/get-started/microsoft-fabric-overview). Microsoft Fabric is an end-to-end, unified analytics platform that brings together all the data and analytics tools that organizations needed to unlock the potential of their data, and lay the foundation for AI scenarios. By using Microsoft Fabric, you can use the rich ecosystem of Azure services to perform advanced analytics and AI/ML with medical imaging data, such as building and deploying machine learning models, creating cohorts for clinical trials, and generating insights for patient care and outcomes.
+Another benefit of Azure Data Lake Storage is that it connects to [Microsoft Fabric](/fabric/get-started/microsoft-fabric-overview). Microsoft Fabric is an end-to-end, unified analytics platform that brings together all the data and analytics tools. Organizations then have a unified way to unlock the potential of their data, and lay the foundation for AI scenarios. By using Microsoft Fabric, you can use the rich ecosystem of Azure services to perform advanced analytics and AI/ML with medical imaging data. This could include building and deploying machine learning models, creating cohorts for clinical trials, and generating insights for patient care and outcomes.
 
 To learn more about using Microsoft Fabric with imaging data, see [Get started using DICOM data in analytics workloads](get-started-with-analytics-dicom.md).
 
@@ -51,7 +51,7 @@ In addition to DICOM data, a small file to enable [health checks](#health-check)
 
 ## Permissions
 
-The DICOM service is granted access to the data like any other service or application accessing data in a storage account. Access can be revoked at any time without affecting your organization's ability to access the data. The DICOM service needs the ability to read, write, and delete files in the provided file system. This can be provided by granting the [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) role to the system-assigned or user-assigned managed identity attached to the DICOM service.
+The DICOM service is granted access to the data like any other service or application accessing data in a storage account. Access can be revoked at any time without affecting your organization's ability to access the data. The DICOM service needs the ability to read, write, and delete files in the provided file system. This can be provided by granting the [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) role to the system-assigned, or user-assigned managed identity attached to the DICOM service.
 
 ## Access tiers
 
@@ -61,8 +61,8 @@ To learn more about access tiers, including cost tradeoffs and best practices, s
 
 ## Health check
 
-The DICOM service writes a small file to the data lake every 30 seconds, following the [Data Contract](#data-contracts) to ensure it maintains access. Making any changes to files stored under the `healthCheck` sub-directory might result in incorrect status of the health check.
-If there is an issue with access, status and details are displayed by [Azure Resource Health](../../service-health/overview.md). Azure Resource Health specifies if any action is required to restore access, for example reinstating a role to the DICOM service's identity.
+The DICOM service writes a small file to the data lake every 30 seconds, following the [Data Contract](#data-contracts) to ensure it maintains access. Making any changes to files stored under the `healthCheck` subdirectory might result in incorrect status of the health check.
+If there's an issue with access, status and details are displayed by [Azure Resource Health](../../service-health/overview.md). Azure Resource Health specifies if any action is required to restore access, for example reinstating a role to the DICOM service's identity.
 
 ## Limitations
 

articles/healthcare-apis/dicom/dicom-extended-query-tags-overview.md

@@ -11,9 +11,9 @@ ms.author: mmitrik
 
 # Extended query tags
 
-By default, the DICOM® service supports querying on the DICOM tags specified in the [conformance statement](dicom-services-conformance-statement-v2.md#searchable-attributes). By enabling extended query tags, the list of tags can easily be expanded based on the application's needs. 
+By default, the DICOM® service supports querying on the DICOM tags specified in the [conformance statement](dicom-services-conformance-statement-v2.md#searchable-attributes). When extended query tags are enabled, the list of tags can easily be expanded based on the application's needs. 
 
-Using the APIs listed below, users can index their DICOM studies, series, and instances on both standard and private DICOM tags such that they can be specified in QIDO-RS queries.
+Using the following listed APIs, users can index their DICOM studies, series, and instances on both standard and private DICOM tags such that they can be specified in QIDO-RS queries.
 
 ## APIs
 
@@ -33,7 +33,7 @@ To help manage the supported tags in a given DICOM service instance, the followi
 
 ### Add extended query tags 
 
-Adds one or more extended query tags and starts a long-running operation that reindexes current DICOM instances with the specified tag(s).
+Adds one or more extended query tags and starts a long-running operation that reindexes current DICOM instances with the specified tags.
 
 ```http
 POST .../extendedquerytags
@@ -85,7 +85,7 @@ The following VR types are supported:
 
 | Name              | Type                                        | Description                                                  |
 | ----------------- | ------------------------------------------- | ------------------------------------------------------------ |
-| 202 (Accepted)    | [Operation Reference](#operation-reference) | Extended query tag(s) have been added, and a long-running operation has been started to reindex existing DICOM instances |
+| 202 (Accepted)    | [Operation Reference](#operation-reference) | Extended query tags have been added, and a long-running operation has been started to reindex existing DICOM instances |
 | 400 (Bad Request) |                                             | Request body has invalid data                                |
 | 409 (Conflict)    |                                             | One or more requested query tags already are supported       |
 
@@ -231,7 +231,7 @@ GET .../operations/{operationId}
 
 The [Status](#extended-query-tag-status) of extended query tag indicates the current status. When an extended query tag is first added, its status is set to `Adding`, and a long-running operation is kicked off to reindex existing DICOM instances. After the operation is completed, the tag status is updated to `Ready`. The extended query tag can now be used in [QIDO](dicom-services-conformance-statement-v2.md#search-qido-rs). 
 
-For example, if the tag Manufacturer Model Name (0008,1090) is added, and in `Ready` status, hereafter the following queries can be used to filter stored instances by the Manufacturer Model Name.
+For example, if the tag Manufacturer Model Name (0008,1090) is added, and in `Ready` status, from then on the following queries can be used to filter stored instances by the Manufacturer Model Name.
 
 ```http
 ../instances?ManufacturerModelName=Microsoft
@@ -282,7 +282,7 @@ Code **example 1** is a standard tag (0008,0070) in `Ready` status.
 }
 ```
 
-Code **example 2** is a standard tag (0010,1010) in `Adding` status.  An operation with ID `1a5d0306d9624f699929ee1a59ed57a0` is running on it, and 21 errors has occurred so far.
+Code **example 2** is a standard tag (0010,1010) in `Adding` status.  An operation with ID `1a5d0306d9624f699929ee1a59ed57a0` is running on it, and 21 errors have occurred so far.
 
 ```json
 {