Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into 1642278-loc-clarification

Author: v-thpra

.gitignore

@@ -22,3 +22,5 @@ articles/directories.txt
 AzureMigration.ps1
 
 !/.vscode/extensions.json
+articles/data-lake-analytics/.vscode/settings.json
+.gitignore

.openpublishing.redirection.json

@@ -5,6 +5,11 @@
       "redirect_url": "https://github.com/Azure/azure-sdk-for-php",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/container-registry/container-registry-upgrade.md",
+      "redirect_url": "/azure/container-registry/container-registry-skus",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/azure-government/documentation-government-get-started-connect-with-vs.md",
       "redirect_url": "/azure/azure-government/documentation-government-welcome",
@@ -765,6 +770,12 @@
       "redirect_url": "/azure/machine-learning/service",
       "redirect_document_id": false
     },
+    
+    {
+      "source_path": "articles/cognitive-services/LUIS/luis-quickstart-intents-only.md",
+      "redirect_url": "/azure/cognitive-services/LUIS/tutorial-intents-only",
+      "redirect_document_id": false
+    },    
     {
       "source_path": "articles/cognitive-services/LUIS/luis-concept-roles.md",
       "redirect_url": "/azure/cognitive-services/LUIS/luis-concept-entity-types#entity-role-defines-context",
@@ -5275,6 +5286,26 @@
       "redirect_url": "/azure/app-service-mobile",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/application-gateway/application-gateway-customize-waf-rules-portal.md",
+      "redirect_url": "/azure/web-application-firewall/ag/application-gateway-customize-waf-rules-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/application-gateway/application-gateway-customize-waf-rules-powershell.md",
+      "redirect_url": "/azure/web-application-firewall/ag/application-gateway-customize-waf-rules-powershell",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/application-gateway/application-gateway-customize-waf-rules-cli.md",
+      "redirect_url": "/azure/web-application-firewall/ag/application-gateway-customize-waf-rules-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/application-gateway/custom-waf-rules-overview.md",
+      "redirect_url": "/azure/web-application-firewall/ag/custom-waf-rules-overview",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/application-gateway/application-gateway-waf-configuration.md",
       "redirect_url": "/azure/web-application-firewall/ag/application-gateway-waf-configuration",
@@ -16225,11 +16256,6 @@
       "redirect_url": "/azure/stream-analytics/stream-analytics-troubleshoot-input",
       "redirect_document_id": false
     },
-    {
-      "source_path": "articles/stream-analytics/powerbi-output-managed-identity.md",
-      "redirect_url": "/azure/stream-analytics/stream-analytics-define-outputs#power-bi",
-      "redirect_document_id": false
-    },
     {
       "source_path": "articles/stream-analytics/vs-code-how-to.md",
       "redirect_url": "/azure/stream-analytics/vscode-explore-jobs",
@@ -43720,5 +43746,15 @@
       "redirect_url": "/azure/cognitive-services/speech-service/how-to-use-conversation-transcription",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/machine-learning/service/publish-a-machine-learning-web-service.md",
+      "redirect_url": "/azure/machine-learning/service/deploy-a-machine-learning-web-service",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/studio/linear-regression-in-azure.md",
+      "redirect_url": "/azure/machine-learning/studio/use-case-excel-studio",
+      "redirect_document_id": false
+    }
   ]
 }

articles/active-directory-b2c/active-directory-b2c-custom-setup-msa-idp.md

@@ -40,7 +40,7 @@ To enable sign-in for users with a Microsoft account, you need to register an ap
 1. Select **Certificates & secrets**
 1. Click **New client secret**
 1. Enter a **Description** for the secret, for example *MSA Application Client Secret*, and then click **Add**.
-1. Record the application password shown in the **VALUE** column. You use this value in the next section.
+1. Record the application password shown in the **Value** column. You use this value in the next section.
 
 ## Create a policy key
 

articles/active-directory-b2c/active-directory-b2c-faqs.md

@@ -128,7 +128,7 @@ Not currently. This feature is on our roadmap. Verifying your domain in the **Do
 
 Follow these steps to delete your Azure AD B2C tenant.
 
-You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 

articles/active-directory-b2c/active-directory-b2c-get-started-custom.md

@@ -69,7 +69,7 @@ You need to register these two applications in your Azure AD B2C tenant only onc
 
 ### Register the IdentityExperienceFramework application
 
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -147,7 +147,7 @@ Now, grant permissions to the API scope you exposed earlier in the *IdentityExpe
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the *Cloud application administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for both scopes. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for both scopes. It might take a few minutes for the permissions to propagate.
 
 * * *
 

articles/active-directory-b2c/active-directory-b2c-reference-audit-logs.md

@@ -119,7 +119,7 @@ Follow these steps register an application, grant it the required Microsoft Grap
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in account if it's been assigned the *Global Administrator* role, or sign in with an account in your Azure AD B2C tenant that's been assigned the *Global Administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for the *AuditLog.Read.All* permission. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for the *AuditLog.Read.All* permission. It might take a few minutes for the permissions to propagate.
 
 * * *
 

articles/active-directory-b2c/active-directory-b2c-setup-aad-custom.md

@@ -43,7 +43,7 @@ To enable sign-in for users from a specific Azure AD organization, you need to r
 
 1. Select **Register**. Record the **Application (client) ID** for use in a later step.
 1. Select **Certificates & secrets**, and then select **New client secret**.
-1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **VALUE** of the secret for use in a later step.
+1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **Value** of the secret for use in a later step.
 
 ## Create a policy key
 

articles/active-directory-b2c/active-directory-b2c-setup-commonaad-custom.md

@@ -43,7 +43,7 @@ To enable sign-in for users from a specific Azure AD organization, you need to r
 
 1. Select **Register**. Record the **Application (client) ID** for use in a later step.
 1. Select **Certificates & secrets**, and then select **New client secret**.
-1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **VALUE** of the secret for use in a later step.
+1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **Value** of the secret for use in a later step.
 
 ## Create a policy key
 

articles/active-directory-b2c/active-directory-b2c-setup-msa-app.md

@@ -33,7 +33,7 @@ To use a Microsoft account as an [identity provider](active-directory-b2c-refere
 1. Select **Certificates & secrets**
 1. Click **New client secret**
 1. Enter a **Description** for the secret, for example *Application password 1*, and then click **Add**.
-1. Record the application password shown in the **VALUE** column. You need this when you configure the identity provider in the next section.
+1. Record the application password shown in the **Value** column. You need this when you configure the identity provider in the next section.
 
 ## Configure a Microsoft account as an identity provider
 

articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app-webapi.md

@@ -62,12 +62,12 @@ In the prerequisite tutorial, you registered a native client application named *
 1. Under **Configured permissions**, select **Add a permission**.
 1. Select the **My APIs** tab.
 1. Select the API to which the native client application should be granted access. For example, *webapi1*.
-1. Under **PERMISSION**, expand **demo**, and then select the scopes that you defined earlier. For example, *demo.read* and *demo.write*.
+1. Under **Permission**, expand **demo**, and then select the scopes that you defined earlier. For example, *demo.read* and *demo.write*.
 1. Select **Add permissions**. As directed, wait a few minutes before proceeding to the next step.
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the *Cloud application administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for both scopes. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for both scopes. It might take a few minutes for the permissions to propagate.
 
 * * *