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

Author: guyhay

.gitignore

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

.openpublishing.publish.config.json

@@ -194,7 +194,7 @@
     {
       "path_to_root": "samples-cognitive-services-speech-sdk",
       "url": "https://github.com/Azure-Samples/cognitive-services-speech-sdk",
-      "branch": "docs-201809"
+      "branch": "rhurey/quickstart.refactor"
     },
     {
       "path_to_root": "media-services-v3-dotnet-quickstarts",
@@ -342,6 +342,11 @@
       "url": "https://github.com/Azure-Samples/azure-cosmos-db-sql-api-nodejs-getting-started",
       "branch": "master"
     },
+    {
+      "path_to_root": "azure-cosmos-db-python-getting-started",
+      "url": "https://github.com/Azure-Samples/azure-cosmos-db-python-getting-started",
+      "branch": "master"
+    },
     {
       "path_to_root": "cognitive-services-content-moderator-samples",
       "url": "https://github.com/Azure-Samples/cognitive-services-content-moderator-samples",
@@ -392,6 +397,11 @@
       "path_to_root": "azure-cosmosdb-java-v2",
       "url": "https://github.com/Azure/azure-cosmosdb-java",
       "branch": "master"
+    },
+    {
+      "path_to_root": "azure-cosmosdb-java-v4-getting-started",
+      "url": "https://github.com/Azure-Samples/azure-cosmos-java-getting-started",
+      "branch": "master"
     }
   ],
   "branch_target_mapping": {

.openpublishing.redirection.json

@@ -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-custom-setup-msa-idp.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](http://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-faqs.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-get-started-custom.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-reference-audit-logs.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-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

@@ -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