edit pass: four-dicom-articles

Author: paulth1

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

@@ -11,7 +11,7 @@ ms.author: mmitrik
 
 # Export DICOM files
 
-The DICOM service provides the ability to easily export DICOM data in a file format. The service simplifies the process of using medical imaging in external workflows, such as AI and machine learning. You can use the export API to export DICOM studies, series, and instances in bulk to an [Azure Blob Storage account](../../storage/blobs/storage-blobs-introduction.md). DICOM data that's exported to a storage account is exported as a `.dcm` file in a folder structure that organizes instances by `StudyInstanceID` and `SeriesInstanceID`.
+The DICOM® service provides the ability to easily export DICOM data in a file format. The service simplifies the process of using medical imaging in external workflows, such as AI and machine learning. You can use the export API to export DICOM studies, series, and instances in bulk to an [Azure Blob Storage account](../../storage/blobs/storage-blobs-introduction.md). DICOM data that's exported to a storage account is exported as a `.dcm` file in a folder structure that organizes instances by `StudyInstanceID` and `SeriesInstanceID`.
 
 There are three steps to exporting data from the DICOM service:
 
@@ -100,7 +100,7 @@ The only setting is the list of identifiers to export.
 
 ### Destination settings
 
-The connection to the Azure Blob Storage account is specified with `BlobContainerUri`.
+The connection to the Blob Storage account is specified with `BlobContainerUri`.
 
 | Property             | Required | Default | Description |
 | :------------------- | :------- | :------ | :---------- |
@@ -194,3 +194,5 @@ Each line of the error log is a JSON object with the following properties. A giv
 
 >[!div class="nextstepaction"]
 >[Overview of the DICOM service](dicom-services-overview.md)
+
+[!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]

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

@@ -20,14 +20,14 @@ As a prerequisite, you need an Azure subscription and permissions to create Azur
 
 ## Create a workspace in your Azure subscription
 
-You can create a workspace from the [Azure portal](../healthcare-apis-quickstart.md) or by using PowerShell, the Azure CLI, or a REST API. You can find scripts from the [Azure Health Data Services samples](https://github.com/microsoft/healthcare-apis-samples/tree/main/src/scripts).
+You can create a workspace from the [Azure portal](../healthcare-apis-quickstart.md) or by using PowerShell, the Azure CLI, or a REST API. You can find scripts from the [Health Data Services samples](https://github.com/microsoft/healthcare-apis-samples/tree/main/src/scripts).
 
 > [!NOTE]
 > There are limits to the number of workspaces and the number of DICOM service instances you can create in each Azure subscription.
 
 ## Create a DICOM service in the workspace
 
-You can create a DICOM service instance from the [Azure portal](deploy-dicom-services-in-azure.md) or by using PowerShell, the Azure CLI, or a REST API. You can find scripts from the [Azure Health Data Services samples](https://github.com/microsoft/healthcare-apis-samples/tree/main/src/scripts).
+You can create a DICOM service instance from the [Azure portal](deploy-dicom-services-in-azure.md) or by using PowerShell, the Azure CLI, or a REST API. You can find scripts from the [Health Data Services samples](https://github.com/microsoft/healthcare-apis-samples/tree/main/src/scripts).
 
 Optionally, you can create a [FHIR service](../fhir/fhir-portal-quickstart.md) and [MedTech service](../iot/deploy-iot-connector-in-azure.md) in the workspace.
 
@@ -37,7 +37,7 @@ The DICOM service is secured by a Microsoft Entra ID that can't be disabled. To
 
 ### Register a client application
 
-You can create or register a client application from the [Azure portal](dicom-register-application.md) or by using PowerShell and Azure CLI scripts. You can use this client application for one or more DICOM service instances. You can also use it for other services in Azure Health Data Services.
+You can create or register a client application from the [Azure portal](dicom-register-application.md) or by using PowerShell and Azure CLI scripts. You can use this client application for one or more DICOM service instances. You can also use it for other services in Health Data Services.
 
 If the client application is created with a certificate or client secret, ensure that you renew the certificate or client secret before expiration and replace the client credentials in your applications.
 

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

@@ -84,8 +84,10 @@ The user or account that adds DICOM images to the import container needs write a
 
 #### Upload DICOM images to the import container
 
-Data is uploaded to Azure storage containers in many ways:
+Data is uploaded to Azure Storage containers in many ways:
 
 - [Upload a blob with Azure Storage Explorer](../../storage/blobs/quickstart-storage-explorer.md#upload-blobs-to-the-container)
 - [Upload a blob with AzCopy](../../storage/common/storage-use-azcopy-blobs-upload.md)
 - [Upload a blob with the Azure CLI](../../storage/blobs/storage-quickstart-blobs-cli.md#upload-a-blob)
+
+[!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]