markdown and edit updates, author update

KendalBond007 · KendalBond007 · commit ba02a59e1ca9 · 2024-08-29T13:21:13.000-07:00
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md
@@ -1,12 +1,12 @@
 ---
 title:  Use cURL and DICOMweb Standard APIs in Azure Health Data Services
 description: Use cURL and DICOMweb Standard APIs to store, retrieve, search, and delete DICOM files in the DICOM service.  
-author: mmitrik
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.topic: tutorial
 ms.date: 10/18/2023
-ms.author: mmitrik
+ms.author: varunbms
 ---
 
 # Use DICOMweb Standard APIs with cURL
@@ -49,11 +49,11 @@ For this code, we access a Public Preview Azure service. It's important that you
  
 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 you get 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:
+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 your specific values.
 
 * {Service URL} The service URL is the URL to access your DICOM service that you provisioned in the Azure portal, for example, ```https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com```. Make sure to specify the version as part of the url when making requests. More information can be found in the [API Versioning for DICOM service Documentation](api-versioning-dicom-service.md).
 * {path-to-dicoms} - The path to the directory that contains the red-triangle.dcm file, such as `C:/dicom-server/docs/dcms`
-    * Ensure to use forward slashes as separators and end the directory _without_ a trailing forward slash.
+    * Ensure using forward slashes as separators and end the directory _without_ a trailing forward slash.
 
 
 ## Upload DICOM instances (STOW)
@@ -76,7 +76,7 @@ _Details:_
 * Body:
     * Content-Type: application/dicom for each file uploaded, separated by a boundary value
 
-Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those tools, you might need to use a slightly modified Content-Type header. These tools can be used successfully.
+Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those tools, you might need to use a slightly modified Content-Type header. The following tools can be used successfully.
 * Content-Type: multipart/related; type="application/dicom"; boundary=ABCD1234
 * Content-Type: multipart/related; boundary=ABCD1234
 * Content-Type: multipart/related
@@ -104,7 +104,7 @@ _Details:_
 * Body:
     * Content-Type: application/dicom for each file uploaded, separated by a boundary value
 
-Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those languages and tools, you might need to use a slightly modified Content-Type header. These tools can be used successfully.
+Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those languages and tools, you might need to use a slightly modified Content-Type header. The following tools can be used successfully.
 
  * Content-Type: multipart/related; type="application/dicom"; boundary=ABCD1234
  * Content-Type: multipart/related; boundary=ABCD1234
@@ -159,7 +159,7 @@ _Details:_
 * Body:
     * Content-Type: application/dicom for each file uploaded, separated by a boundary value
 
-Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those tools, you might need to use a slightly modified Content-Type header. These tools can be used successfully:
+Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those tools, you might need to use a slightly modified Content-Type header. The following tools can be used successfully.
 * Content-Type: multipart/related; type="application/dicom"; boundary=ABCD1234
 * Content-Type: multipart/related; boundary=ABCD1234
 * Content-Type: multipart/related
@@ -188,7 +188,7 @@ _Details:_
 * Body:
     * Content-Type: application/dicom for each file uploaded, separated by a boundary value
 
-Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those languages and tools, you might need to use a slightly modified Content-Type header. These tools can be used successfully:
+Some programming languages and tools behave differently. For instance, some require you to define your own boundary. For those languages and tools, you might need to use a slightly modified Content-Type header. The following tools can be used successfully.
 
  * Content-Type: multipart/related; type="application/dicom"; boundary=ABCD1234
  * Content-Type: multipart/related; boundary=ABCD1234
@@ -205,9 +205,9 @@ curl --request PUT "{Service URL}/v{version}/studies/1.2.826.0.1.3680043.8.498.1
 ### Upsert single instance
 
 > [!NOTE]
-> This is a non-standard API that allows the upsert of a single DICOM files. 
+> This is a non-standard API that allows the upsert of a single DICOM file. 
 
-Use this method to upload a single DICOM file:
+Use this method to upload a single DICOM file.
 
 _Details:_
 * Path: ../studies
@@ -342,7 +342,7 @@ curl --request GET "{Service URL}/v{version}/studies/1.2.826.0.1.3680043.8.498.1
 
 ### Retrieve one or more frames from a single instance
 
-This request retrieves one or more frames from a single instance, and returns them as a collection of multipart/related bytes. Multiple frames can be retrieved by passing a comma-separated list of frame numbers.  All DICOM instances with images have at minimum one frame, which is often just the image associated with the instance itself.
+This request retrieves one or more frames from a single instance, and returns them as a collection of multipart/related bytes. Multiple frames can be retrieved by passing a comma-separated list of frame numbers.  All DICOM instances with images have at minimum one frame, which is often simply the image associated with the instance itself.
 
 _Details:_
 * Path: ../studies/{study}/series{series}/instances/{instance}/frames/1,2,3
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md
@@ -1,13 +1,13 @@
 ---
 title:  Use Python and DICOMweb Standard APIs in Azure Health Data Services
 description: Use Python and DICOMweb Standard APIs to store, retrieve, search, and delete DICOM files in the DICOM service.  
