acrolinx edits

Author: anastasia-ms

articles/azure-maps/drawing-conversion-error-codes.md

@@ -288,9 +288,9 @@ The following image shows a label that inside two zones.
 
 To fix a **labelWarning**, ensure that:
 
-* all unit labels are inside units.
-* all zone labels are inside zones.
-* all zone labels are in one and only one zone.
+* All unit labels are inside units.
+* All zone labels are inside zones.
+* All zone labels are in one and only one zone.
 
 ## Drawing Package errors
 
@@ -306,9 +306,9 @@ An **invalidArchiveFormat** error will also occur if the ZIP archive is empty.
 
 To fix an **invalidArchiveFormat** error, verify that:
 
-* your archive file name ends in _.zip_.
-* your ZIP archive contains data.
-* you can open your ZIP archive.
+* Your archive file name ends in _.zip_.
+* Your ZIP archive contains data.
+* You can open your ZIP archive.
 
 ### **invalidUserData**
 
@@ -324,9 +324,9 @@ You attempted to upload a Drawing package with an incorrect `udid` parameter.
 
 To fix an **invalidUserData** error, verify that:
 
-* you've provided a correct `udid` for the uploaded package.
+* You've provided a correct `udid` for the uploaded package.
 * Azure Maps Creator has been enabled for the Azure Maps account you used for uploading the Drawing package.
-* the API request to the Conversion service contains the subscription key to the Azure Maps account you used for uploading the Drawing package.
+* The API request to the Conversion service contains the subscription key to the Azure Maps account you used for uploading the Drawing package.
 
 ### **dwgError**
 

articles/azure-maps/drawing-requirements.md

@@ -20,7 +20,7 @@ The Drawing package includes drawings saved in DWG format, which is the native f
 
 You may choose any CAD software to produce the drawings in the Drawing package.  
 
-The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) converts the Drawing package into map data.  The Conversion service as been developed and tested using the AutoCAD DWG file format, with AC1032 as the internal format version for the DWG files. You're encouraged to select AC1032 for the internal DWG file format version.  
+The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) converts the Drawing package into map data.  The Conversion service has been developed and tested using the AutoCAD DWG file format. `AC1032` is the internal format version for the DWG files. You're encouraged to select `AC1032` for the internal DWG file format version.  
 
 Glossary of terms used within this document.
 
@@ -34,7 +34,12 @@ Glossary of terms used within this document.
 
 ## Drawing Package structure
 
-A Drawing package is a .zip file that consists of files in AutoCAD DWG file format and a manifest file for a single facility. The DWG files can be organized in any way inside the folder, but the manifest file must live at the root directory of the folder. The folder must be zipped in a single archive file, with a .zip extension. The next sections detail the requirements for the DWG files, manifest file, and the content of these files.  
+A Drawing package is a .zip archive that contains the following files:
+
+* DWG files in AutoCAD DWG file format.
+* A _manifest.json_ file for a single facility.
+
+The DWG files can be organized in any way inside the folder, but the manifest file must live at the root directory of the folder. The folder must be zipped in a single archive file, with a .zip extension. The next sections detail the requirements for the DWG files, manifest file, and the content of these files.  
 
 ## DWG files requirements
 
@@ -55,9 +60,9 @@ The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/dat
 
 All conversion jobs result in a minimal set of default categories: room, structure.wall, opening.door, zone, and facility. Additional categories are for each Category Name referenced by objects.  
 
-A DWG layer must contain features of a single class, and classes must not share a layer. For example, units and walls can't share a layer.
+A DWG layer must contain features of a single class. Classes must not share a layer. For example, units and walls can't share a layer.
 
-Moreover:
+DWG layers must also follow the following criteria:
 
 * The origins of drawings for all DWG files must align to the same latitude and longitude.
 * Each level must be in the same orientation as the other levels.
