Skip to content

Commit ce48153

Browse files
committed
typo
1 parent 6378fae commit ce48153

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ services: azure-maps
1212

1313
# Tutorial: Use Creator to create indoor maps
1414

15-
This tutorial describes how to create indoor maps for use in Microsoft Azure Maps. In this tutorial, you'll learn how to:
15+
This tutorial describes how to create indoor maps for use in Microsoft Azure Maps. This tutorial demonstrates how to:
1616

1717
> [!div class="checklist"]
1818
>
@@ -37,7 +37,7 @@ This tutorial uses the [Postman] application, but you can use a different API de
3737
>[!IMPORTANT]
3838
>
3939
> * This article uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator services].
40-
> * In the URL examples in this article you will need to replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key.
40+
> * Replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key in the URL examples.
4141
4242
## Upload a drawing package
4343

@@ -75,7 +75,7 @@ To upload the drawing package:
7575
7676
11. Select **Select File**, and then select a drawing package.
7777
78-
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-upload-body.png" alt-text="A screenshot of Postman showing the body tab in the POST window, with Select File highlighted, this is used to select the drawing package to import into Creator.":::
78+
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-upload-body.png" alt-text="A screenshot of Postman showing the body tab in the POST window, with Select File highlighted, it's used to select the drawing package to import into Creator.":::
7979
8080
12. Select **Send**.
8181
@@ -97,7 +97,7 @@ To check the status of the drawing package and retrieve its unique ID (`udid`):
9797
9898
4. Select the **GET** HTTP method.
9999
100-
5. Enter the `status URL` you copied as the last step in the previous section of this article. The request should look like the following URL:
100+
5. Enter the `status URL` you copied as the last step in the previous section. The request should look like the following URL:
101101
102102
```http
103103
https://us.atlas.microsoft.com/mapData/operations/{operationId}?api-version=2.0&subscription-key={Your-Azure-Maps-Subscription-key}
@@ -125,7 +125,7 @@ To retrieve content metadata:
125125
126126
4. . Select the **GET** HTTP method.
127127
128-
5. Enter the `resource Location URL` you copied as the last step in the previous section of this article:
128+
5. Enter the `resource Location URL` you copied as the last step in the previous section:
129129
130130
```http
131131
https://us.atlas.microsoft.com/mapData/metadata/{udid}?api-version=2.0&subscription-key={Your-Azure-Maps-Subscription-key}
@@ -148,7 +148,7 @@ To retrieve content metadata:
148148
149149
## Convert a drawing package
150150
151-
Now that the drawing package is uploaded, you'll use the `udid` for the uploaded package to convert the package into map data. The [Conversion API] uses a long-running transaction that implements the pattern defined in the [Creator Long-Running Operation] article.
151+
Now that the drawing package is uploaded, you use the `udid` for the uploaded package to convert the package into map data. The [Conversion API] uses a long-running transaction that implements the pattern defined in the [Creator Long-Running Operation] article.
152152
153153
To convert a drawing package:
154154
@@ -170,7 +170,7 @@ To convert a drawing package:
170170
171171
7. In the response window, select the **Headers** tab.
172172
173-
8. Copy the value of the **Operation-Location** key. This is the `status URL` that you'll use to check the status of the conversion.
173+
8. Copy the value of the **Operation-Location** key, it contains the `status URL` that you use to check the status of the conversion.
174174
175175
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-convert-location-url.png" border="true" alt-text="A screenshot of Postman showing the URL value of the operation location key in the responses header.":::
176176
@@ -198,7 +198,7 @@ To check the status of the conversion process and retrieve the `conversionId`:
198198
199199
7. In the response window, select the **Headers** tab.
200200
201-
8. Copy the value of the **Resource-Location** key, which is the `resource location URL`. The `resource location URL` contains the unique identifier (`conversionId`), which can be used by other APIs to access the converted map data.
201+
8. Copy the value of the **Resource-Location** key, which is the `resource location URL`. The `resource location URL` contains the unique identifier (`conversionId`), which is used by other APIs to access the converted map data.
202202
203203
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-conversion-id.png" alt-text="A screenshot of Postman highlighting the conversion ID value that appears in the resource location key in the responses header.":::
204204
@@ -255,7 +255,7 @@ To create a dataset:
255255
256256
7. In the response window, select the **Headers** tab.
257257
258-
8. Copy the value of the **Operation-Location** key. This is the `status URL` that you'll use to check the status of the dataset.
258+
8. Copy the value of the **Operation-Location** key, it contains the `status URL` that you use to check the status of the dataset.
259259
260260
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-dataset-location-url.png" border="true" alt-text="A screenshot of Postman showing the value of the operation location key for dataset in the responses header.":::
261261
@@ -299,7 +299,7 @@ To create a tileset:
299299
300300
4. Select the **POST** HTTP method.
301301
302-
5. Enter the following URL to the [Tileset service]. The request should look like the following URL (replace `{datasetId`} with the `datasetId` obtained in the [Check the dataset creation status](#check-the-dataset-creation-status) section above:
302+
5. Enter the following URL to the [Tileset service]. The request should look like the following URL (replace `{datasetId`} with the `datasetId` obtained in the [Check the dataset creation status](#check-the-dataset-creation-status) section:
303303
304304
```http
305305
https://us.atlas.microsoft.com/tilesets?api-version=2023-03-01-preview&datasetID={datasetId}&subscription-key={Your-Azure-Maps-Primary-Subscription-key}
@@ -309,7 +309,7 @@ To create a tileset:
309309
310310
7. In the response window, select the **Headers** tab.
311311
312-
8. Copy the value of the **Operation-Location** key, this is the `status URL`, which you'll use to check the status of the tileset.
312+
8. Copy the value of the **Operation-Location** key, it contains the `status URL`, which you use to check the status of the tileset.
313313
314314
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-tileset-location-url.png" border="true" alt-text="A screenshot of Postman highlighting the status URL that is the value of the operation location key in the responses header.":::
315315
@@ -357,7 +357,7 @@ Once your tileset creation completes, you can get the `mapConfigurationId` using
357357
358358
6. Select **Send**.
359359
360-
7. The tileset JSON will appear in the body of the response, scroll down to see the `mapConfigurationId`:
360+
7. The tileset JSON appears in the body of the response, scroll down to see the `mapConfigurationId`:
361361
362362
```json
363363
"defaultMapConfigurationId": "5906cd57-2dba-389b-3313-ce6b549d4396"

0 commit comments

Comments
 (0)