Updated document based on suggestions.

Author: Pooja Adhikari

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

@@ -10,47 +10,43 @@ ms.author: buchvarun
 ---
 
 # What is URL manipulation
-URL manipulation allows customizing URL of the image location that is in response object.
+Using URL manipulation allows you to customize the URL of the image location that is in the response object.
 
-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:
+For the following API operations the DICOM service returns the fully qualified URL of the image location in the response object, under a DICOM tag (UR) in the response object.
 1. Retrieve Instance 
 2. Retrieve WorkItems
 3. Retrieve OperationStatus
 4. Resolve QueryTag
 5. Resolve QueryTagError
 
-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:
+The following is an example of a fully qualified image location URL. This could be found in the standard response for a STOW operation for a DICOM service that has data partition enabled, with partition name "foo".
 
 `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`
 
- To breakdown the structure of the above URL, it consists of following three parts:
+ The preceding URL consists of 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`
+ 2. path -> `v2/partitions/foo` (the path that represents the version of DICOM service being used and the datapartition name, if enabled)
+ 3. The 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`
 
- This feature will allow to customize the path of the image URL, if directed by client based on the request headers they have provided.
+ This feature allows you to customize the path of the image URL, if directed by the client, based on the request headers provided.
 
  # How it works
-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.
-Example:
-   `X-Forwarded-Prefix: /prefix`
+The modified URL will be based on following two headers.
+1. X-Forwarded-Host: The domain name of the original host (the one the client requested before the proxy or load balancer handled the request). For example: `X-Forwarded-Host: www.example.com`
 
+2. X-Forwarded-Prefix:  the original URL path or prefix that was part of the client’s request before the proxy forwarded or changed the request. For example: `X-Forwarded-Prefix: /prefix`
 
 These headers are a part of [.net core standard forwarded headers](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-8.0#forwarded-headers). 
 
-If x-forwarded-host header is present in the request object, it would replace the host name with the value provided.
+If `x-forwarded-host` header is present in the request object, it replaces the host name with the value provided.
 
-if x-forwarded-prefix header is present in the request object, it would replace the path with the value provided.
+If `x-forwarded-prefix` header is present in the request object, it replaces the path with the value provided.
 
- # List of API that can use forwarded headers for URL manipulation
+ # List of API's that can use forwarded headers for URL manipulation
 
  ### STOW, WADO, worklist, operation status, querytag and querytagerror APIs
 
-Details of a request header for a STOW operation with the forwarded headers:
-
+Here are the details of a request header for a STOW operation with the forwarded headers:
 * Path: ../studies/{study}
 * Method: POST
 * Headers:
@@ -63,13 +59,15 @@ Details of a request header for a STOW operation with the forwarded headers:
     * Content-Type: application/DICOM for each file uploaded, separated by a boundary value
 
 ## Example:
-### Value of DICOM tag with VR = UR for a STOW operation when the above headers are not provided:
+The following is an example of a DICOM tag with VR = UR for a STOW operation when the above headers are not provided:
+
 `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`
 
-### Value of DICOM tag with VR = UR for a STOW operation when the above headers are provided:
+
+The following is an example of a DICOM tag with VR = UR for a STOW operation when the above headers are provided:
 
 Sample Request object:
- * Path: https://localhost:63838/v2/partitions/foo/studies/studies/{study}
+* Path: https://localhost:63838/v2/partitions/foo/studies/studies/{study}
 * Method: POST
 * Headers:
     * Accept: application/DICOM+json
@@ -86,8 +84,8 @@ URL of image:
 
 
  # Things to remember
- 1. Forwarded headers do not 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.
+ 1. Forwarded headers do not have to be used together. If there is a need to, simply replace hostname and not path. Only the forwarded host header can be used. Similarly, if there is a need to replace the path, only the forwarded prefix header can be used.
 
- 2. Client is responsible for mapping the hostname and path provided in forwarded headers with correct DICOM service hostname and pathbase.
+ 2. The client is responsible for mapping the hostname and path provided in forwarded headers to the correct DICOM service hostname and pathbase.
 
  [!INCLUDE [DICOM trademark statement](../includes/healthcare-APIs-DICOM-trademark.md)]