adding additional edits

Author: stevemunk

articles/azure-maps/drawing-package-guide.md

@@ -53,7 +53,7 @@ When preparing your facility drawing files for the Conversion service, make sure
 
 ## Step 2: Prepare the DWG files
 
-This part of the guide will show you how to use CAD commands to ensure that your DWG files meet the requirements of the Conversion service.
+This part of the guide shows you how to use CAD commands to ensure that your DWG files meet the requirements of the Conversion service.
 
 You may choose any CAD software to open and prepare your facility drawing files. However, this guide is created using Autodesk's AutoCAD® software. Any commands referenced in this guide are meant to be executed using Autodesk's AutoCAD® software.  
 
@@ -91,15 +91,15 @@ The following image is taken from the sample package, and shows the exterior lay
 
 ### Unit layer
 
-Units are navigable spaces in the building, such as offices, hallways, stairs, and elevators. A closed entity type such as Polygon, closed Polyline, Circle, or closed Ellipse is required to represent each unit. So, walls and doors alone won't create a unit because there isn’t an entity that represents the unit.  
+Units are navigable spaces in the building, such as offices, hallways, stairs, and elevators. A closed entity type such as Polygon, closed Polyline, Circle, or closed Ellipse is required to represent each unit. So, walls and doors alone doesn't create a unit because there isn’t an entity that represents the unit.  
 
 The following image is taken from the [sample drawing package] and shows the unit label layer and unit layer in red. All other layers are turned off to help with visualization. Also, one unit is selected to help show that each unit is a closed Polyline.  
 
 :::image type="content" source="./media/drawing-package-guide/unit.png" alt-text="Screenshot showing the unit layer of a facility.":::
 
 ### Unit label layer
 
