'Service' as part of the link.

stevemunk · stevemunk · commit e715ae1cee14 · 2023-09-25T15:45:54.000-05:00
diff --git a/articles/azure-maps/about-azure-maps.md b/articles/azure-maps/about-azure-maps.md
@@ -53,23 +53,23 @@ Azure Maps consists of the following services that can provide geographic contex
 
 ### Data registry service
 
-Data is imperative for maps. Use the Data registry service to access geospatial data, used with spatial operations or image composition, previously uploaded to your [Azure Storage].  By bringing customer data closer to the Azure Maps service, you reduce latency and increase productivity. For more information on this service, see [Data registry service].
+Data is imperative for maps. Use the Data registry service to access geospatial data, used with spatial operations or image composition, previously uploaded to your [Azure Storage].  By bringing customer data closer to the Azure Maps service, you reduce latency and increase productivity. For more information, see [Data registry] in the Azure Maps REST API documentation.
 
 > [!NOTE]
 >
 > **Azure Maps Data service retirement**
 >
-> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data Registry service] by 9/16/24. For more information, see [How to create data registry].
+> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data registry] service by 9/16/24. For more information, see [How to create data registry].
 
 ### Geolocation service
 
 Use the Geolocation service to retrieve the two-letter country/region code for an IP address. This service can help you enhance user experience by providing customized application content based on geographic location.
 
-For more information, see the [Geolocation service] documentation.
+For more information, see [Geolocation] in the Azure Maps REST API documentation.
 
 ### Render service
 
-[Render service] introduces a new version of the [Get Map Tile] API that supports using Azure Maps tiles not only in the Azure Maps SDKs but other map controls as well. It includes raster and vector tile formats, 256x256 or 512x512 tile sizes (where applicable) and numerous map types such as road, weather, contour, or map tiles. For a complete list, see [TilesetID] in the REST API documentation. You're required to display the appropriate copyright attribution on the map anytime you use the Azure Maps Render service, either as basemaps or layers, in any third-party map control. For more information, see [How to use the Get Map Attribution API].
+[Render] service introduces a new version of the [Get Map Tile] API that supports using Azure Maps tiles not only in the Azure Maps SDKs but other map controls as well. It includes raster and vector tile formats, 256x256 or 512x512 tile sizes (where applicable) and numerous map types such as road, weather, contour, or map tiles. For a complete list, see [TilesetID] in the REST API documentation. You're required to display the appropriate copyright attribution on the map anytime you use the Azure Maps Render service, either as basemaps or layers, in any third-party map control. For more information, see [How to use the Get Map Attribution API].
 
 :::image type="content" source="./media/about-azure-maps/intro_map.png" border="false" alt-text="Example of a map from the Render service":::
 
@@ -91,7 +91,7 @@ The Route service offers advanced set features, such as:
 * Matrices of travel time and distance between a set of origins and destinations.
 * Finding routes or distances that users can travel based on time or fuel requirements.
 
-For more information on routing capabilities, see the [Route service] documentation.
+For more information, see [Route] in the Azure Maps REST API documentation.
 
 ### Search service
 
@@ -106,13 +106,13 @@ The Search service also provides advanced features such as:
 * Batch a group of search requests.
 * Search electric vehicle charging stations and Point of Interest (POI) data by brand name.
 
-For more information on search capabilities, see the [Search service] documentation.
+For more information, see [Search] in the Azure Maps REST API documentation.
 
 ### Spatial service
 
 The Spatial service quickly analyzes location information to help inform customers of ongoing events happening in time and space. It enables near real-time analysis and predictive modeling of events.
 
-The service enables customers to enhance their location intelligence with a library of common geospatial mathematical calculations. Common calculations include closest point, great circle distance, and buffers. For more information about the Spatial service and its various features, see the [Spatial service] documentation.
+The service enables customers to enhance their location intelligence with a library of common geospatial mathematical calculations. Common calculations include closest point, great circle distance, and buffers. For more information about the Spatial service and its various features, see [Spatial] in the Azure Maps REST API documentation.
 
 ### Timezone service
 
