Merge pull request #298292 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-maps/creator-long-running-operation-v2.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Maps long-running operation API V2
-description: Learn about long-running asynchronous V2 background processing in Azure Maps
+title: Azure Maps long-running operation API v2
+description: Learn about long-running asynchronous v2 background processing in Azure Maps
 author: faterceros
 ms.author: aterceros
 ms.date: 09/16/2024
@@ -10,7 +10,7 @@ ms.subservice: creator
 ms.custom: mvc
 ---
 
-# Creator Long-Running Operation API V2
+# Creator Long-Running Operation API v2
 
 > [!NOTE]
 >

articles/azure-maps/how-to-dev-guide-csharp-sdk.md

@@ -299,7 +299,7 @@ for (var i = 0; i < count; i++)
 }
 ```
 
-## Using V1 SDKs for Search and Render
+## Using v1 SDKs for Search and Render
 
 For more information on using Search v1, see [Azure Maps Search client library for .NET](https://www.nuget.org/packages/Azure.Maps.Search/1.0.0-beta.5). For more information on using Render v1, see [Azure Maps Render client library for .NET](https://www.nuget.org/packages/Azure.Maps.Rendering/1.0.0-beta.3).
 

articles/azure-maps/how-to-dev-guide-js-sdk.md

@@ -345,9 +345,9 @@ main().catch(console.error);
 
 ```
 
-## Use V1 SDK
+## Use v1 SDK
 
-We are working to make all V1 features available in V2, until then, install the following V1 SDK packages if needed:
+We are working to make all v1 features available in v2, until then, install the following v1 SDK packages if needed:
 
 ```bash
 npm install @azure-rest/map-search-v1@npm:@azure-rest/map-search@^1.0.0
@@ -361,7 +361,7 @@ const MapsSearchV1 = require("@azure-rest/map-search-v1").default;
 const MapsSearchV2 = require("@azure-rest/map-search-v2").default;
 ```
 
-The following example demonstrates creating a function that accepts an address and search POIs around it. Use V2 SDK to get the coordinates of the address(/geocode) and V1 SDK to search POIs around it(/search/nearby).
+The following example demonstrates creating a function that accepts an address and search POIs around it. Use v2 SDK to get the coordinates of the address(/geocode) and v1 SDK to search POIs around it(/search/nearby).
 
 ```javascript
 const MapsSearchV1 = require("@azure-rest/map-search-v1").default;

articles/azure-maps/how-to-dev-guide-py-sdk.md

@@ -354,9 +354,9 @@ if __name__ == '__main__':
 ```
 
 
-## Using V1 SDKs for Search and Render
+## Using v1 SDKs for Search and Render
 
