edit pass: four-dicom-articles

Author: paulth1

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

@@ -16,12 +16,12 @@ The DICOM service provides the ability to easily export DICOM data in a file for
 There are three steps to exporting data from the DICOM service:
 
 - Enable a system-assigned managed identity for the DICOM service.
-- Configure a new or existing storage account and give permission to the system-managed identity.
+- Configure a new or existing storage account and give permission to the system-assigned managed identity.
 - Use the export API to create a new export job to export the data.
 
 ## Enable managed identity for the DICOM service
 
-The first step to export data from the DICOM service is to enable a system-managed identity. This managed identity is used to authenticate the DICOM service and give permission to the storage account used as the destination for export. For more information about managed identities in Azure, see [About managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md).
+The first step to export data from the DICOM service is to enable a system-assigned managed identity. This managed identity is used to authenticate the DICOM service and give permission to the storage account used as the destination for export. For more information about managed identities in Azure, see [About managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md).
 
 1. In the Azure portal, browse to the DICOM service that you want to export from and select **Identity**.
 
@@ -35,25 +35,25 @@ The first step to export data from the DICOM service is to enable a system-manag
 
    :::image type="content" source="media/dicom-export-confirm-enable.png" alt-text="Screenshot that shows the dialog confirming enabling system identity." lightbox="media/dicom-export-confirm-enable.png":::
 
-It takes a few minutes to create the system-managed identity. After the system identity is enabled, an **Object (principal) ID** appears.
+It takes a few minutes to create the system-assigned managed identity. After the system identity is enabled, an **Object (principal) ID** appears.
 
-## Give storage account permissions to the system-managed identity
+## Give storage account permissions to the system-assigned managed identity
 
-The system-managed identity needs **Storage Blob Data Contributor** permission to write data to the destination storage account.
+The system-assigned managed identity needs **Storage Blob Data Contributor** permission to write data to the destination storage account.
 
 1. Under **Permissions**, select **Azure role assignments**.
 
    :::image type="content" source="media/dicom-export-azure-role-assignments.png" alt-text="Screenshot that shows the Azure role assignments button on the Identity view." lightbox="media/dicom-export-azure-role-assignments.png":::
 
-1. Select **Add role assignment**. On the **Add role assignment** panel, make the following selections:
+1. Select **Add role assignment**. On the **Add role assignment** pane, make the following selections:
 
     * Under **Scope**, select **Storage**.
     * Under **Resource**, select the destination storage account for the export operation.
     * Under **Role**, select **Storage Blob Data Contributor**.
 
    :::image type="content" source="media/dicom-export-add-role-assignment.png" alt-text="Screenshot that shows the Add role assignment pane." lightbox="media/dicom-export-add-role-assignment.png":::
 
-1. Select **Save** to add the permission to the system-managed identity.
+1. Select **Save** to add the permission to the system-assigned managed identity.
 
 ## Use the export API
 

articles/healthcare-apis/dicom/get-started-with-dicom.md

@@ -73,6 +73,6 @@ DICOMcast is currently available as an [open-source](https://github.com/microsof
 
 ## Next steps
 
-[Deploy DICOM service using the Azure portal](deploy-dicom-services-in-azure.md)
+[Deploy the DICOM service by using the Azure portal](deploy-dicom-services-in-azure.md)
 
 [!INCLUDE [FHIR and DICOM trademark statements](../includes/healthcare-apis-fhir-dicom-trademark.md)]

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

@@ -20,7 +20,7 @@ Bulk import is a quick way to add data to the DICOM® service. Importing DICO
 ## Prerequisites
 
 - **Deploy an instance of the DICOM service.** For more information, see [Deploy the DICOM service](deploy-dicom-services-in-azure.md).
-- **Deploy the events capability for the DICOM service.** For more information, see [Deploy events using the Azure portal](../events/events-deploy-portal.md).
+- **Deploy the events capability for the DICOM service.** For more information, see [Deploy events by using the Azure portal](../events/events-deploy-portal.md).
 
 ## Enable a system-assigned managed identity
 
@@ -69,7 +69,7 @@ Here's an example of how to configure bulk import in an ARM template:
 
 ## Import data
 
-After you enable bulk import, a resource group is provisioned in your Azure subscription. The name of the resource group begins with the prefix `AHDS_`, followed by the workspace and DICOM service name. For example, for the DICOM service named `mydicom` in the workspace `contoso`, the resource group would be named `AHDS_contoso-mydicom`.
+After you enable bulk import, a resource group is provisioned in your Azure subscription. The name of the resource group begins with the prefix `AHDS_`, followed by the workspace and DICOM service name. For example, for the DICOM service named `mydicom` in the workspace `contoso`, the resource group is named `AHDS_contoso-mydicom`.
 
 Within the new resource group, two resources are created: