additional fixes to links

Author: stevemunk

articles/azure-maps/drawing-requirements.md

@@ -13,9 +13,9 @@ services: azure-maps
 
 # Drawing package requirements
 
-You can convert uploaded drawing packages into map data by using the Azure Maps [Conversion service]. 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).
+You can convert uploaded drawing packages into map data by using the Azure Maps [Conversion service]. This article describes the drawing package requirements for the Conversion API. To view a sample package, you can download the sample [Drawing package].
 
-For a guide on how to prepare your drawing package, see [Conversion Drawing Package Guide](drawing-package-guide.md).
+For a guide on how to prepare your drawing package, see [Conversion Drawing Package Guide].
 
 ## Prerequisites
 
@@ -45,7 +45,7 @@ A drawing package is a .zip archive that contains the following files:
 - DWG files in AutoCAD DWG file format.
 - A _manifest.json_ file that describes the DWG files in the drawing package.
 
-The drawing package must be zipped into a single archive file, with the .zip extension. The DWG files can be organized in any way inside the package, but the manifest file must live at the root directory of the zipped package. The next sections detail the requirements for the DWG files, manifest file, and the content of these files. To view a sample package, you can download the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+The drawing package must be zipped into a single archive file, with the .zip extension. The DWG files can be organized in any way inside the package, but the manifest file must live at the root directory of the zipped package. The next sections detail the requirements for the DWG files, manifest file, and the content of these files. To view a sample package, you can download the [sample drawing package].
 
 ## DWG file conversion process
 