-To use Search V1 and Render V1 SDK, please refer to Search V1 SDK [package](https://pypi.org/project/azure-maps-search/1.0.0b2/) page and Render V1 SDK [package](https://pypi.org/project/azure-maps-render/1.0.0b2/) for more information.
+To use Search v1 and Render v1 SDK, please refer to Search v1 SDK [package](https://pypi.org/project/azure-maps-search/1.0.0b2/) page and Render v1 SDK [package](https://pypi.org/project/azure-maps-render/1.0.0b2/) for more information.
 
 
 ## Additional information

articles/azure-maps/migrate-from-google-maps-web-app.md

@@ -11,7 +11,7 @@ ms.subservice: web-sdk
 
 # Tutorial: Migrate a web app from Google Maps
 
-Most web apps, which use Google Maps, are using the Google Maps V3 JavaScript SDK. The Azure Maps Web SDK is the suitable Azure-based SDK to migrate to. The Azure Maps Web SDK lets you customize interactive maps with your own content and imagery. You can run your app on both web or mobile applications. This control makes use of WebGL, allowing you to render large data sets with high performance. Develop with this SDK using JavaScript or TypeScript. This tutorial demonstrates:
+Most web apps, which use Google Maps, are using the Google Maps v3 JavaScript SDK. The Azure Maps Web SDK is the suitable Azure-based SDK to migrate to. The Azure Maps Web SDK lets you customize interactive maps with your own content and imagery. You can run your app on both web or mobile applications. This control makes use of WebGL, allowing you to render large data sets with high performance. Develop with this SDK using JavaScript or TypeScript. This tutorial demonstrates:
 
 > [!div class="checklist"]
 > * Load a map
@@ -56,7 +56,7 @@ If you don't have an Azure subscription, create a [free account] before you begi
 
 ## Key features support
 
-The table lists key API features in the Google Maps V3 JavaScript SDK and the supported API feature in the Azure Maps Web SDK.
+The table lists key API features in the Google Maps v3 JavaScript SDK and the supported API feature in the Azure Maps Web SDK.
 
 | Google Maps feature     | Azure Maps Web SDK support |
 |-------------------------|:--------------------------:|
@@ -89,7 +89,7 @@ The following are some key differences between the Google Maps and Azure Maps We
 
 ## Web SDK side-by-side examples
 
-This collection has code samples for each platform, and each sample covers a common use case. It's intended to help you migrate your web application from Google Maps V3 JavaScript SDK to the Azure Maps Web SDK. Code samples related to web applications are provided in JavaScript. However, Azure Maps also provides TypeScript definitions as another option through an [npm module].
+This collection has code samples for each platform, and each sample covers a common use case. It's intended to help you migrate your web application from Google Maps v3 JavaScript SDK to the Azure Maps Web SDK. Code samples related to web applications are provided in JavaScript. However, Azure Maps also provides TypeScript definitions as another option through an [npm module].
 
 **Topics**
 
@@ -286,7 +286,7 @@ Here's an example of Azure Maps with the language set to "fr" and the user regio
 Dynamic maps in both Azure and Google Maps can be programmatically moved to new geographic locations. To do so, call the appropriate functions in JavaScript. The examples show how to make the map display satellite aerial imagery, center the map over a location, and change the zoom level to 15 in Google Maps. The following location coordinates are used: longitude: -111.0225 and latitude: 35.0272.
 
 > [!NOTE]
-> Google Maps uses tiles that are 256 pixels in dimensions, while Azure Maps uses a larger 512-pixel tile. Thus, Azure Maps requires less number of network requests to load the same map area as Google Maps. Due to the way tile pyramids work in map controls, you need to subtract the zoom level used in Google Maps by the number one when using Azure Maps. This arithmetic operation ensures that larger tiles in Azure Maps render that same map area as in Google Maps,
+> Google Maps uses 256-pixel tiles, whereas Azure Maps uses larger 512-pixel tiles. Consequently, Azure Maps requires fewer network requests to load the same map area as Google Maps. Due to the tile pyramid structure in map controls, you need to subtract one from the zoom level used in Google Maps when using Azure Maps. This adjustment ensures that the larger tiles that Azure Maps renders will use the same map area as used in Google Maps.
 
 #### Before: Google Maps
 
@@ -1692,9 +1692,9 @@ The following are some more code samples related to Google Maps migration:
 * [Show directions from A to B]
 * [Search Autosuggest with jQuery UI]
 
-## Google Maps V3 to Azure Maps Web SDK class mapping
+## Google Maps v3 to Azure Maps Web SDK class mapping
 
-The following appendix provides a cross reference of the commonly used classes in Google Maps V3 and the equivalent Azure Maps Web SDK.
+The following appendix provides a cross reference of the commonly used classes in Google Maps v3 and the equivalent Azure Maps Web SDK.
 
 ### Core Classes
 

articles/azure-maps/migrate-route-v1-api.md

@@ -56,7 +56,7 @@ This article explains how to migrate the [Azure Maps Route v1.0] APIs to [Azure
 
 ### Route Range notable differences
 
-| Feature           | V1.0      | V2025-01-01                                               |
+| Feature           | v1.0      | v2025-01-01                                               |
 |-------------------|-----------|-----------------------------------------------------------|
 | Coordinate format | Latitude/Longitude | Longitude/latitude, as defined by [GeoJSON].     |
 | Electric consumption model | Supported | Not Supported                                    |

articles/azure-maps/release-notes-map-control.md

@@ -137,7 +137,7 @@ This document contains information about new features and other changes to the M
 
 #### Other changes
 
-- The accessibility feature for screen reader has been upgraded to utilize the Search V2 API (reverse geocoding).
+- The accessibility feature for screen reader has been upgraded to utilize the Search v2 API (reverse geocoding).
 
 - Enhanced accessibility in the Compass and Pitch controls.
 
@@ -513,7 +513,7 @@ This update is the first preview of the upcoming 3.0.0 release. The underlying [
 
 #### Other changes
 
-- The accessibility feature for screen reader has been upgraded to utilize the Search V2 API (reverse geocoding).
+- The accessibility feature for screen reader has been upgraded to utilize the Search v2 API (reverse geocoding).
 
 ### [2.3.4] (November 1, 2023)
 

articles/azure-maps/rest-api-creator.md

@@ -52,7 +52,7 @@ Pre-release version of a Creator service. Preview releases contain new functiona
 | [Tileset][Tileset-preview] | 2023-03-01-preview | A collection of vector tiles that render on the map, created from an existing dataset. |
 | [Wayfinding] | 2023-03-01-preview | Wayfinding is a technology that helps people navigate through complex indoor environments such as malls, offices, stadiums, airports and office buildings. |
 
-<!--- V2 is the latest stable release of each Creator service --->
+<!--- v2 is the latest stable release of each Creator service --->
 
 [Alias]: /rest/api/maps-creator/alias
 [Conversion]: /rest/api/maps-creator/conversion

articles/azure-resource-manager/management/tag-support.md

@@ -2367,8 +2367,6 @@ To get the same data as a file of comma-separated values, download [tag-support.
 <a id="network-limitations"></a>
 
 > [!NOTE]
-> For Azure Front Door Service, you can apply tags when creating the resource, but updating or adding tags is not currently supported. Front Door doesn't support the use of # or : in the tag name.
-> 
 > Azure DNS zones and Traffic Manager doesn't support the use of spaces in the tag or a tag that starts with a number. Azure DNS and Traffic Manager tag names do not support special and unicode characters. The value can contain all characters.
 > 
 > Azure IP Groups and Azure Firewall Policies don't support PATCH operations, which means they don't support updating tags through the portal. Instead, use the update commands for those resources. For example, you can update tags for an IP group with the [az network ip-group update](/cli/azure/network/ip-group#az-network-ip-group-update) command.

articles/logic-apps/logic-apps-workflow-actions-triggers.md

@@ -1717,7 +1717,7 @@ This action stops the run for a workflow instance, cancels any actions in progre
 
 *Optional*
 
-The properties for the "runStatus" object apply only 
+The properties for the "runError" object apply only 
 when the "runStatus" property is set to "Failed" status.
 
 | Value | Type | Description |