removed tm symbol

Author: shellyhaverkamp

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

@@ -15,7 +15,7 @@ ms.author: mmitrik
 > [!NOTE]
 > API version 2 is the latest API version.  For a list of changes in v2 compared to v1, see [DICOM service API v2 changes](dicom-service-v2-api-changes.md)
 
-The Medical Imaging Server for DICOM® supports a subset of the DICOMweb™ Standard. Support includes:
+The Medical Imaging Server for DICOM® supports a subset of the DICOMweb Standard. Support includes:
 
 * [Studies Service](#studies-service)
     * [Store (STOW-RS)](#store-stow-rs)
@@ -602,7 +602,7 @@ The query API returns one of the following status codes in the response:
 
 ### Delete
 
-This transaction isn't part of the official DICOMweb™ Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
+This transaction isn't part of the official DICOMweb Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
 
 | Method | Path                                                    | Description |
 | :----- | :------------------------------------------------------ | :---------- |
@@ -671,7 +671,7 @@ required to be present, required to not be present, required to be empty, or req
 found [in this table](https://dicom.nema.org/medical/dicom/current/output/html/part04.html#table_CC.2.5-3).
 
 > [!NOTE]
-> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb™. SOP Instance UID should be present in the dataset if not in the URI.
+> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb. SOP Instance UID should be present in the dataset if not in the URI.
 
 > [!NOTE]
 > All the conditional requirement codes including 1C and 2C are treated as optional.

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

@@ -15,7 +15,7 @@ ms.author: mmitrik
 > [!NOTE]
 > API version 2 is the latest API version and should be used in place of v1. See the [DICOM Conformance Statement v2](dicom-services-conformance-statement-v2.md) for details.
 
-The Medical Imaging Server for DICOM® supports a subset of the DICOMweb™ Standard. Support includes:
+The Medical Imaging Server for DICOM® supports a subset of the DICOMweb Standard. Support includes:
 
 * [Studies Service](#studies-service)
     * [Store (STOW-RS)](#store-stow-rs)
@@ -514,7 +514,7 @@ The query API returns one of the following status codes in the response:
 
 ### Delete
 
-This transaction isn't part of the official DICOMweb™ Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
+This transaction isn't part of the official DICOMwe Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
 
 | Method | Path                                                    | Description |
 | :----- | :------------------------------------------------------ | :---------- |
@@ -583,7 +583,7 @@ required to be present, required to not be present, required to be empty, or req
 found [in this table](https://dicom.nema.org/medical/dicom/current/output/html/part04.html#table_CC.2.5-3).
 
 > [!NOTE]
-> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb™. SOP Instance UID should be present in the dataset if not in the URI.
+> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb. SOP Instance UID should be present in the dataset if not in the URI.
 
 > [!NOTE]
 > All the conditional requirement codes including 1C and 2C are treated as optional.

articles/healthcare-apis/dicom/dicom-services-faqs.yml

@@ -16,7 +16,7 @@ sections:
   - name: Ignored
     questions:
       - question: What is the DICOM service?
-        answer: The DICOM® service is a managed service within [Azure Health Data Services](../healthcare-apis-overview.md) that ingests and persists DICOM objects at multiple thousands of images per second. It facilitates communication and transmission of imaging data with any DICOMweb™ enabled systems or applications via DICOMweb Standard APIs like [Store (STOW-RS)](dicom-services-conformance-statement-v2.md#store-stow-rs), [Search (QIDO-RS)](dicom-services-conformance-statement-v2.md#search-qido-rs), [Retrieve (WADO-RS)](dicom-services-conformance-statement-v2.md#retrieve-wado-rs). It's backed by a managed Platform-as-a Service (PaaS) offering in the cloud with complete [PHI](https://www.hhs.gov/answers/hipaa/what-is-phi/index.html) compliance that you can upload PHI data to the DICOM service and exchange it through secure networks.
+        answer: The DICOM® service is a managed service within [Azure Health Data Services](../healthcare-apis-overview.md) that ingests and persists DICOM objects at multiple thousands of images per second. It facilitates communication and transmission of imaging data with any DICOMweb enabled systems or applications via DICOMweb Standard APIs like [Store (STOW-RS)](dicom-services-conformance-statement-v2.md#store-stow-rs), [Search (QIDO-RS)](dicom-services-conformance-statement-v2.md#search-qido-rs), [Retrieve (WADO-RS)](dicom-services-conformance-statement-v2.md#retrieve-wado-rs). It's backed by a managed Platform-as-a Service (PaaS) offering in the cloud with complete [PHI](https://www.hhs.gov/answers/hipaa/what-is-phi/index.html) compliance that you can upload PHI data to the DICOM service and exchange it through secure networks.
 
       - question: What are the key requirements to use the DICOM service?
         answer: The DICOM service needs an Azure subscription to configure and run the required components. These components are, by default, created inside of an existing or new Azure Resource Group to simplify management. Additionally, a Microsoft Entra account is required.
@@ -31,9 +31,9 @@ sections:
           
       - question: What data formats are compatible with the DICOM service?
         answer: |
-          The DICOM service exposes a REST API that is compatible with the [DICOMweb™ Standards](https://www.dicomstandard.org/using/dicomweb) specified and maintained by NEMA.
+          The DICOM service exposes a REST API that is compatible with the [DICOMweb Standards](https://www.dicomstandard.org/using/dicomweb) specified and maintained by NEMA.
           
-          The server doesn't support DICOM DIMSE, which works primarily over a local area network and is unsuited for modern internet-based APIs. DIMSE is an incredibly popular standard used by nearly all medical imaging devices to communicate with other components of a provider’s medical imaging solution, such as PACS (Picture Archiving and Communication Systems) and medical imaging viewers. However, many modern systems, especially PACS and viewers, have begun to also support the related (and compatible) DICOMweb™ Standard. For those systems which only speak DICOM DIMSE, there are adapters available which allow for seamless communication between the local DIMSE-supporting systems and the DICOM service.
+          The server doesn't support DICOM DIMSE, which works primarily over a local area network and is unsuited for modern internet-based APIs. DIMSE is an incredibly popular standard used by nearly all medical imaging devices to communicate with other components of a provider’s medical imaging solution, such as PACS (Picture Archiving and Communication Systems) and medical imaging viewers. However, many modern systems, especially PACS and viewers, have begun to also support the related (and compatible) DICOMweb Standard. For those systems which only speak DICOM DIMSE, there are adapters available which allow for seamless communication between the local DIMSE-supporting systems and the DICOM service.
           
       - question: What version of DICOM does the DICOM service support?
         answer: |
@@ -57,7 +57,7 @@ sections:
           
       - question: What is the difference between Retrieve, Query, and Store?
         answer: |
-          Query, Retrieve, and store are standard DICOMweb™ verbs. Query (QIDO) searches for DICOM objects. QIDO enables you to search for studies, series and instances by patient ID. Retrieve (WADO) enables you to retrieve specific studies, series, and instances by reference. Store (STOW-RS) enables you to store specific instances to a DICOM server. For more information about the specifics of QIDO, WADO, and STOW, see [DICOMweb™](https://www.dicomstandard.org/using/dicomweb).
+          Query, Retrieve, and store are standard DICOMweb verbs. Query (QIDO) searches for DICOM objects. QIDO enables you to search for studies, series and instances by patient ID. Retrieve (WADO) enables you to retrieve specific studies, series, and instances by reference. Store (STOW-RS) enables you to store specific instances to a DICOM server. For more information about the specifics of QIDO, WADO, and STOW, see [DICOMweb](https://www.dicomstandard.org/using/dicomweb).
       
       - question: What is REST API versioning in the DICOM service?
         answer: |

articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md

@@ -11,7 +11,7 @@ ms.author: mmitrik
 
 # Use C# and DICOMweb Standard APIs
 
-This article shows how to work with the DICOM® service using C# and [sample .dcm DICOM files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
+This article shows how to work with the DICOMweb service using C# and [sample .dcm DICOM® files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
 
 Use these sample files:
 
@@ -33,7 +33,7 @@ The filename, studyUID, seriesUID, and instanceUID of the sample DICOM files are
 
 ## Prerequisites
 
-To use the DICOMweb™ Standard APIs, you need an instance of the DICOM service deployed. If you haven't already deployed an instance of the DICOM service, see [Deploy DICOM service using the Azure portal](deploy-dicom-services-in-azure.md).
+To use the DICOMweb Standard APIs, you need an instance of the DICOM service deployed. If you haven't already deployed an instance of the DICOM service, see [Deploy DICOM service using the Azure portal](deploy-dicom-services-in-azure.md).
 
 After you've deployed an instance of the DICOM service, retrieve the URL for your app service:
 

articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md

@@ -11,7 +11,7 @@ ms.author: mmitrik
 
 # Use DICOMweb Standard APIs with cURL
 
-This article shows how to work with the DICOM® service using cURL and [sample .dcm DICOM files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
+This article shows how to work with the DICOMweb service using cURL and [sample .dcm DICOM® files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
 
 Use these sample files:
 
@@ -45,9 +45,9 @@ Once you've deployed an instance of the DICOM service, retrieve the URL for your
 For this code, we'll be accessing an Public Preview Azure service. It's important that you don't upload any private health information (PHI).
 
 
-## Working with the DICOM service
+## Work with the DICOM service
 
-The DICOMweb™ Standard makes heavy use of `multipart/related` HTTP requests combined with DICOM specific accept headers. Developers familiar with other REST-based APIs often find working with the DICOMweb™ Standard awkward. However, once you've it up and running, it's easy to use. It just takes a little familiarity to get started.
+The DICOMweb Standard makes heavy use of `multipart/related` HTTP requests combined with DICOM specific accept headers. Developers familiar with other REST-based APIs often find working with the DICOMweb Standard awkward. However, once you've it up and running, it's easy to use. It just takes a little familiarity to get started.
 
 The cURL commands each contain at least one, and sometimes two, variables that must be replaced. To simplify running the commands, search and replace the following variables by replacing them with your specific values:
 

articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md

@@ -12,7 +12,7 @@ ms.author: mmitrik
 
 # Using DICOM Standard APIs with Python
 
-This article shows how to work with the DICOM® service using cURL and [sample .dcm DICOM files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
+This article shows how to work with the DICOM® service using Python and [sample .dcm DICOM files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
 
 Use these sample files:
 
@@ -45,7 +45,7 @@ After you've deployed an instance of the DICOM service, retrieve the URL for you
 
 For this code, you access a Public Preview Azure service. It's important that you don't upload any private health information (PHI).
 
-## Working with the DICOM service
+## Work with the DICOM service
 
 The DICOMweb Standard makes heavy use of `multipart/related` HTTP requests combined with DICOM specific accept headers. Developers familiar with other REST-based APIs often find working with the DICOMweb standard awkward. However, after it's up and running, it's easy to use. It just takes a little familiarity to get started.
 
@@ -65,7 +65,7 @@ from urllib3.filepost import encode_multipart_formdata, choose_boundary
 from azure.identity import DefaultAzureCredential
 ```
 
-### Configure user-defined variables to be used throughout
+### Configure user-defined variables
 
 Replace all variable values wrapped in { } with your own values. Additionally, validate that any constructed variables are correct.  For instance, `base_url` is constructed using the Service URL and then appended with the version of the REST API being used. The Service URL of your DICOM service is: ```https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com```. You can use the Azure portal to navigate to the DICOM service and obtain your Service URL. You can also visit the [API Versioning for DICOM service Documentation](api-versioning-dicom-service.md) for more information on versioning. If you're using a custom URL, you need to override that value with your own.
 
@@ -101,7 +101,7 @@ bearer_token = f'Bearer {token.token}'
 
 ### Create supporting methods to support `multipart\related`
 
-The `Requests` libraries (and most Python libraries) don't work with `multipart\related` in a way that supports DICOMweb&trade;. Because of these libraries, we must add a few methods to support working with DICOM files.
+The `Requests` libraries (and most Python libraries) don't work with `multipart\related` in a way that supports DICOMweb. Because of these libraries, we must add a few methods to support working with DICOM files.
 
 `encode_multipart_related` takes a set of fields (in the DICOM case, these libraries are generally Part 10 dam files) and an optional user-defined boundary. It returns both the full body, along with the content_type, which it can be used.