@@ -71,11 +76,11 @@ The table below outlines the supported entity types and supported features for e
 | :----- | :-------------------| :-------
 | [Exterior](#exterior-layer) | Polygon, PolyLine (closed), Circle | Levels
 | [Unit](#unit-layer) |  Polygon, PolyLine (closed), Circle | Vertical Penetrations, Units
-| [Wall](#wall-layer)  | Polygon, PolyLine (closed), Circle | Not applicable. For more details, see the [Wall layer](#wall-layer).
+| [Wall](#wall-layer)  | Polygon, PolyLine (closed), Circle | Not applicable. For more information, see the [Wall layer](#wall-layer).
 | [Door](#door-layer) | Polygon, PolyLine, Line, CircularArc, Circle | Openings
 | [Zone](#zone-layer) | Polygon, PolyLine (closed), Circle | Zone
-| [UnitLabel](#unitlabel-layer) | Text (single line) | Not applicable. This layer can only add properties to the unit features from the Units layer. For more details, see the [UnitLabel layer](#unitlabel-layer).
-| [ZoneLabel](#zonelabel-layer) | Text (single line) | Not applicable. This layer can only add properties to zone features from the ZonesLayer. For more details, see the [ZoneLabel layer](#zonelabel-layer)
+| [UnitLabel](#unitlabel-layer) | Text (single line) | Not applicable. This layer can only add properties to the unit features from the Units layer. For more information, see the [UnitLabel layer](#unitlabel-layer).
+| [ZoneLabel](#zonelabel-layer) | Text (single line) | Not applicable. This layer can only add properties to zone features from the ZonesLayer. For more information, see the [ZoneLabel layer](#zonelabel-layer)
 
 The next sections detail the requirements for each layer.
 
@@ -119,7 +124,7 @@ An example of the Walls layer can be seen as the WALLS layer in the [sample Draw
 
 You may include a DWG layer containing doors. Each door must overlap the edge of a unit from the unit layer.
 
-Doors (openings) in an Azure Maps dataset are represented as a single line segment that overlaps multiple unit boundaries. The following steps are taken to convert geometry in the door layer to opening features in a dataset.
+Doors openings in an Azure Maps dataset are represented as a single-line segment that overlaps multiple unit boundaries. The following steps are taken to convert geometry in the door layer to opening features in a dataset.
 
 ![Steps to generate openings](./media/drawing-requirements/opening-steps.png)
 
@@ -131,7 +136,7 @@ The DWG file for each level may contain a zone layer that defines the physical e
 * Zones may overlap.
 * Zones may fall inside or outside the facility's exterior perimeter.
 
-Name a zone by creating a text object in the _zoneLabel_ layer, and placing the text object inside the bounds of the zone. For more details, see [ZoneLabel layer](#zonelabel-layer).
+Name a zone by creating a text object in the _zoneLabel_ layer, and placing the text object inside the bounds of the zone. For more information, see [ZoneLabel layer](#zonelabel-layer).
 
 An example of the Zones layer can be seen as the ZONES layer in the [sample Drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
 
@@ -209,8 +214,8 @@ The `buildingLevels` object contains a JSON array of buildings levels.
 
 | Property  | Type | Required | Description |
 |-----------|------|----------|-------------|
-|lat    | numeric |    true |    Decimal representation of degrees latitude at the facility drawing's origin. The origin coordinates must be in WGS84 Web Mercator (EPSG:3857).|
-|lon    |numeric|    true|    Decimal representation of degrees longitude at the facility drawing's origin. The origin coordinates must be in WGS84 Web Mercator (EPSG:3857). |
+|lat    | numeric |    true |    Decimal representation of degrees latitude at the facility drawing's origin. The origin coordinates must be in WGS84 Web Mercator (`EPSG:3857`).|
+|lon    |numeric|    true|    Decimal representation of degrees longitude at the facility drawing's origin. The origin coordinates must be in WGS84 Web Mercator (`EPSG:3857`). |
 |angle|    numeric|    true|   The clockwise angle, in degrees, between true north and the drawing’s vertical (Y) axis.   |
 
 ### dwgLayers

articles/azure-maps/how-to-manage-creator.md

@@ -28,7 +28,7 @@ This article takes you through the steps to create and delete a Creator resource
 
     ![Create Azure Maps Creator page](./media/how-to-manage-creator/creator-blade.PNG)
 
-4. Enter the name and location for your Creator resource. Currently, the United States is the only supported geographical location. Click **Review + create**.
+4. Enter the name and location for your Creator resource. Currently, Creator is only supported in the United States. Click **Review + create**.
 
    ![Enter Creator account information page](./media/how-to-manage-creator/creator-creation.PNG)
 
@@ -62,11 +62,13 @@ To delete the Creator resource, navigate to your Azure Maps account. Select **Ov
 
 Click the **Delete** button and type your Creator name to confirm deletion. Once the resource is deleted, you'll see a confirmation page, like in the image below:
 
-![Creator delete confirmation](./media/how-to-manage-creator/creator-confirmdelete.png)
+![Creator page with delete confirmation](./media/how-to-manage-creator/creator-confirmdelete.png)
 
 ## Authentication
 
-Creator inherits Azure Maps Access Control (IAM) settings. All API calls for data access must be sent with authentication and authorization rules. Also, Creator usage data is incorporated in your Azure Maps usage charts and activity log.  For more detail, see [Manage authentication in Azure Maps](https://docs.microsoft.com/azure/azure-maps/how-to-manage-authentication).
+Creator inherits Azure Maps Access Control (IAM) settings. All API calls for data access must be sent with authentication and authorization rules.
+
+Creator usage data is incorporated in your Azure Maps usage charts and activity log.  For more information, see [Manage authentication in Azure Maps](https://docs.microsoft.com/azure/azure-maps/how-to-manage-authentication).
 
 ## Access to Creator services
 

articles/azure-maps/indoor-map-dynamic-styling.md

@@ -12,7 +12,7 @@ manager: philmea
 
 # Implement dynamic styling for Creator indoor maps
 
-The Azure Maps Creator [Feature State service](https://docs.microsoft.com/rest/api/maps/featurestate/featurestate) lets you apply styles based on the dynamic properties of indoor map data features.  For example, you can render facility meeting rooms with a specific color to reflect occupancy status. In this article, we'll show you how to dynamically render indoor map features based on associated dynamic properties (*states*) using the [Feature State service](https://docs.microsoft.com/rest/api/maps/featurestate/featurestate) and the [Indoor Web Module](how-to-use-indoor-module.md).
+Azure Maps Creator [Feature State service](https://docs.microsoft.com/rest/api/maps/featurestate/featurestate) lets you apply styles based on the dynamic properties of indoor map data features.  For example, you can render facility meeting rooms with a specific color to reflect occupancy status. In this article, we'll show you how to dynamically render indoor map features with the [Feature State service](https://docs.microsoft.com/rest/api/maps/featurestate/featurestate) and the [Indoor Web Module](how-to-use-indoor-module.md).
 
 ## Prerequisites
 

articles/azure-maps/tutorial-creator-indoor-maps.md

@@ -98,7 +98,7 @@ Use the [Data Upload API](https://docs.microsoft.com/rest/api/maps/data/uploadpr
 
 3. Click the **Send** button and wait for the request to process. Once the request completes, go to the **Headers** tab of the response, and look for the **Location** key. Copy the value of the **Location** key, which is the `status URL` for the conversion request.
 
-4. Start a new **GET** HTTP method in the builder tab. Append your Azure Maps primary subscription key to the `status URL`. Make a **GET** request at the `status URL` from the previous step. If the conversion process hasn't yet completed, you may see something like the following:
+4. Start a new **GET** HTTP method in the builder tab. Append your Azure Maps primary subscription key to the `status URL`. Make a **GET** request at the `status URL` from the previous step. If the conversion process hasn't yet completed, you may see something like the following JSON response:
 
     ```json
     {
@@ -123,7 +123,7 @@ Use the [Data Upload API](https://docs.microsoft.com/rest/api/maps/data/uploadpr
 >[!NOTE]
 >The Postman application does not natively support HTTP Long Running Requests. As a result, you may notice a long delay while making a **GET** request at the status URL.  Wait about thirty seconds and try clicking the **Send** button again until the response shows success or fail.
 
-The sample Drawing package should be converted without errors. However, if you receive errors from your own Drawing package, the JSON response, will give you a link to the [Drawing error visualizer](azure-maps-drawing-errors-visualizer.md). The Drawing error visualizer allows you to inspect the details of errors and warnings. To receive recommendations on how to resolve conversion errors and warnings, see the [Drawing conversion errors and warnings](drawing-conversion-error-codes.md).
+The sample Drawing package should be converted without errors or warnings. However, if you receive errors or warnings from your own Drawing package, the JSON response will give you a link to the [Drawing error visualizer](azure-maps-drawing-errors-visualizer.md). The Drawing Error visualizer allows you to inspect the details of errors and warnings. To receive recommendations on how to resolve conversion errors and warnings, see the [Drawing conversion errors and warnings](drawing-conversion-error-codes.md).
 
 ```json
 {