Merge pull request #299126 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/rest-api-azure-maps.md

@@ -42,7 +42,7 @@ There are previous stable releases of an Azure Maps service that are still in us
 | [Render][render-2022-08-01] |  2022-08-01  | Get road, satellite/aerial, weather, traffic map tiles, and static map images. |
 | [Route][Route v1] |  1.0  | Calculate optimized travel times and distances between locations for multiple modes of transportation and get localized travel instructions. |
 | [Search][Search v1] |  1.0  | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons. This is version 1.0 of the Search service. For the latest version, see [Search]. |
-| [Search] |  2023-06-01  | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons. |
+| Search |  2023-06-01  | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons.  For the latest version, see [Search].|
 | [Traffic][Traffic v1] |  1.0  | Get current traffic information including traffic flow and traffic incident details. |
 
 ## Latest preview

articles/operator-service-manager/get-started-with-cluster-registry.md

@@ -76,7 +76,7 @@ The cluster registry feature deploys helper pods on the target edge cluster to a
 
 #### Pod mutating webhook
 * These pods implement Kubernetes mutating admission webhooks, serving an instance of the mutate API. The mutate API does two things:
-  * It modifies the image registry path to the local registry IP, substituting out the AOSM artifact store Azure container registry (ACR).
+  * It modifies the image registry path to the local registry IP, substituting out the AOSM artifact store Azure Container Registry (ACR).
   * It creates an Artifact CR on the edge cluster.
 
 #### Artifact reconciler

articles/virtual-desktop/required-fqdn-endpoint.md

@@ -42,7 +42,7 @@ The following table is the list of FQDNs and endpoints your session host VMs nee
 | `*.prod.warm.ingest.monitor.core.windows.net` | TCP | 443 | Agent traffic<br />[Diagnostic output](diagnostics-log-analytics.md) | `AzureMonitor` |
 | `gcs.prod.monitoring.core.windows.net` | TCP | 443 | Agent traffic | `AzureMonitor` |
 | `azkms.core.windows.net` | TCP | 1688 | Windows activation | `Internet` |
-| `mrsglobalsteus2prod.blob.core.windows.net` | TCP | 443 | Agent and side-by-side (SXS) stack updates | `AzureStorage` |
+| `mrsglobalsteus2prod.blob.core.windows.net` | TCP | 443 | Agent and side-by-side (SXS) stack updates | `Storage` |
 | `wvdportalstorageblob.blob.core.windows.net` | TCP | 443 | Azure portal support | `AzureCloud` |
 | `169.254.169.254` | TCP | 80 | [Azure Instance Metadata service endpoint](/azure/virtual-machines/windows/instance-metadata-service) | N/A |
 | `168.63.129.16` | TCP | 80 | [Session host health monitoring](../virtual-network/network-security-groups-overview.md#azure-platform-considerations) | N/A |