included acrolinx suggestions to get required score

Author: Gunjit Chhatwal

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

@@ -30,7 +30,7 @@ The Medical Imaging Server for DICOM® supports a subset of the DICOMweb Stan
   * [Request Cancellation](#request-cancellation)
   * [Search Workitems](#search-workitems)
 
-Additionally, these nonstandard API(s) are supported:
+Additionally, these nonstandard APIs are supported:
 
 * [Change Feed](change-feed-overview.md)
 * [Extended Query Tags](dicom-extended-query-tags-overview.md)
@@ -751,7 +751,7 @@ The request payload might include Action Information as [defined in the DICOM St
 
 | Code                           | Description                                                                                                                                                                                                        |
 | :----------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `202 (Accepted)`               | The request was accepted by the server, but the Target Workitem state isn't changed yet.                                                                                                                           |
+| `202 (Accepted)`               | Server has accepted the request, but the Target Workitem state isn't changed yet.                                                                                                                           |
 | `400 (Bad Request)`            | There was a problem with the syntax of the request.                                                                                                                                                                |
 | `401 (Unauthorized)`           | The client isn't authenticated.                                                                                                                                                                                    |
 | `403 (Forbidden)`              | The user isn't authorized.                                                                                                                                                                                         |
@@ -937,7 +937,7 @@ We support these matching types:
 | Range Query | `Scheduled​Procedure​Step​Start​Date​Time` | `{attributeID}={value1}-{value2}`. For date/time values, we support an inclusive range on the tag. This range is mapped to `attributeID >= {value1} AND attributeID <= {value2}`. If `{value1}` isn't specified, all occurrences of dates/times prior to and including `{value2}` is matched. Likewise, if `{value2}` isn't specified, all occurrences of `{value1}` and subsequent dates/times are matched. However, one of these values must be present. `{attributeID}={value1}-` and `{attributeID}=-{value2}` are valid, however, `{attributeID}=-` isn't valid. |
 | Exact Match | All supported attributes                   | `{attributeID}={value1}`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | Fuzzy Match | `PatientName`                              | Matches any component of the name that starts with the value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| WildCard Match | `PatientID`, <br/> `ReferencedRequestSequence.AccessionNumber`, <br/> `ReferencedRequestSequence.RequestedProcedureID`, <br/> `ProcedureStepState`, <br/> `ScheduledStationNameCodeSequence.CodeValue`, <br/> `ScheduledStationClassCodeSequence.CodeValue`, <br/> `ScheduledStationGeographicLocationCodeSequence.CodeValue`                              | Following wildcard characters are supported - <br/> `*` - Matches zero or more characters. E.g. - `{attributeID}={val*}` will match "val", "valid", "value" but not "evaluate". <br/> `?` - Matches a single character. E.g. - `{attributeID}={valu?}` will match "value", "valu1" but not "valued" or "valu"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| WildCard Match | `PatientID`, <br/> `ReferencedRequestSequence.AccessionNumber`, <br/> `ReferencedRequestSequence.RequestedProcedureID`, <br/> `ProcedureStepState`, <br/> `ScheduledStationNameCodeSequence.CodeValue`, <br/> `ScheduledStationClassCodeSequence.CodeValue`, <br/> `ScheduledStationGeographicLocationCodeSequence.CodeValue`                              | Following wildcard characters are supported - <br/> `*` - Matches zero or more characters. For example - `{attributeID}={val*}` matches "val", "valid", "value" but not "evaluate". <br/> `?` - Matches a single character. For example - `{attributeID}={valu?}` matches "value", "valu1" but not "valued" or "valu"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 
 > [!NOTE]
 > Although we don't support full sequence matching, we do support exact match on the attributes listed that are contained in a sequence.