Clean ups

Author: Pooja Adhikari

articles/healthcare-apis/dicom/dicom-proxy-url-support.md

@@ -1,42 +1,37 @@
 ---
-title: Support for url manipulation for the DICOM service in Azure Health Data Services
-description: Learn how to customize or manipulate the url of the image location that is in response object.
+title: Support for url customization for the DICOM service in Azure Health Data Services
+description: Learn how to customize the url of the image location that is in response object.
 author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: fhir
 ms.topic: overview
-ms.date: 03/26/2024
+ms.date: 10/17/2024
 ms.author: buchvarun
 ---
 
 # What is URL manipulation
-URl manipulation allows customizing the url of the image location that is in response object.
+URl manipulation allows customizing url of the image location that is in response object.
 
-The Dicom service returns the fully qualified url of the imae location in the response object in the dicom tag (UR) in following api resonse:
+Dicom service returns the fully qualified url of the image location in response object under dicom tag (UR) in the response object of following api operations:
 1. Retrieve Instance 
 2. Retrieve WorkItems
 3. Retrieve OperationStatus
 4. Resolve QueryTag
 5. Resolve QueryTagError
 
-An example of a standard response for a stow operatoin is as below:
+An example of fully qualified image location of url in the standard response for a stow operation for a dicom service that has data partition enabled with partition name "foo" is as below:
 
 `https://localhost:63838/v2/partitions/foo/studies/1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420/series/1.2.826.0.1.3680043.8.498.77033797676425927098669402985243398207/instances/1.2.826.0.1.3680043.8.498.13273713909719068980354078852867170114`
 
-Here, the url in the response contains a dicom tag "UR" with the value represents the location of the image.
-
- The hostname of this Url represents the dicom service that is being used. 
-
- To breakdown the structure of the above urlm it consists of
- 1. hostname -> `https://localhost:63838`
- 2. path -> `v2/partitions/foo`
+ To breakdown the structure of the above url, it consists of following three parts:
+ 1. hostname -> `https://localhost:63838` (the hostname of dicom service)
+ 2. path -> `v2/partitions/foo` (path that represents the version of dicom service being used and the datapartition name if it enabled)
  3. Dicom web standard path -> `studies/1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420/series/1.2.826.0.1.3680043.8.498.77033797676425927098669402985243398207/instances/1.2.826.0.1.3680043.8.498.13273713909719068980354078852867170114`
 
- The feature allows to manipuate the hostname and the path of the response object if needed.
+ This feature will allow to customize the path of the image url, if directed by client based on the request headers they have provided.
 
  # How it works
- This feature will allow modify the path of response url if directed by client based on the request headers they provided.
-The modified header will be based on following two headers:
+The modified url will be based on following two headers:
 1. X-Forwarded-Host: This represents the domain name of the original host (the one the client requested before the proxy or load balancer handled the request). Example: `X-Forwarded-Host: www.example.com`
 
 2. X-Forwarded-Prefix: This represents the original URL path or prefix that was part of the client’s request before the proxy forwarded or changed the request.
@@ -93,8 +88,6 @@ Url of image:
  # Things to remember
  1. Forwarded headers donot have to be used together. If there is a need to just replace hostname and not path, only forwarded host header can be used. Similarly, if there is a need to just replace path, only forwared prefix header can be used.
 
- 2. This is only url manipulation. Client is responsible for mapping the headers and path provided in forwarded headers with the actual dicom service hostname and pathbase.
-
-
+ 2. Client is responsible for mapping the hostname and path provided in forwarded headers with correct dicom service hostname and pathbase.
 
  [!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]