acrolinx fixes

Author: shellyhaverkamp

articles/healthcare-apis/dicom/data-partitions.md

@@ -15,21 +15,27 @@ Data partitioning allows you to set up a lightweight data partition scheme to st
 
 Although UIDs should be [unique across all contexts](http://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_9.html), it's common practice for healthcare providers to write DICOM files to portable storage media and then give them to a patient. The patient then gives the files to another healthcare provider, who then transfers the files into a new DICOM storage system. Therefore, multiple copies of one DICOM file do commonly exist in isolated DICOM systems. Data partitioning provides an on-ramp for your existing data stores and workflows. 
 
-## Enable data partitions on initial deployment of the DICOM service
+## Limitations
 
-You enable data partitions feature by selecting **Enable data partitions** when you deploy a new DICOM service. After data partitioning is turned on, it can't be turned off. In addition, data partitions can't be turned on for any DICOM service that is already deployed.
+- The **partitions feature** can't be turned off after you turn it on.
+- **Querying across partitions** isn't supported.
+- **Updating and deleting partitions** is also not supported.
 
-After the data partitions setting is enabled, the capability modifies the API surface of the DICOM server and makes any previous data accessible under the `Microsoft.Default` partition. 
+## Enable data partitions during initial deployment 
+
+You enable data partitions by selecting **Enable data partitions** when you deploy a new DICOM service. After data partitioning is turned on, it can't be turned off. In addition, data partitions can't be turned on for any DICOM service that is already deployed.
+
+After the data partitions setting is turned on, the capability modifies the API surface of the DICOM server and makes any previous data accessible under the `Microsoft.Default` partition. 
 
 > [!IMPORTANT]
-> Data partitions can't be disabled if partitions other than `Microsoft.Default` are present. In this case, the system throws a `DataPartitionsFeatureCannotBeDisabledException` error on startup.
+> Data partitions can't be disabled if partitions other than `Microsoft.Default` are present. When this situation happens, the system throws a `DataPartitionsFeatureCannotBeDisabledException` error on startup.
 
 ## API changes
 
-All unique resource identifies (URIs) assume an implicit DICOM service base URI. For example, the base URI of a DICOM server running locally is `https://localhost:63838/`.
+All unique resource identifiers (URIs) assume an implicit DICOM service base URI. For example, the base URI of a DICOM server running locally is `https://localhost:63838/`.
 Example requests can be sent in the [Postman collection](../resources/Conformance-as-Postman.postman_collection.json) by providing a value for the `partitionName` collection variable.
 
-### List all data partitions
+#### List all data partitions
 This command Lists all data partitions:
 
 ```http
@@ -50,11 +56,11 @@ GET /partitions
 | 204 (No Content)  |                               | No partitions exist.                   |
 | 400 (Bad Request) |                               | Data partitions capability is disabled.   |
 
-### STOW, WADO, QIDO, Delete, Export update and worklist APIs
+#### STOW, WADO, QIDO, delete, export, update, and worklist APIs
 
 After partitions are enabled, STOW, WADO, QIDO, delete, export, update, and worklist requests must include a data partition URI segment after the base URI, with the form `/partitions/{partitionName}`, where `partitionName` is:
 
- - Up to 64 characters long
+ - Up to 64 characters long.
  - Any combination of alphanumeric characters, `.`, `-`, and `_`, to allow both DICOM UID and GUID formats, as well as human-readable identifiers.
 
 | Action  | Example URI                                                         |
@@ -74,15 +80,14 @@ After partitions are enabled, STOW, WADO, QIDO, delete, export, update, and work
 | 400 (Bad Request) | `PartitionName` value is missing in the route segment.      |
 | 400 (Bad Request) | Specified `PartitionName {PartitionName}` doesn't exist.   |
 
-### Other APIs
+#### Other APIs
 All other APIs, including [extended query tags](../how-to-guides/extended-query-tags.md), [operations](../how-to-guides/extended-query-tags.md#get-operation), and [change feed](change-feed.md) continue to be accessed at the base URI. 
 
-## Manage data partitions
+### Manage data partitions
 
 The only management operation supported for partitions is an implicit creation during STOW and workitem create requests. If the partition specified in the URI doesn't exist, the system creates it implicitly and the response returns a retrieve URI including the partition path. 
 
-
-## Partition definitions
+### Partition definitions
 
 A partition is a unit of logical isolation and data uniqueness.