-author: mmitrik
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.custom: devx-track-python
 ms.topic: tutorial
 ms.date: 02/15/2022
-ms.author: mmitrik
+ms.author: varunbms
 ---
 
 # Use DICOMweb Standard APIs with Python
@@ -30,7 +30,7 @@ The filename, studyUID, seriesUID, and instanceUID of the sample DICOM files are
 |blue-circle.dcm|1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420|1.2.826.0.1.3680043.8.498.77033797676425927098669402985243398207|1.2.826.0.1.3680043.8.498.13273713909719068980354078852867170114|
 
 > [!NOTE]
-> Each of these files represents a single instance and is part of the same study. Also,the green-square and red-triangle are part of the same series, while the blue-circle is in a separate series.
+> Each of these files represents a single instance and is part of the same study. Also, the green-square and red-triangle are part of the same series, while the blue-circle is in a separate series.
 
 ## Prerequisites
 
@@ -82,10 +82,10 @@ instance_uid = "1.2.826.0.1.3680043.8.498.47359123102728459884412887463296905395
 
 ### Authenticate to Azure and get a token
 
-`DefaultAzureCredential` allows us to use various ways to get tokens to log into the service. In this example, use the `AzureCliCredential` to get a token to log into the service. There are other credential providers such as `ManagedIdentityCredential` and `EnvironmentCredential` that are also possible to use. To use the AzureCliCredential, you need to sign in to Azure from the CLI before running this code. For more information, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md). Alternatively, copy and paste the token retrieved while signing in from the CLI.
+`DefaultAzureCredential` allows us to use various ways to get tokens to log into the service. In this example, use the `AzureCliCredential` to get a token to log into the service. There are other credential providers such as `ManagedIdentityCredential` and `EnvironmentCredential` that you may use. To use the AzureCliCredential, you need to sign in to Azure from the CLI before running this code. For more information, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md). Alternatively, copy and paste the token retrieved while signing in from the CLI.
 
 > [!NOTE]
-> `DefaultAzureCredential` returns several different Credential objects. We reference the `AzureCliCredential` as the 5th item in the returned collection. This may not be consistent. If so, uncomment the `print(credential.credential)` line. This will list all the items. Find the correct index, recalling that Python uses zero-based indexing.
+> `DefaultAzureCredential` returns several different Credential objects. We reference the `AzureCliCredential` as the 5th item in the returned collection. This may not always be the case. If not, uncomment the `print(credential.credential)` line. This will list all the items. Find the correct index, recalling that Python uses zero-based indexing.
 
 > [!NOTE]
 > If you have not logged into Azure using the CLI, this will fail. You must be logged into Azure from the CLI for this to work. 
@@ -103,7 +103,7 @@ bearer_token = f'Bearer {token.token}'
 
 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.
+`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 can be used.
 
 ```python
 def encode_multipart_related(fields, boundary=None):
@@ -144,7 +144,7 @@ The following examples highlight persisting DICOM files.
 
 ### Store instances using `multipart/related`
 
-This example demonstrates how to upload a single DICOM file, and it uses a bit of a Python to preload the DICOM file (as bytes) into memory. When an array of files is passed to the fields parameter of `encode_multipart_related`, multiple files can be uploaded in a single POST. It's sometimes used to upload several instances inside a complete series or study.
+This example demonstrates how to upload a single DICOM file, and it uses Python to preload the DICOM file into memory as bytes. When an array of files is passed to the fields parameter `encode_multipart_related`, multiple files can be uploaded in a single POST. It's sometimes used to upload several instances inside a complete series or study.
 
 _Details:_
 
@@ -183,9 +183,9 @@ response = client.post(url, body, headers=headers, verify=False)
 
 ### Store instances for a specific study
 
-This example demonstrates how to upload multiple DICOM files into the specified study. It uses a bit of a Python to preload the DICOM file (as bytes) into memory.  
+This example demonstrates how to upload multiple DICOM files into the specified study. It uses Python to preload the DICOM file into memory as bytes.  
 
-When an array of files is passed to the fields parameter of `encode_multipart_related`, multiple files can be uploaded in a single POST. It's sometimes used to upload a complete series or study. 
+When an array of files is passed to the fields parameter `encode_multipart_related`, multiple files can be uploaded in a single POST. It's sometimes used to upload a complete series or study. 
 
 _Details:_
 * Path: ../studies/{study}
@@ -264,7 +264,7 @@ _Details:_
    * Accept: multipart/related; type="application/dicom"; transfer-syntax=*
    * Authorization: Bearer $token"
 
-All three of the dcm files that we uploaded previously are part of the same study so the response should return all three instances. Validate that the response has a status code of OK and that all three instances are returned.
+All three of the dcm files that we uploaded previously are part of the same study, so the response should return all three instances. Validate that the response has a status code of OK and that all three instances are returned.
 
 ```python
 url = f'{base_url}/studies/{study_uid}'
@@ -275,7 +275,7 @@ response = client.get(url, headers=headers) #, verify=False)
 
 ### Use the retrieved instances
 
-The instances are retrieved as binary bytes. You can loop through the returned items and convert the bytes into a file that `pydicom` can read.
+The instances are retrieved as binary bytes. You can loop through the returned items and convert the bytes into a file that `pydicom` can read as follows.
 
 
 ```python