@@ -114,7 +114,7 @@ No matter how many entity drawings are in the exterior layer, the [resulting fac
 
 If the layer contains multiple overlapping PolyLines, the PolyLines are dissolved into a single Level feature. Instead, if the layer contains multiple non-overlapping PolyLines, the resulting Level feature has a multi-polygonal representation.
 
-You can see an example of the Exterior layer as the outline layer in the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+You can see an example of the Exterior layer as the outline layer in the [sample drawing package].
 
 ### Unit layer
 
@@ -129,7 +129,7 @@ The Units layer should adhere to the following requirements:
 
 Name a unit by creating a text object in the UnitLabel layer, and then place the object inside the bounds of the unit. For more information, see the [UnitLabel layer](#unitlabel-layer).
 
-You can see an example of the Units layer in the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+You can see an example of the Units layer in the [sample drawing package].
 
 ### Wall layer
 
@@ -138,7 +138,7 @@ The DWG file for each level can contain a layer that defines the physical extent
 - Walls must be drawn as Polygon, PolyLine (closed), Circle, or Ellipse (closed).
 - The wall layer or layers should only contain geometry that's interpreted as building structure.
 
-You can see an example of the Walls layer in the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+You can see an example of the Walls layer in the [sample drawing package].
 
 ### Door layer
 
@@ -158,7 +158,7 @@ The DWG file for each level can contain a Zone layer that defines the physical e
 
 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).
 
-You can see an example of the Zone layer in the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+You can see an example of the Zone layer in the [sample drawing package].
 
 ### UnitLabel layer
 
@@ -168,7 +168,7 @@ The DWG file for each level can contain a UnitLabel layer. The UnitLabel layer a
 - Unit labels must fall entirely inside the bounds of their unit.
 - Units must not contain multiple text entities in the UnitLabel layer.
 
-You can see an example of the UnitLabel layer in the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+You can see an example of the UnitLabel layer in the [sample drawing package].
 
 ### ZoneLabel layer
 
@@ -178,7 +178,7 @@ The DWG file for each level can contain a ZoneLabel layer. This layer adds a nam
 - Zones labels must fall inside the bounds of their zone.
 - Zones must not contain multiple text entities in the ZoneLabel layer.
 
-You can see an example of the ZoneLabel layer in the [sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
+You can see an example of the ZoneLabel layer in the [sample drawing package].
 
 ## Manifest file requirements
 
@@ -213,7 +213,7 @@ The next sections detail the requirements for each object.
 |`locality` |string | false   | Name of a city, town, area, neighborhood, or region.|
 |`adminDivisions`|JSON array of strings | false| An array containing address designations. For example: (Country, State) Use ISO 3166 country codes and ISO 3166-2 state/territory codes. |
 |`postalCode`|string| false   | The mail sorting code. |
-|`hoursOfOperation` |string|false| Adheres to the [OSM Opening Hours](https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification) format. |
+|`hoursOfOperation` |string|false| Adheres to the [OSM Opening Hours] format. |
 |`phone`    |string| false   |    Phone number associated with the building. |
 |`website`  |string| false   | Website associated with the building. |
 |`nonPublic`|bool| false     | Flag specifying if the building is open to the public. |
@@ -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](https://github.com/Azure-Samples/am-creator-indoor-data-examples) on GitHub to download the entire package.
+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.
 
 #### Manifest file
 
@@ -425,4 +425,8 @@ Learn more by reading:
 > [!div class="nextstepaction"]
 > [Creator for indoor maps](creator-indoor-maps.md)
 
-[Conversion service]: /rest/api/maps/v2/conversion
+[Conversion service]: /rest/api/maps/v2/conversion
+[Drawing package]: https://github.com/Azure-Samples/am-creator-indoor-data-examples
+[Conversion Drawing Package Guide]: drawing-package-guide.md
+[sample drawing package]: https://github.com/Azure-Samples/am-creator-indoor-data-examples
+[OSM Opening Hours]: https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification

articles/azure-maps/geofence-geojson.md

@@ -33,7 +33,7 @@ The data for geofence or set of geofences is represented by `Feature` Object and
 
 * All coordinate values are represented as [longitude, latitude] defined in `WGS84`.
 * For each Feature, which contains `MultiPoint`, `MultiLineString`, `MultiPolygon` , or `GeometryCollection`, the properties are applied to all the elements. for example: All the points in `MultiPoint` will use same radius to form a multiple circle geofence.
-* In point-circle scenario, a circle geometry can be represented using a `Point` geometry object with properties elaborated in [Extending GeoJSON geometries](./extend-geojson.md).
+* In point-circle scenario, a circle geometry can be represented using a `Point` geometry object with properties elaborated in [Extending GeoJSON geometries].
 
 Following is a sample request body for a geofence represented as a circle geofence geometry in `GeoJSON` using a center point and a radius. The valid period of the geofence data starts from 2018-10-22, 9AM to 5PM, repeated every day except for the weekend. `expiredTime` indicates this geofence data will be considered expired, if `userTime` in the request is later than `2019-01-01`.  
 
@@ -67,4 +67,5 @@ Following is a sample request body for a geofence represented as a circle geofen
 
 [GET Geofence]: /rest/api/maps/spatial/getgeofence
 [POST Geofence]: /rest/api/maps/spatial/postgeofence
-[rfc7946]: https://tools.ietf.org/html/rfc7946
+[rfc7946]: https://tools.ietf.org/html/rfc7946
+[Extending GeoJSON geometries]: extend-geojson.md

articles/azure-maps/how-to-create-custom-styles.md

@@ -44,7 +44,7 @@ Select the **Get map configuration list** button to get a list of every map conf
 :::image type="content" source="./media/creator-indoor-maps/style-editor/select-the-map-configuration.png" alt-text="A screenshot of the open style dialog box in the visual style editor with the Select map configuration drop-down list highlighted.":::
 
 > [!NOTE]
-> If the map configuration was created as part of a custom style and has a user provided alias, that alias will appear in the map configuration drop-down list, otherwise the `mapConfigurationId` will appear. The default map configuration ID for any given tileset can be found by using the [tileset get][tileset get] HTTP request and passing in the tileset ID:
+> If the map configuration was created as part of a custom style and has a user provided alias, that alias will appear in the map configuration drop-down list, otherwise the `mapConfigurationId` will appear. The default map configuration ID for any given tileset can be found by using the [tileset get] HTTP request and passing in the tileset ID:
 >
 > ```http
 > https://{geography}.atlas.microsoft.com/tilesets/{tilesetId}?2022-09-01-preview

articles/azure-maps/how-to-create-data-registries.md

@@ -317,7 +317,7 @@ The data returned when running the list request is similar to the data provided
 
 ## Get content from a data registry
 
-Once you've uploaded one or more files to an Azure storage account, created and Azure Maps datastore to link to those files, then registered them using the [register][register or replace] API, you can access the data contained in the files.
+Once you've uploaded one or more files to an Azure storage account, created and Azure Maps datastore to link to those files, then registered them using the [register] API, you can access the data contained in the files.
 
 Use the `udid` to get the content of a file registered in an Azure Maps account:
 
@@ -363,7 +363,7 @@ When you register a file in Azure Maps using the data registry API, an MD5 hash
 
 [data registry]: /rest/api/maps/data-registry
 [list]: /rest/api/maps/data-registry/list
-[Register Or Replace]: /rest/api/maps/data-registry/register-or-replace
+[Register]: /rest/api/maps/data-registry/register-or-replace
 [Get operation]: /rest/api/maps/data-registry/get-operation
 
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account

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

@@ -16,8 +16,8 @@ The Azure Maps Creator [wayfinding service] allows you to navigate from place to
 
 ## Prerequisites
 
-- Understanding of [Creator concepts](creator-indoor-maps.md).
-- An Azure Maps Creator [dataset] and [tileset]. If you have never used Azure Maps Creator to create an indoor map, you might find the [Use Creator to create indoor maps](tutorial-creator-indoor-maps.md) tutorial helpful.
+- Understanding of [Creator concepts].
+- An Azure Maps Creator [dataset] and [tileset]. If you have never used Azure Maps Creator to create an indoor map, you might find the [Use Creator to create indoor maps] tutorial helpful.
 
 >[!IMPORTANT]
 >
@@ -122,6 +122,7 @@ The wayfinding service calculates the path through specific intervening points.
 
 <!-- TODO: ## Implement the wayfinding service in your map   (Refer to sample app once completed)  -->
 
+[Creator concepts]: creator-indoor-maps.md
 [dataset]: creator-indoor-maps.md#datasets
 [tileset]: creator-indoor-maps.md#tilesets
 [routeset]: /rest/api/maps/v20220901preview/routeset
@@ -130,3 +131,4 @@ The wayfinding service calculates the path through specific intervening points.
 [Access to Creator services]: how-to-manage-creator.md#access-to-creator-services
 [Check the dataset creation status]: tutorial-creator-indoor-maps.md#check-the-dataset-creation-status
 [wayfinding service]: creator-indoor-maps.md#wayfinding-preview
+[Use Creator to create indoor maps]: tutorial-creator-indoor-maps.md