Merge pull request #208922 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/active-directory/privileged-identity-management/pim-how-to-change-default-settings.md

@@ -103,6 +103,8 @@ If setting multiple approvers, approval completes as soon as one of them approve
     ![Select a user or group pane to select approvers](./media/pim-resource-roles-configure-role-settings/resources-role-settings-select-approvers.png)
 
 1. Select at least one user and then click **Select**. Select at least one approver. If no specific approvers are selected, Privileged Role Administrators and Global Administrators become the default approvers.
+   > [!Note]
+   > An approver does not have to have an Azure AD administrative role themselves. They can be a regular user, such as an IT executive.
 
 1. Select **Update** to save your changes.
 

articles/aks/ingress-basic.md

@@ -394,7 +394,7 @@ kubectl apply -f aks-helloworld-two.yaml --namespace ingress-basic
 
 Both applications are now running on your Kubernetes cluster. To route traffic to each application, create a Kubernetes ingress resource. The ingress resource configures the rules that route traffic to one of the two applications.
 
-In the following example, traffic to *EXTERNAL_IP* is routed to the service named `aks-helloworld-one`. Traffic to *EXTERNAL_IP/hello-world-two* is routed to the `aks-helloworld-two` service. Traffic to *EXTERNAL_IP/static* is routed to the service named `aks-helloworld-one` for static assets.
+In the following example, traffic to *EXTERNAL_IP/hello-world-one* is routed to the service named `aks-helloworld-one`. Traffic to *EXTERNAL_IP/hello-world-two* is routed to the `aks-helloworld-two` service. Traffic to *EXTERNAL_IP/static* is routed to the service named `aks-helloworld-one` for static assets.
 
 Create a file named `hello-world-ingress.yaml` and copy in the following example YAML.
 

articles/azure-functions/functions-bindings-register.md

@@ -45,7 +45,7 @@ The following table lists the currently available versions of the default *Micro
 <sup>1</sup> Version 3.x of the extension bundle currently doesn't include the [Table Storage bindings](./functions-bindings-storage-table.md). If your app requires Table Storage, you'll need to continue using the 2.x version for now.
 
 > [!NOTE]
-> While you can a specify custom version range in host.json, we recommend you use a version value from this table.
+> Even though host.json supports custom ranges for `version`, you should use a version value from this table.
 
 ## Explicitly install extensions
 

articles/azure-monitor/profiler/profiler.md

@@ -17,7 +17,7 @@ To enable Profiler on Linux, walk through the [ASP.NET Core Azure Linux web apps
 > For more information about supported runtime, see [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
 
 
-## Pre-requisites
+## Prerequisites
 
 - An [Azure App Services ASP.NET/ASP.NET Core app](../../app-service/quickstart-dotnetcore.md).
 - [Application Insights resource](../app/create-new-resource.md) connected to your App Service app. 

articles/iot-hub-device-update/device-update-proxy-updates.md

@@ -16,7 +16,7 @@ With Proxy updates, you can (1) target over-the-air updates to multiple componen
 * Targeting specific update files to different apps/components on the device  
 * Targeting specific update files to sensors connected to an IoT devices. These sensors could be connected to the IoT device over a network protocol (for example, USB, CANbus etc.). 
 
-## Pre-requisite
+## Prerequisite 
 In order to update a component or components that connected to a target IoT Device, the device builder must register a custom **Component Enumerator Extension** that is built specifically for their IoT devices. The Component Enumerator Extension is required so that the Device Update Agent can map a **'child update'** with a specific component, or group of components, which the update is intended for. See [Contoso Component Enumerator](components-enumerator.md) for an example on how to implement and register a custom Component Enumerator extension.
 
 > [!NOTE]

articles/remote-rendering/how-tos/create-an-account.md

@@ -16,7 +16,7 @@ This chapter guides you through the steps to create an account for the **Azure R
 
 The following steps are needed to create an account for the Azure Remote Rendering service:
 
-1. Go to the [Mixed Reality Preview page](https://aka.ms/MixedRealityPrivatePreview)
+1. Go to the Azure portal [portal.azure.com](https://ms.portal.azure.com/)
 1. Click the 'Create a resource' button
 1. In the search field ("Search the marketplace"), type in "Remote Rendering" and hit 'enter'.
 1. In the result list, click on the "Remote Rendering" tile

articles/synapse-analytics/sql/create-external-table-as-select.md

@@ -83,12 +83,12 @@ USE [mydbname];
 GO
 
 SELECT
-    country_name, population
+    CountryName, PopulationCount
 FROM PopulationCETAS
 WHERE
-    [year] = 2019
+    [Year] = 2019
 ORDER BY
-    [population] DESC;
+    [PopulationCount] DESC;
 ```
 
 ## Remarks