@@ -345,7 +345,7 @@ _Details:_
    * Accept: application/dicom+json
    * Authorization: Bearer $token"
 
-This series has two instances (green-square and red-triangle), so the response should return for both instances. Validate that the response has a status code of OK and that both instances metadata are returned.
+This series has two instances (green-square and red-triangle), so the response should return for both instances. Validate that the response has a status code of OK and that the metadata of both instances are returned.
 
 ```python
 url = f'{base_url}/studies/{study_uid}/series/{series_uid}/metadata'
@@ -420,7 +420,7 @@ response = client.get(url, headers=headers) #, verify=False)
 
 In the following examples, we search for items using their unique identifiers. You can also search for other attributes, such as PatientName.
 
-Refer to the [DICOM Conformance Statement](dicom-services-conformance-statement-v2.md#supported-search-parameters) document for supported DICOM attributes.
+Refer to the [DICOM Conformance Statement](dicom-services-conformance-statement-v2.md#supported-search-parameters) for supported DICOM attributes.
 
 ### Search for studies
 
@@ -553,7 +553,7 @@ response = client.get(url, headers=headers, params=params) #, verify=False)
 > [!NOTE]
 > Delete is not part of the DICOM standard, but it has been added for convenience.
 
-A 204 response code is returned when the deletion is successful. A 404 response code is returned if the item(s) never existed or are already deleted.
+A 204 response code is returned when the deletion is successful. A 404 response code is returned if the items never existed or are already deleted.
 
 ### Delete a specific instance within a study and series
 
@@ -565,7 +565,7 @@ _Details:_
 * Headers:
    * Authorization: Bearer $token
 
-This request deletes the red-triangle instance from the server. If it's successful, the response status code contains no content.
+This request deletes the red-triangle instance from the server. If successful, the response status code contains no content.
 
 ```python
 headers = {"Authorization":bearer_token}
@@ -583,7 +583,7 @@ _Details:_
 * Headers:
    * Authorization: Bearer $token
 
-This code example deletes the green-square instance (it's the only element left in the series) from the server. If it's successful, the response status code doesn't delete content.
+This code example deletes the green-square instance from the server (it's the only element left in the series). If successful, the response status code doesn't delete content.
 
 ```python
 headers = {"Authorization":bearer_token}
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services.md
@@ -1,12 +1,12 @@
 ---
 title:  Access DICOMweb APIs to manage DICOM data in Azure Health Data Services
 description: Learn how to use DICOMweb APIs to store, review, search, and delete DICOM objects. Learn how to use custom APIs to track changes and assign unique tags to DICOM data.
-author: mmitrik
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.topic: tutorial
 ms.date: 05/29/2024
-ms.author: mmitrik
+ms.author: varunbms
 ---
 
 # Access DICOMweb APIs to manage DICOM data
@@ -39,7 +39,7 @@ In addition to the subset of DICOMweb APIs, the DICOM service supports these cus
 
 The DICOM service provides a web-based interface that follows REST (representational state transfer) principles. The REST API allows different applications or systems to communicate with each other using standard methods like GET, POST, PUT, and DELETE. To interact with the DICOM service, use any programming language that supports HTTP requests and responses.
 
-Refer to the language-specific examples. You can view Postman collection examples in several languages including:
+Refer to the language-specific examples. You can view Postman collection examples in several languages including the following.
 
 - Go 
 - Java 
@@ -73,7 +73,7 @@ For more information about how to use Python with the DICOM service, see [Using
 
 Postman is an excellent tool for designing, building, and testing REST APIs. [Download Postman](https://www.postman.com/downloads/) to get started. For more information, see [Postman learning site](https://learning.postman.com/).
 
-One important caveat with Postman and the DICOMweb standard is that Postman only supports uploading DICOM files by using the single-part payload defined in the DICOM standard. This caveat is because Postman can't support custom separators in a multipart/related POST request. For more information, see [Multipart POST not working for me # 576](https://github.com/postmanlabs/postman-app-support/issues/576). All examples in the Postman collection for uploading DICOM documents by using a multipart request are prefixed with **[won't work - see description]**. The examples for uploading by using a single-part request are included in the collection and are prefixed with **Store-Single-Instance**.
+One important caution with Postman and the DICOMweb standard is that Postman only supports uploading DICOM files by using the single-part payload defined in the DICOM standard. This is because Postman can't support custom separators in a multipart/related POST request. For more information, see [Multipart POST not working for me # 576](https://github.com/postmanlabs/postman-app-support/issues/576). All examples in the Postman collection for uploading DICOM documents by using a multipart request are prefixed with **[won't work - see description]**. The examples for uploading by using a single-part request are included in the collection and are prefixed with **Store-Single-Instance**.
 
 To use the Postman collection, download it locally and then import the collection through Postman. To access the collection, see [Postman Collection Examples](https://github.com/microsoft/dicom-server/blob/main/docs/resources/Conformance-as-Postman.postman_collection.json).
 
