Merge pull request #223975 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: huypub

articles/azure-monitor/essentials/metrics-store-custom-rest-api.md

@@ -50,7 +50,7 @@ curl -X POST 'https://login.microsoftonline.com/<tennant ID>/oauth2/token' \
 --data-urlencode 'grant_type=client_credentials' \
 --data-urlencode 'client_id=<your apps client ID>' \
 --data-urlencode 'client_secret=<your apps client secret' \
---data-urlencode 'resource=https://management.azure.com'
+--data-urlencode 'resource=https://monitor.azure.com'
 ```
 
 The response body appears as follows:  
@@ -144,4 +144,4 @@ If you receive an error message with some part of the process, consider the foll
 
 ## Next steps
 
-- Learn more about [custom metrics](./metrics-custom-overview.md).
+- Learn more about [custom metrics](./metrics-custom-overview.md).

articles/azure-monitor/essentials/prometheus-metrics-enable.md

@@ -76,7 +76,7 @@ The output for each command will look similar to the following:
     "metrics": {
         "enabled": true,
         "kubeStateMetrics": {
-            "metrican'tationsAllowList": "",
+            "metricAnnotationsAllowList": "",
             "metricLabelsAllowlist": ""
         }
     }
@@ -102,7 +102,7 @@ The output will be similar to the following:
         "metrics": {
           "enabled": true,
           "kubeStateMetrics": {
-            "metrican'tationsAllowList": "pods=[k8s-annotation-1,k8s-annotation-n]",
+            "metricAnnotationsAllowList": "pods=[k8s-annotation-1,k8s-annotation-n]",
             "metricLabelsAllowlist": "namespaces=[k8s-label-1,k8s-label-n]"
           }
         }

articles/marketplace/azure-container-technical-assets.md

@@ -52,8 +52,8 @@ You can't deploy an image to Azure Container Instances from an on-premises regis
 
 - If you already have a working container in your local registry, create an Azure Registry and upload your container image to the Azure Container Registry. To learn more, see [Tutorial: Build and deploy container images in the cloud with Azure Container Registry Tasks](../container-registry/container-registry-tutorial-quick-task.md).
 
-- If don’t have a container image yet and need to containerize your existing application or create a new container based application,  clone the application source code from GitHub, create a container image from the application source, and test the image in a local Docker environment. To learn more, see [Tutorial: Create a container image for deployment to Azure Container Instances](../container-instances/container-instances-tutorial-prepare-app.md).
+- If you don't have a container image yet, and you need to containerize your existing application or create a new container-based application, clone the application source code from GitHub, create a container image from the application source, and test the image in a local Docker environment. To learn more, see [Tutorial: Create a container image for deployment to Azure Container Instances](../container-instances/container-instances-tutorial-prepare-app.md).
 
 ## Next steps
 
-- [Create your container offer](azure-container-offer-setup.md)
+- [Create your container offer](azure-container-offer-setup.md)

articles/site-recovery/azure-to-azure-network-mapping.md

@@ -20,7 +20,7 @@ Before you map networks, you should have [Azure VNets](../virtual-network/virtua
 
 ## Set up network mapping manually (Optional)
 
->[!NOTE
+>[!NOTE]
 > Replication can now be done between any two Azure regions around the world. Customers are no longer limited to enabling replication within their continent.
 
 Map networks as follows: