Merge pull request #115660 from anastasia-ms/atlas

PR Review 3

Author: tfosmark

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

@@ -31,7 +31,7 @@ Use the [Azure Maps Data Upload API](https://docs.microsoft.com/rest/api/maps/da
 
 ## Convert a Drawing package
 
-The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) converts an uploaded Drawing package into indoor map data. The Conversion service also validates the package. Validation issues are classified into two types: errors and warnings. If any errors are detected, the conversion process fails. Should warnings be detected, the conversion will succeed. However, it’s recommended that you review and resolve all warnings. A warning means that part of the conversion was ignored or automatically fixed. Failing to resolve the warnings could result in errors in latter processes. For more information, see [Drawing package warnings and errors](drawing-conversion-error-codes.md).
+The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) converts an uploaded Drawing package into indoor map data. The Conversion service also validates the package. Validation issues are classified into two types: errors and warnings. If any errors are detected, the conversion process fails. Should warnings be detected, the conversion will succeed. However, it’s recommended that you review and resolve all warnings. A warning means that part of the conversion was ignored or automatically fixed. Failing to resolve the warnings could result in errors in latter processes. For more information, see [Drawing package warnings and errors](drawing-conversion-error-codes.md).
 
 When an error occurs, the Conversion service provides a link to the [Azure Maps Drawing Error Visualizer](drawing-error-visualizer.md) stand-alone web application. You can use the Drawing Error Visualizer to inspect [Drawing package warnings and errors](drawing-conversion-error-codes.md) that occurred during the conversion process. Once you have fixed the errors, you can then attempt to upload and convert the package.
 

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

@@ -12,7 +12,7 @@ manager: philMea
 
 # Drawing conversion errors and warnings
 
-The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) lets you convert uploaded Drawing packages into map data. Drawing packages must adhere to the [Drawing package requirements](drawing-requirements.md). If one or more requirements aren't met, then the Conversion service will return errors or warnings. This article lists the conversion error and warning codes, with recommendations on how to resolve them. It also provides some examples of drawings that can cause the Conversion service to return these codes.
+The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) lets you convert uploaded Drawing packages into map data. Drawing packages must adhere to the [Drawing package requirements](drawing-requirements.md). If one or more requirements aren't met, then the Conversion service will return errors or warnings. This article lists the conversion error and warning codes, with recommendations on how to resolve them. It also provides some examples of drawings that can cause the Conversion service to return these codes.
 
 The Conversion service will succeed if there are any conversion warnings. However, it's recommended that you review and resolve all warnings. A warning means part of the conversion was ignored or automatically fixed. Failing to resolve the warnings could result in errors in latter processes.
 
@@ -68,7 +68,7 @@ The **unsupportedFeatureRepresentation** warning occurs when the drawing contain
 
 The image below shows an unsupported entity type as a multi-line text object on a label layer.
 
-![Example of a multi-line text object on label layer](./media/drawing-conversion-error-codes/multiline.png)
+![Example of a multi-line text object on label layer](./media/drawing-conversion-error-codes/multi-line.png)
 
 #### *How to fix unsupportedFeatureRepresentation*
 
@@ -489,7 +489,7 @@ The image below shows a vertical penetration area with no overlapping vertical p
 
 The following image shows a vertical penetration area that overlaps more than one vertical penetration area on an adjacent level.
 
-![Example of a vertical penetration 2](./media/drawing-conversion-error-codes/vrt.png)
+![Example of a vertical penetration 2](./media/drawing-conversion-error-codes/vrt-1.png)
 
 #### How to fix verticalPenetrationError
 

articles/azure-maps/drawing-error-visualizer.md

@@ -12,7 +12,7 @@ manager: philmea
 
 # Using the Azure Maps Drawing Error Visualizer
 
-The Drawing Error Visualizer is a stand-alone web application that displays [Drawing package warnings and errors](drawing-conversion-error-codes.md) detected during the conversion process. The Error Visualizer web application consists of a static page that you can use without connecting to the internet.  You can use the Error Visualizer to fix errors and warnings in accordance with [Drawing package requirements](drawing-requirements.md). The [Azure Maps Conversion API](https://docs.microsoft.com/rest/api/maps/data/conversion) only returns a response with a link to the Error Visualizer only when an error is detected.
+The Drawing Error Visualizer is a stand-alone web application that displays [Drawing package warnings and errors](drawing-conversion-error-codes.md) detected during the conversion process. The Error Visualizer web application consists of a static page that you can use without connecting to the internet.  You can use the Error Visualizer to fix errors and warnings in accordance with [Drawing package requirements](drawing-requirements.md). The [Azure Maps Conversion API](https://docs.microsoft.com/rest/api/maps/conversion) only returns a response with a link to the Error Visualizer only when an error is detected.
 
 ## Prerequisites
 
@@ -85,7 +85,7 @@ Once the _ConversionWarningsAndErrors.json_ file loads, you'll see a list of you
 
 ## Next steps
 
-Once your [Drawing package meets the requirements](drawing-requirements.md), you can use the [Azure Maps Dataset service](https://docs.microsoft.com/rest/api/maps/data/conversion) to convert the Drawing package to a dataset. Then, you can use the Indoor Maps web module to develop your application. Learn more by reading the following articles:
+Once your [Drawing package meets the requirements](drawing-requirements.md), you can use the [Azure Maps Dataset service](https://docs.microsoft.com/rest/api/maps/conversion) to convert the Drawing package to a dataset. Then, you can use the Indoor Maps web module to develop your application. Learn more by reading the following articles:
 
 > [!div class="nextstepaction"]
 > [Drawing Conversion error codes](drawing-conversion-error-codes.md)

articles/azure-maps/drawing-requirements.md

@@ -12,15 +12,15 @@ manager: philMea
 
 # Drawing package requirements
 
-The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) lets you convert uploaded Drawing packages into map data. This article describes the Drawing package requirements for the Conversion API. To view a sample package, you can download the sample [Drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) lets you convert uploaded Drawing packages into map data. This article describes the Drawing package requirements for the Conversion API. To view a sample package, you can download the sample [Drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
 
 ## Prerequisites
 
 The Drawing package includes drawings saved in DWG format, which is the native file format for Autodesk’s AutoCAD® software, a [trademark of Autodesk,Inc](https://www.autodesk.com/company/legal-notices-trademarks/trademarks/guidelines-for-use#section12).
 
 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 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.  
+The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/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.
 
@@ -49,7 +49,7 @@ A single DWG file is required for each level of the facility. The level's data m
 * Must not contain features from multiple levels.
 * Must not contain features from multiple facilities.
 
-The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) can extract the following feature classes from a DWG file:
+The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) can extract the following feature classes from a DWG file:
 
 * Levels
 * Units
@@ -66,11 +66,11 @@ 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.
-* Self-intersecting polygons will be automatically repaired, and the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) will raise a warning. It's recommended to manually inspect the repaired results as they may not match the expected results.
+* Self-intersecting polygons will be automatically repaired, and the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) will raise a warning. It's recommended to manually inspect the repaired results as they may not match the expected results.
 
 All layer entities must be one of the following types: Line, PolyLine, Polygon, Circular Arc, Circle, Text (single line). Any other entity types will be ignored.
 
-The table below outlines the supported entity types and supported features for each layer. If a layer contains unsupported entity types, then the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) will ignore these entities.  
+The table below outlines the supported entity types and supported features for each layer. If a layer contains unsupported entity types, then the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) will ignore these entities.  
 
 | Layer | Entity types | Features |
 | :----- | :-------------------| :-------
@@ -162,11 +162,11 @@ An example of the Zonelabel layer can be seen as the ZONELABELS layer in the [sa
 
 ## Manifest file requirements
 
-The zip folder must contain a manifest file at the root level of the directory, and the file must be named **manifest.json**. It describes the DWG files to allow the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) to parse their content. Only the files identified by the manifest will be ingested. Files that are in the zip folder, but aren't properly listed in the manifest, will be ignored.
+The zip folder must contain a manifest file at the root level of the directory, and the file must be named **manifest.json**. It describes the DWG files to allow the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) to parse their content. Only the files identified by the manifest will be ingested. Files that are in the zip folder, but aren't properly listed in the manifest, will be ignored.
 
 The file paths, in the **buildingLevels** object of the manifest file, must be relative to the root of the zip folder. The DWG file name must exactly match the name of the facility level. For example, a DWG file for the "Basement" level would be "Basement.dwg." A DWG file for level 2 would be named as "level_2.dwg." Use an underscore, if your level name has a space. 
 
-Although there are requirements when using the manifest objects, not all objects are required. The table below shows the required and the optional objects for version 1.1 of the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion).
+Although there are requirements when using the manifest objects, not all objects are required. The table below shows the required and the optional objects for version 1.1 of the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion).
 
 | Object | Required | Description |
 | :----- | :------- | :------- |
@@ -397,7 +397,7 @@ Below is a sample manifest file for the sample Drawing package. To download the
 
 ## Next steps
 
-Once your Drawing package meets the requirements, you may use the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) to convert the package to a map dataset. Then, you can use the dataset to generate an indoor map using the Indoor Maps module. Learn more about using the Indoor Maps module by reading the following articles:
+Once your Drawing package meets the requirements, you may use the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/conversion) to convert the package to a map dataset. Then, you can use the dataset to generate an indoor map using the Indoor Maps module. Learn more about using the Indoor Maps module by reading the following articles:
 
 > [!div class="nextstepaction"]
 >[Creator for indoor maps](creator-indoor-maps.md)

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

@@ -34,7 +34,7 @@ This article takes you through the steps to create and delete a Creator resource
 
 5. Review your settings and click **Create**.
 
-    ![Confirm Creator account settings page](./media/how-to-manage-creator/creator-create.PNG)
+    ![Confirm Creator account settings page](./media/how-to-manage-creator/creator-create-dialog.png)
 
 6. When the deployment completes, you'll see a page with a success or a failure message.
 

articles/azure-maps/media/drawing-conversion-error-codes/multiLine.png renamed to articles/azure-maps/media/drawing-conversion-error-codes/multi-line.png

@@ -52,7 +52,7 @@ The Data Upload API is a long running transaction that implements the pattern de
 
 4. In the **Headers** tab, specify a value for the `Content-Type` key. The Drawing package is a zipped folder, so use the `application/octet-stream` value. In the **Body** tab, select **binary**. Click on **Select File** and choose a Drawing package.
 
-     ![data-management](./media/tutorial-creator-indoor-maps/enter-content-type.png)
+     ![data-management](./media/tutorial-creator-indoor-maps/enter-content-type-dialog.png)
 
 5. Click the blue **Send** button and wait for the request to process. Once the request completes, go to the **Headers** tab of the response. Copy the value of the **Location** key, which is the `status URL`.