@@ -150,7 +150,7 @@ A typical JSON response for a query to the Time zone service looks like the foll
 }
 ```
 
-For more information, see the [Time zone service] documentation.
+For more information, see [Timezone] in the Azure Maps REST API documentation.
 
 ### Traffic service
 
@@ -161,7 +161,7 @@ The Traffic service is a suite of web services that developers can use for web o
 
 ![Example of a map with traffic information](media/about-azure-maps/intro_traffic.png)
 
-For more information, see the [Traffic service] documentation.
+For more information, see [Traffic] in the Azure Maps REST API documentation.
 
 ### Weather service
 
@@ -229,21 +229,20 @@ Stay up to date on Azure Maps:
 [What is Azure Maps Creator?]: about-creator.md
 [v1]: /rest/api/maps/data
 [v2]: /rest/api/maps/data-v2
-[Data Registry service]: /rest/api/maps/data-registry
 [How to create data registry]: how-to-create-data-registries.md
 <!---------   REST API Links     --------------->
-[Data registry service]: /rest/api/maps/data-registry
-[Geolocation service]: /rest/api/maps/geolocation
+[Data registry]: /rest/api/maps/data-registry
+[Geolocation]: /rest/api/maps/geolocation
 [Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
 [Get Weather along route API]: /rest/api/maps/weather/getweatheralongroute
-[Render service]: /rest/api/maps/render-v2
+[Render]: /rest/api/maps/render-v2
 [REST APIs]: /rest/api/maps/
-[Route service]: /rest/api/maps/route
-[Search service]: /rest/api/maps/search
-[Spatial service]: /rest/api/maps/spatial
+[Route]: /rest/api/maps/route
+[Search]: /rest/api/maps/search
+[Spatial]: /rest/api/maps/spatial
 [TilesetID]: /rest/api/maps/render-v2/get-map-tile#tilesetid
-[Time zone service]: /rest/api/maps/timezone
-[Traffic service]: /rest/api/maps/traffic
+[Timezone]: /rest/api/maps/timezone
+[Traffic]: /rest/api/maps/traffic
 <!---------   JavaScript API Links     --------------->
 [JavaScript map control]: /javascript/api/azure-maps-control
 <!---------   External Links     --------------->
diff --git a/articles/azure-maps/about-creator.md b/articles/azure-maps/about-creator.md
@@ -24,7 +24,7 @@ Creator is a platform for building indoor mapping solutions for all your needs.
 
 An [onboarding tool] is provided to prepare your facility's DWGs by identifying the data to use and to positioning your facility on the map. The conversion service then converts the geometry and data from your DWG files into a digital indoor map.
 
-The first step in creating your indoor map is to upload a drawing package into your Azure Maps account. A drawing package contains one or more CAD (computer-aided design) drawings of your facility along with a manifest describing the drawings. The drawings define the elements of the facility while the manifest tells the Azure Maps [Conversion service] how to read the facility drawing files and metadata. For more
+The first step in creating your indoor map is to upload a drawing package into your Azure Maps account. A drawing package contains one or more CAD (computer-aided design) drawings of your facility along with a manifest describing the drawings. The drawings define the elements of the facility while the manifest tells the Azure Maps [Conversion] service how to read the facility drawing files and metadata. For more
 information about manifest properties, see [Manifest file requirements] and for more information on creating and uploading a drawing package, see the [Drawing package guide].
 
 ### Dataset
@@ -60,7 +60,7 @@ This section provides a high-level overview of the indoor map creation workflow.
     account. Upload drawing packages using the [Data Upload API].
 
 1. **Convert**. Once the drawing package is uploaded into your Azure Maps account,
-    use the [Conversion service] to validate the data in the uploaded drawing
+    use the [Conversion] service to validate the data in the uploaded drawing
     package and convert it into map data.
 
 1. **Dataset**. Create a [dataset] from the map data. A dataset is collection
@@ -110,7 +110,7 @@ This section provides a high-level overview of the indoor map creation workflow.
 
 [Azure Maps Creator onboarding tool]: https://azure.github.io/azure-maps-creator-onboarding-tool
 [Azure Maps Creator REST API]: /rest/api/maps-creator
-[Conversion service]: /rest/api/maps/v2/conversion
+[Conversion]: /rest/api/maps/v2/conversion
 [Create a feature stateset]: how-to-creator-feature-stateset.md
 [Create custom styles for indoor maps]: how-to-create-custom-styles.md
 [Create dataset using GeoJson package]: how-to-dataset-geojson.md
diff --git a/articles/azure-maps/azure-maps-qps-rate-limits.md b/articles/azure-maps/azure-maps-qps-rate-limits.md
@@ -44,13 +44,13 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
 | Traffic service | 50 | 50 | 50 |
 | Weather service | 50 | 50 | 50 |
 
-<sup>1</sup> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data Registry service] by 9/16/24. For more information, see [How to create data registry].
+<sup>1</sup> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data Registry] service by 9/16/24. For more information, see [How to create data registry].
 
 When QPS limits are reached, an HTTP 429 error is returned. If you're using the Gen 2 or Gen 1 S1 pricing tiers, you can create an Azure Maps *Technical* Support Request in the [Azure portal] to increase a specific QPS limit if needed. QPS limits for the Gen 1 S0 pricing tier can't be increased.
 
 [Azure portal]: https://portal.azure.com/
 [Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md
 [v1]: /rest/api/maps/data
 [v2]: /rest/api/maps/data-v2
-[Data Registry service]: /rest/api/maps/data-registry
+[Data Registry]: /rest/api/maps/data-registry
 [How to create data registry]: how-to-create-data-registries.md
diff --git a/articles/azure-maps/how-to-search-for-address.md b/articles/azure-maps/how-to-search-for-address.md
@@ -12,7 +12,7 @@ services: azure-maps
 
 # Search for a location using Azure Maps Search services
 
-The [Search service] is a set of RESTful APIs designed to help developers search addresses, places, and business listings by name, category, and other geographic information. In addition to supporting traditional geocoding, services can also reverse geocode addresses and cross streets based on latitudes and longitudes. Latitude and longitude values returned by the search can be used as parameters in other Azure Maps services, such as [Route] and [Weather] services.
+The [Search] service is a set of RESTful APIs designed to help developers search addresses, places, and business listings by name, category, and other geographic information. In addition to supporting traditional geocoding, services can also reverse geocode addresses and cross streets based on latitudes and longitudes. Latitude and longitude values returned by the search can be used as parameters in other Azure Maps services, such as [Route] and [Weather].
 
 This article demonstrates how to:
 
@@ -193,7 +193,7 @@ This example demonstrates how to search for a cross street based on the coordina
 [Search Address]: /rest/api/maps/search/getsearchaddress
 [Search Coverage]: geocoding-coverage.md
 [Search Polygon API]: /rest/api/maps/search/getsearchpolygon
-[Search service]: /rest/api/maps/search
+[Search]: /rest/api/maps/search
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [URI Parameter reference]: /rest/api/maps/search/getsearchfuzzy#uri-parameters
 [Weather]: /rest/api/maps/weather
diff --git a/articles/azure-maps/understanding-azure-maps-transactions.md b/articles/azure-maps/understanding-azure-maps-transactions.md
@@ -37,7 +37,7 @@ The following table summarizes the Azure Maps services that generate transaction
 | [Traffic] | Yes | One request = 1 transaction (except tiles)<br>15 tiles = 1 transaction | <ul><li>Location Insights Traffic (Gen2 pricing)</li><li>Standard S1 Traffic Transactions (Gen1 S1 pricing)</li><li>Standard Geolocation Transactions (Gen1 S0 pricing)</li><li>Maps Traffic Tiles (Gen2 pricing)</li><li>Standard S1 Tile Transactions (Gen1 S1 pricing)</li><li>Standard Tile Transactions (Gen1 S0 pricing)</li></ul> |
 | [Weather] | Yes | One request = 1 transaction | <ul><li>Location Insights Weather (Gen2 pricing)</li><li>Standard S1 Weather Transactions (Gen1 S1 pricing)</li><li>Standard Weather Transactions (Gen1 S0 pricing)</li></ul> |
 
-<sup>1</sup> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data Registry service] by 9/16/24. For more information, see [How to create data registry].
+<sup>1</sup> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data Registry] service by 9/16/24. For more information, see [How to create data registry].
 
 <!-- In Bing Maps, any time a synchronous Truck Routing request is made, three transactions are counted. Does this apply also to Azure Maps?-->
 
@@ -85,7 +85,6 @@ The following table summarizes the Azure Maps services that generate transaction
 [Data registry]: /rest/api/maps/data-registry
 [v1]: /rest/api/maps/data
 [v2]: /rest/api/maps/data-v2
-[Data Registry service]: /rest/api/maps/data-registry
 [How to create data registry]: how-to-create-data-registries.md
 [Dataset]: /rest/api/maps/v2/dataset
 [Feature State]: /rest/api/maps/v2/feature-state
