Update dicom-services-conformance-statement-v2.md

Author: abdullah248

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

@@ -98,7 +98,7 @@ Each file stored must have a unique combination of `StudyInstanceUID`, `SeriesIn
 Only transfer syntaxes with explicit Value Representations are accepted.
 
 > [!NOTE]
-> Requests are limited to 4GB. No single DICOM file or combination of files might exceed this limit.
+> Requests are limited to 4 GB. No single DICOM file or combination of files might exceed this limit.
 
 #### Store changes from v1
 In previous versions, a Store request would fail if any of the [required](#store-required-attributes) or [searchable attributes](#searchable-attributes) failed validation. Beginning with V2, the request fails only if **required attributes** fail validation.
@@ -113,19 +113,19 @@ If an attribute is padded with nulls, the attribute is indexed when searchable a
 The [external metadata](external-metadata.md#store-stow-rs) documentation explains the ability to store DICOM file with external metadata.
 
 #### Store DICOM file with Expiry
-When storing a DICOM file, users can specify a deletion time in the future through the usage of expiry headers.
+Expiry headers allow users to specify a future deletion time when storing.
 
 In order to set an expiry time, the following headers must be set on POST or PUT requests.
 
 | Header                                | Accepted Values    | Description                                                                                  |
 | :------------------------------------ | :----------------- | :------------------------------------------------------------------------------------------- |
 | `msdicom-expiry-option`               | `RelativeToNow`    | How the deletion time is calculated. Currently the only supported option is `RelativeToNow`  |
 | `msdicom-expiry-level`                | `Study`            | The level at which the expiry should be set. Currently only supported at the `Study` level.  |
-| `msdicom-expiry-time-milliseconds`    | Integer values > 0 | The number of milliseconds after which the study should be deleted                           |
+| `msdicom-expiry-time-milliseconds`    | Integer values > 0 | The number of milliseconds after which the study should be deleted.                          |
 
-At this time, expiry is only supported at the study level, meaning that all instances of a study will be deleted at the same time. If multiple instances are stored for the same study in seperate requests, the deletion will be based on the expiry headers sent in the last STOW request. In the case that the last STOW request does not specify expiry headers, the study will not be scheduled for deletion and any previously sent expiry headers will be ignored.
+At this time, expiry is only supported at the study level, meaning that all instances of a study will be deleted at the same time. If multiple instances are stored for the same study in separate requests, the deletion will be based on the expiry headers sent in the last STOW request. In the case that the last STOW request doesn't specify expiry headers, the study won't be scheduled for deletion and any previously sent expiry headers will be ignored.
 
-When using the `RelativeToNow` expiry option, the deletion time will be calulcated based on the time the request is recieved by the DICOM service. The deletion may not happen at the exact time calculated, but within a few hours of the calculated time. 
+The `RelativeToNow` expiry option will calculate the expiry time based on the time the request is received by the DICOM service. The deletion may not happen at the exact time calculated, but within a few hours of the calculated time. 
 
 #### Store response status codes
 
@@ -507,7 +507,7 @@ We support searching the following attributes and search types.
 | `SOPInstanceUID`                  |             |            |       X       |                |         X         |            X            |
 
 > [!NOTE]
-> We do not support searching using empty string for any attributes.
+> We don't support searching using empty string for any attributes.
 
 #### Search matching
 
@@ -640,7 +640,7 @@ The query API returns one of the following status codes in the response.
 | `400 (Bad Request)` | The server was unable to perform the query because the query component was invalid. The response body contains details of the failure. |
 | `401 (Unauthorized)` | The client isn't authenticated. |
 | `403 (Forbidden)` | The user isn't authorized. |
-| `414 (URI Too Long)` | URI exceeded maximum supported length of 8192 characters. |
+| `414 (URI Too Long)` | URI exceeded maximum supported length of 8,192 characters. |
 | `424 (Failed Dependency)` | The DICOM service can't access a resource it depends on to complete this request. An example is failure to access the connected Data Lake store, or the key vault for supporting customer-managed key encryption. |
 | `503 (Service Unavailable)` | The service is unavailable or busy. Try again later. |
 
@@ -671,7 +671,7 @@ Parameters `study`, `series`, and `instance` correspond to the DICOM attributes
 There are no restrictions on the request's `Accept` header, `Content-Type` header, or body content.
 
 > [!NOTE]
-> After a Delete transaction, the deleted instances will not be recoverable.
+> After a Delete transaction, the deleted instances won't be recoverable.
 
 ### Response status codes
 
@@ -952,7 +952,7 @@ We support searching on the following attributes.
 | `StudyInstanceUID`                                         |
 
 > [!NOTE]
-> We do not support searching using empty string for any attributes.
+> We don't support searching using empty string for any attributes.
 
 ##### Search Matching