-If you'd like to add a name property to a unit, you'll need to add a separate layer for unit labels. Labels must be provided as single-line text entities that fall inside the bounds of a unit. A corresponding unit property must be added to the manifest file where the `unitName` matches the Contents of the Text.  To learn about all supported unit properties, see [`unitProperties`](#unitproperties).
+If you'd like to add a name property to a unit, add a separate layer for unit labels. Labels must be provided as single-line text entities that fall inside the bounds of a unit. A corresponding unit property must be added to the manifest file where the `unitName` matches the Contents of the Text.  To learn about all supported unit properties, see [`unitProperties`](#unitproperties).
 
 ### Door layer
 
@@ -153,7 +153,7 @@ The `georeference` object is used to specify where the facility is located geogr
 
 ### dwgLayers
 
-The `dwgLayers` object is used to specify that DWG layer names where feature classes can be found. To receive a property converted facility, it's important to provide the correct layer names. For example, a DWG wall layer must be provided as a wall layer and not as a unit layer. The drawing can have other layers such as furniture or plumbing; but, they'll be ignored by the Azure Maps Conversion service if they're not specified in the manifest.  
+The `dwgLayers` object is used to specify that DWG layer names where feature classes can be found. To receive a property converted facility, it's important to provide the correct layer names. For example, a DWG wall layer must be provided as a wall layer and not as a unit layer. The drawing can have other layers such as furniture or plumbing; but, the Azure Maps Conversion service ignores them if they're not specified in the manifest.  
 
 The following example of the `dwgLayers` object in the manifest.  
 
@@ -193,7 +193,7 @@ The `unitProperties` object allows you to define other properties for a unit tha
 
 The following image is taken from the [sample drawing package]. It displays the unit label that's associated to the unit property in the manifest.
 
-:::image type="content" source="./media/drawing-package-guide/unit-property.png" alt-text="Screenshot showing the unit label that will be associated to the unity property in the manifest.":::
+:::image type="content" source="./media/drawing-package-guide/unit-property.png" alt-text="Screenshot showing the unit label that is associated to the unity property in the manifest.":::
 
 The following snippet shows the unit property object that is associated with the unit.  
 
@@ -221,7 +221,7 @@ The following snippet shows the unit property object that is associated with the
 
 ## Step 4: Prepare the Drawing Package
 
-You should now have all the DWG drawings prepared to meet Azure Maps Conversion service requirements. A manifest file has also been created to help describe the facility. All files will need to be zipped into a single archive file, with the `.zip` extension. It's important that the manifest file is named `manifest.json` and is placed in the root directory of the zipped package. All other files can be in any directory of the zipped package if the filename includes the relative path to the manifest. For an example of a drawing package, see the [sample drawing package].
+You should now have all the DWG drawings prepared to meet Azure Maps Conversion service requirements. A manifest file has also been created to help describe the facility. All files need to be zipped into a single archive file, with the `.zip` extension. It's important that the manifest file is named `manifest.json` and is placed in the root directory of the zipped package. All other files can be in any directory of the zipped package if the filename includes the relative path to the manifest. For an example of a drawing package, see the [sample drawing package].
 
 :::zone-end
 
@@ -298,7 +298,7 @@ You can use the [Azure Maps Creator onboarding tool] to create new and edit exis
 
 To process the DWG files, enter the geography of your Azure Maps Creator resource, the subscription key of your Azure Maps account and the path and filename of the DWG ZIP package, the select **Process**. This process can take several minutes to complete.
 
-:::image type="content" source="./media/creator-indoor-maps/onboarding-tool/create-manifest.png" alt-text="Screenshot showing the create a new manifest screen of the Azure Maps Creator onboarding tool.":::
+:::image type="content" source="./media/creator-indoor-maps/onboarding-tool/create-manifest.png" alt-text="Screenshot showing the 'create a new manifest' screen of the Azure Maps Creator onboarding tool.":::
 
 ### Facility levels
 
@@ -313,7 +313,7 @@ The following example is taken from the [sample drawing package v2]. The facilit
 The `dwgLayers` object is used to specify the DWG layer names where feature classes can be found. To receive a properly converted facility, it's important to provide the correct layer names. For example, a DWG wall layer must be provided as a wall layer and not as a unit layer. The drawing can have other layers such as furniture or plumbing; but, the Azure Maps Conversion service ignores anything not specified in the manifest.
 Defining text properties enables you to associate text entities that fall inside the bounds of a feature. Once defined they can be used to style and display elements on your indoor map
 
-:::image type="content" source="./media/creator-indoor-maps/onboarding-tool/dwg-layers.png" alt-text="Screenshot showing the create a new manifest screen of the onboarding tool.":::
+:::image type="content" source="./media/creator-indoor-maps/onboarding-tool/dwg-layers.png" alt-text="Screenshot showing the 'create a new manifest' screen of the onboarding tool.":::
 
 > [!IMPORTANT]
 > Wayfinding support for `Drawing Package 2.0` will be available soon. The following feature class should be defined (not case sensitive) in order to use [wayfinding]. `Wall` will be treated as an obstruction for a given path request. `Stair` and `Elevator` will be treated as level connectors to navigate across floors:
@@ -336,7 +336,7 @@ The **Anchor Point Angle** is specified in degrees between true north and the dr
 
 You position the facility's location by entering either an address or longitude and latitude values. You can also pan the map to make minor adjustments to the facility's location.
 
-:::image type="content" source="./media/creator-indoor-maps/onboarding-tool/georeference-location-defined.png" alt-text="Screenshot showing the georeference tab of the Azure Maps Creator onboarding tool with values entered for the longitude and latitude anchor points.":::
+:::image type="content" source="./media/creator-indoor-maps/onboarding-tool/georeference-location-defined.png" alt-text="Screenshot showing the georeference tab of the Azure Maps Creator onboarding tool with values entered for longitude and latitude.":::
 
 ### Review and download
 

articles/azure-maps/drawing-requirements.md

@@ -59,7 +59,7 @@ The [Conversion service] does the following on each DWG file:
   - Walls
   - Vertical penetrations
 - Produces a *Facility* feature.  
-- Produces a minimal set of default Category features to be referenced by other features:
+- Produces a minimal set of default Category features referenced by other features:
   - room
   - structure
   - wall
@@ -69,7 +69,7 @@ The [Conversion service] does the following on each DWG file:
 
 ## DWG file requirements
 
-A single DWG file is required for each level of the facility. All data of a single level must be contained in a single DWG file.  Any external references (_xrefs_) must be bound to the parent drawing. For example, a facility with three levels will have three DWG files in the drawing package.
+A single DWG file is required for each level of the facility. All data of a single level must be contained in a single DWG file.  Any external references (_xrefs_) must be bound to the parent drawing. For example, a facility with three levels has three DWG files in the drawing package.
 
 Each DWG file must adhere to the following requirements:
 
@@ -87,7 +87,7 @@ Each DWG layer must adhere to the following rules:
 - Self-intersecting polygons are permitted, but are automatically repaired. When they repaired, the [Conversion service] raises a warning. It's advisable to manually inspect the repaired results, because they might not match the expected results.
 - Each layer has a supported list of entity types. Any other entity types in a layer will be ignored. For example, text entities aren't supported on the wall layer.
 
-The table below outlines the supported entity types and converted map features for each layer. If a layer contains unsupported entity types, then the [Conversion service] ignores those entities.  
+The following table outlines the supported entity types and converted map features for each layer. If a layer contains unsupported entity types, then the [Conversion service] ignores those entities.  
 
 | Layer | Entity types | Converted Features |
 | :----- | :-------------------| :-------
@@ -99,13 +99,13 @@ The table below outlines the supported entity types and converted map features f
 | [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 sections below describe the requirements for each layer.
+The following sections describe the requirements for each layer.
 
 ### Exterior layer
 
 The DWG file for each level must contain a layer to define that level's perimeter. This layer is referred to as the *exterior* layer. For example, if a facility contains two levels, then it needs to have two DWG files, with an exterior layer for each file.
 
-No matter how many entity drawings are in the exterior layer, the [resulting facility dataset](tutorial-creator-feature-stateset.md) will contain only one level feature for each DWG file. Additionally:
+No matter how many entity drawings are in the exterior layer, the [resulting facility dataset](tutorial-creator-feature-stateset.md) contains only one level feature for each DWG file. Additionally:
 
 - Exteriors must be drawn as POLYGON, POLYLINE (closed), CIRCLE, or ELLIPSE (closed).
 - Exteriors may overlap, but are dissolved into one geometry.
@@ -270,7 +270,7 @@ The `unitProperties` object contains a JSON array of unit properties.
 |`verticalPenetrationDirection`|    string|    false    |If `verticalPenetrationCategory` is defined, optionally define the valid direction of travel. The permitted values are: `lowToHigh`, `highToLow`, `both`, and `closed`. The default value is `both`. The value is case-sensitive.|
 | `nonPublic` | bool | false | Indicates if the unit is open to the public. |
 | `isRoutable` | bool | false | When this property is set to `false`, you can't go to or through the unit. The default value is `true`. |
-| `isOpenArea` | bool | false | Allows the navigating agent to enter the unit without the need for an opening attached to the unit. By default, this value is set to `true` for units with no openings, and `false` for units with openings. Manually setting `isOpenArea` to `false` on a unit with no openings results in a warning, because the resulting unit won't be reachable by a navigating agent.|
+| `isOpenArea` | bool | false | Allows the navigating agent to enter the unit without the need for an opening attached to the unit. By default, this value is set to `true` for units with no openings, and `false` for units with openings. Manually setting `isOpenArea` to `false` on a unit with no openings results in a warning, because the resulting unit isn't reachable by a navigating agent.|
 
 ### `zoneProperties`
 
@@ -286,7 +286,7 @@ The `zoneProperties` object contains a JSON array of zone properties.
 
 ### Sample drawing package manifest
 
-Below is the manifest file for the sample drawing package. Go to the [Sample drawing package] for Azure Maps Creator on GitHub to download the entire package.
+The following is the manifest file for the sample drawing package. Go to the [Sample drawing package] for Azure Maps Creator on GitHub to download the entire package.
 
 #### Manifest file
 
@@ -494,9 +494,9 @@ One or more DWG layer(s) can be mapped to a user defined feature class. One inst
 
 Text entities that fall within the bounds of a closed shape can be associated to that feature as a property. For example, a room feature class might have text that describes the room name and another the room type [sample drawing package v2]. Additionally:
 
-- Only TEXT and MTEXT entities will be associated to the feature as a property. All other entity types will be ignored.
+- Only TEXT and MTEXT entities are associated to the feature as a property. All other entity types are ignored.
 - The TEXT and MTEXT justification point must fall within the bounds of the closed shape.
-- If more than one TEXT property is within the bounds of the closed shape and both are mapped to one property, one will be randomly selected.
+- If more than one TEXT property is within the bounds of the closed shape and both are mapped to one property, one is randomly selected.
 
 ### Facility level
 

articles/azure-maps/drawing-tools-events.md

@@ -1,6 +1,6 @@
 ---
 title: Drawing tool events | Microsoft Azure Maps
-description: In this article you'll learn, how to add a drawing toolbar to a map using Microsoft Azure Maps Web SDK
+description: This article demonstrates how to add a drawing toolbar to a map using Microsoft Azure Maps Web SDK
 author: brendansco
 ms.author: Brendanc
 ms.date: 12/05/2019
@@ -15,8 +15,8 @@ When using drawing tools on a map, it's useful to react to certain events as the
 
 | Event | Description |
 |-------|-------------|
-| `drawingchanged` | Fired when any coordinate in a shape has been added or changed. | 
-| `drawingchanging` | Fired when any preview coordinate for a shape is being displayed. For example, this event will fire multiple times as a coordinate is dragged. | 
+| `drawingchanged` | Fired when any coordinate in a shape has been added or changed. |
+| `drawingchanging` | Fired when any preview coordinate for a shape is being displayed. For example, this event fires multiple times as a coordinate is dragged. |
 | `drawingcomplete` | Fired when a shape has finished being drawn or taken out of edit mode. |
 | `drawingerased` | Fired when a shape is erased from the drawing manager when in `erase-geometry` mode. |
 | `drawingmodechanged` | Fired when the drawing mode has changed. The new drawing mode is passed into the event handler. |
@@ -65,7 +65,7 @@ This code searches for points of interests inside the area of a shape after the
 
 ### Create a measuring tool
 
-The code below shows how the drawing events can be used to create a measuring tool. The `drawingchanging` is used to monitor the shape, as it's being drawn. As the user moves the mouse, the dimensions of the shape are calculated. The `drawingcomplete` event is used to do a final calculation on the shape after it has been drawn. The `drawingmodechanged` event is used to determine when the user is switching into a drawing mode. Also, the  `drawingmodechanged` event clears the drawing canvas and clears old measurement information.
+The following code shows how the drawing events can be used to create a measuring tool. The `drawingchanging` is used to monitor the shape, as it's being drawn. As the user moves the mouse, the dimensions of the shape are calculated. The `drawingcomplete` event is used to do a final calculation on the shape after it has been drawn. The `drawingmodechanged` event is used to determine when the user is switching into a drawing mode. Also, the  `drawingmodechanged` event clears the drawing canvas and clears old measurement information.
 
 <br/>
 
@@ -78,7 +78,7 @@ The code below shows how the drawing events can be used to create a measuring to
 
 ## Next steps
 
-Learn how to use additional features of the drawing tools module:
+Learn how to use other features of the drawing tools module:
 
 > [!div class="nextstepaction"]
 > [Get shape data](map-get-shape-data.md)