acrolinx recos

shellyhaverkamp · shellyhaverkamp · commit 05ed75e249ff · 2023-10-19T12:40:09.000-07:00
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md
@@ -35,7 +35,7 @@ The filename, studyUID, seriesUID, and instanceUID of the sample DICOM files are
 
 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:
+After you deploy an instance of the DICOM service, retrieve the URL for your app service:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Search **Recent resources** and select your DICOM service instance.
@@ -49,7 +49,7 @@ In your application, install the following NuGet packages:
 
 ## Create a DicomWebClient
 
-After you've deployed your DICOM service, you create a DicomWebClient. Run the code snippet to create DicomWebClient, which you use for the rest of this tutorial. Ensure you have both NuGet packages installed. If you haven't already obtained a token, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md).
+After you deploy your DICOM service, you create a DicomWebClient. Run the code snippet to create DicomWebClient, which you use for the rest of this tutorial. Ensure you have both NuGet packages installed. If you haven't already obtained a token, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md).
 
 ```c#
 string webServerUrl ="{Your DicomWeb Server URL}"
@@ -60,7 +60,7 @@ client.HttpClient.DefaultRequestHeaders.Authorization = new System.Net.Http.Head
 ```
 With the DicomWebClient, we can now perform the Store, Retrieve, Search, and Delete operations.
 
-## Store DICOM Instances (STOW)
+## Store DICOM instances (STOW)
 
 Using the DicomWebClient that we've created, we can now store DICOM files.
 
@@ -92,7 +92,7 @@ DicomWebResponse response = await client.StoreAsync(new[] { dicomFile }, "1.2.82
 
 Before moving on to the next part of the tutorial, upload the `green-square.dcm` file using either of the preceding methods.
 
-## Retrieving DICOM instance(s) (WADO)
+## Retrieve DICOM instance (WADO)
 
 The code snippets show how to perform each of the retrieve queries using the DicomWebClient created previously.
 
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-curl.md
@@ -42,28 +42,28 @@ Once you've deployed an instance of the DICOM service, retrieve the URL for your
 3. Copy the **Service URL** of your DICOM service. 
 4. If you haven't already obtained a token, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md). 
 
-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).
+For this code, we access a Public Preview Azure service. It's important that you don't upload any private health information (PHI).
 
 
 ## 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, 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:
 
-* {Service URL} This 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).
+* {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.
 
 
-## Uploading DICOM Instances (STOW)
+## Upload DICOM instances (STOW)
 
 ### Store-instances-using-multipart/related
 
 This request intends to demonstrate how to upload DICOM files using multipart/related. 
 
 >[!NOTE]
->The DICOM service is more lenient than the DICOM standard. However, the example below demonstrates a POST request that complies tightly to the standard.
+>The DICOM service is more lenient than the DICOM standard. However, the example demonstrates a POST request that complies tightly to the standard.
 
 _Details:_
 
@@ -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, you may need to use a slightly modified Content-Type header. The following have been 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 have been 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, you may need to use a slightly modified Content-Type header. The following have been 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 have been used successfully.
 
  * Content-Type: multipart/related; type="application/dicom"; boundary=ABCD1234
  * Content-Type: multipart/related; boundary=ABCD1234
@@ -143,7 +143,7 @@ curl --location --request POST "{Service URL}/v{version}/studies"
 --data-binary "@{path-to-dicoms}/green-square.dcm"
 ```
 
-## Retrieving DICOM (WADO)
+## Retrieve DICOM (WADO)
 
 ### Retrieve all instances within a study
 
@@ -163,7 +163,7 @@ curl --request GET "{Service URL}/v{version}/studies/1.2.826.0.1.3680043.8.498.1
 --output "suppressWarnings.txt"
 ```
 
-This cURL command will show the downloaded bytes in the output file (suppressWarnings.txt), but these aren't direct DICOM files, only a text representation of the multipart/related download.
+This cURL command shows the downloaded bytes in the output file (suppressWarnings.txt), but they aren't direct DICOM files, only a text representation of the multipart/related download.
 
 ### Retrieve metadata of all instances in study
 
@@ -176,7 +176,7 @@ _Details:_
    * Accept: application/dicom+json
    * Authorization: Bearer {token value}
 
-This cURL command will show the downloaded bytes in the output file (suppressWarnings.txt), but these aren't direct DICOM files, only a text representation of the multipart/related download.
+This cURL command shows the downloaded bytes in the output file (suppressWarnings.txt), but they aren't direct DICOM files, only a text representation of the multipart/related download.
 
 ```
 curl --request GET "{Service URL}/v{version}/studies/1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420/metadata"
@@ -195,7 +195,7 @@ _Details:_
    * Accept: multipart/related; type="application/dicom"; transfer-syntax=*
    * Authorization: Bearer {token value}
 
-This cURL command will show the downloaded bytes in the output file (suppressWarnings.txt), but it's not the DICOM file, only a text representation of the multipart/related download.
+This cURL command shows the downloaded bytes in the output file (suppressWarnings.txt), but it's not the DICOM file, only a text representation of the multipart/related download.
 
 ```
 curl --request GET "{Service URL}/v{version}/studies/1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420/series/1.2.826.0.1.3680043.8.498.45787841905473114233124723359129632652"
@@ -278,7 +278,7 @@ curl --request GET "{Service URL}/v{version}/studies/1.2.826.0.1.3680043.8.498.1
 
 ## Query DICOM (QIDO)
 
-In the following examples, we'll search for items using their unique identifiers. You can also search for other attributes, such as `PatientName`.
+In the following examples, we search for items using their unique identifiers. You can also search for other attributes, such as `PatientName`.
 
 ### Search for studies
 
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md
@@ -10,9 +10,9 @@ ms.date: 02/15/2022
 ms.author: mmitrik
 ---
 
-# Using DICOM Standard APIs with Python
+# Use DICOMweb Standard APIs with Python
 
-This article shows how to work with the DICOM&reg; service using Python 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 Python and [sample .dcm DICOM&reg; files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
 
 Use these sample files:
 
@@ -36,7 +36,7 @@ The filename, studyUID, seriesUID, and instanceUID of the sample DICOM files are
 
 To use the DICOMweb Standard APIs, you must have an instance of the DICOM service deployed. If you haven't already deployed 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:
+After you deploy an instance of the DICOM service, retrieve the URL for your App service:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Search **Recent resources** and select your DICOM service instance.
@@ -49,7 +49,7 @@ For this code, you access a Public Preview Azure service. It's important that yo
 
 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.
 
-### Import the appropriate Python libraries
+### Import the Python libraries
 
 First, import the necessary Python libraries.
 
@@ -138,13 +138,13 @@ if (response.status_code != 200):
     print('Error! Likely not authenticated!')
 ```
 
-## Uploading DICOM Instances (STOW)
+## Upload DICOM instances (STOW)
 
 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. By passing an array of files 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 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.
 
 _Details:_
 
@@ -185,7 +185,7 @@ response = client.post(url, body, headers=headers, verify=False)
 
 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.  
 
-By passing an array of files 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 of `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}
@@ -249,7 +249,7 @@ response = client.post(url, body, headers=headers, verify=False)
 response  # response should be a 409 Conflict if the file was already uploaded in the above request
 ```
 
-## Retrieve DICOM Instances (WADO)
+## Retrieve DICOM instances (WADO)
 
 The following examples highlight retrieving DICOM instances.
 
