minor edits for clarity

Author: KendalBond007

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

@@ -13,7 +13,7 @@ ms.author: mmitrik
 
 Data partitioning allows you to set up a lightweight data partition scheme to store multiple copies of the same image with the same unique identifier (UID) in a single DICOM instance. 
 
-Although UIDs should be [unique across all contexts](http://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_9.html), it's common practice for healthcare providers to write DICOM files to portable storage media and then give them to a patient. The patient then gives the files to another healthcare provider, who then transfers the files into a new DICOM storage system. Therefore, multiple copies of one DICOM file do commonly exist in isolated DICOM systems. Data partitioning provides an on-ramp for your existing data stores and workflows. 
+Although UIDs should be [unique across all contexts](http://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_9.html), it's common practice for healthcare providers to write DICOM files to portable storage media and give them to a patient. The patient then gives the files to another healthcare provider, who transfers the files into a new DICOM storage system. As a result, multiple copies of one DICOM file commonly exist in several isolated DICOM systems. Data partitioning provides an on-ramp for your existing data stores and workflows.
 
 ## Limitations
 
@@ -60,7 +60,7 @@ GET /partitions
 After partitions are enabled, STOW, WADO, QIDO, delete, export, update, and worklist requests must include a data partition URI segment after the base URI, with the form `/partitions/{partitionName}`, where `partitionName` is:
 
  - Up to 64 characters long.
- - Any combination of alphanumeric characters, `.`, `-`, and `_`, to allow both DICOM UID and GUID formats, as well as human-readable identifiers.
+ - Any combination of alphanumeric characters, `.`, `-`, and `_` (to allow both DICOM UID and GUID formats), as well as human-readable identifiers.
 
 | Action  | Example URI                                                         |
 | ------- | ------------------------------------------------------------------- |

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure-data-lake.md

@@ -18,9 +18,9 @@ After deployment completes, you can use the Azure portal to see the details abou
 
 ## Prerequisites
 
-- **Deploy an Azure Health Data Services workspace**.  For more information, see [Deploy a workspace in the Azure portal](../healthcare-apis-quickstart.md).
-- **Create a storage account with a hierarchical namespace**.  For more information, see [Create a storage account to use with Azure Data Lake Storage Gen2](/azure/storage/blobs/create-data-lake-storage-account).
-- **Create a blob container in the storage account**.  The container is used by the DICOM service to store DICOM files.  For more information, see [Manage blob containers using the Azure portal](/azure/storage/blobs/blob-containers-portal).
+- **Deploy an Azure Health Data Services workspace**. For more information, see [Deploy a workspace in the Azure portal](../healthcare-apis-quickstart.md).
+- **Create a storage account with a hierarchical namespace**. For more information, see [Create a storage account to use with Azure Data Lake Storage Gen2](/azure/storage/blobs/create-data-lake-storage-account).
+- **Create a blob container in the storage account**. The container is used by the DICOM service to store DICOM files. For more information, see [Manage blob containers using the Azure portal](/azure/storage/blobs/blob-containers-portal).
 
 > [!NOTE]
 > The Azure Data Lake Storage option is only available for new instances of the DICOM service. After the option becomes generally available, we plan to offer a migration path for existing DICOM service instances.
@@ -65,7 +65,7 @@ After deployment completes, you can use the Azure portal to see the details abou
 
 ## Deploy the DICOM service with Data Lake Storage by using an ARM template
 
-Use the Azure portal to **Deploy a custom template** and then use the sample ARM template to deploy the DICOM service with Azure Data Lake Storage. For more information, see [Create and deploy ARM templates by using the Azure portal](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
+Use the Azure portal to **Deploy a custom template**. Then use the sample ARM template to deploy the DICOM service with Azure Data Lake Storage. For more information, see [Create and deploy ARM templates by using the Azure portal](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
 
 ```json
 {
@@ -212,13 +212,13 @@ Use the Azure portal to **Deploy a custom template** and then use the sample ARM
 
 ### Connectivity
 
-To be alerted to store health and connectivity failures, please sign up for [Resource Health alerts](/azure/service-health/resource-health-alert-monitor-guide).
+To receive alerts regarding store health and connectivity failures please sign up for [Resource Health alerts](/azure/service-health/resource-health-alert-monitor-guide).
 
 ### 424 Failed Dependency
 
 When the response status code is `424 Failed Dependency`, the issue lies with a dependency configured with DICOM and it may be the data lake store.
 The response body indicates which dependency failed and provides more context on the failure. For data lake storage account failures, an error code is provided which was received when attempting to interact with the store. For more information, see [Azure Blob Storage error codes](/rest/api/storageservices/blob-service-error-codes).
-Note that a code of `ConditionNotMet` typically indicates the blob file has been moved, deleted or modified without using DICOM APIs. The best way to mitigate such a situation is to use the DICOM API to DELETE the instance to remove the index and then reupload the modified file. This will enable you to continue to reference and interact with the file through DICOM APIs.
+Note that a `ConditionNotMet` code typically indicates the blob file has been moved, deleted or modified without using DICOM APIs. The best way to mitigate this situation is to use the DICOM API to DELETE the instance, to remove the index and then reupload the modified file. This enables you to continue to reference and interact with the file through DICOM APIs.
 
 ## Next steps
 [Receive resource health alerts](/azure/service-health/resource-health-alert-monitor-guide)

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure.md

@@ -13,10 +13,10 @@ ms.custom: mode-api
 
 In this quickstart, you learn how to deploy the DICOM® service by using the Azure portal.
 
-After deployment completes, you can use the Azure portal to see the details about the DICOM service, including the service URL. The service URL to access your DICOM service is ```https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com```. Make sure to specify the API version as part of the URL when you make requests. For more information, see [API versioning for the DICOM service](api-versioning-dicom-service.md).
+After deployment completes, you can use the Azure portal to see the details about the DICOM service, including the service URL. The service URL used to access your DICOM service is ```https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com```. Make sure to specify the API version as part of the URL when you make requests. For more information, see [API versioning for the DICOM service](api-versioning-dicom-service.md).
 
 > [!NOTE]
-> The DICOM service with Azure Data Lake Storage is generally available. This capability provides greater flexibility and control over your imaging data. Learn more: [Deploy the DICOM service with Azure Data Lake Storage](deploy-dicom-services-in-azure-data-lake.md)
+> The DICOM service with Azure Data Lake Storage is generally available. This capability provides greater flexibility and control over your imaging data. For more information, see [Deploy the DICOM service with Azure Data Lake Storage](deploy-dicom-services-in-azure-data-lake.md)
 
 ## Prerequisites