Merge pull request #183737 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: Taojunshen

articles/active-directory/develop/active-directory-saml-claims-customization.md

@@ -111,7 +111,7 @@ To apply a transformation to a user attribute:
 
 1. In **Manage claim**, select *Transformation* as the claim source to open the **Manage transformation** page.
 2. Select the function from the transformation dropdown. Depending on the function selected, you will have to provide parameters and a constant value to evaluate in the transformation. Refer to the table below for more information about the available functions.
-3. (preview ) `Treat source as multivalued` is a checkbox indicating if the transform should be applied to all values or just the first. By default, transformations will only be applied to the first element in a multi value claim, by checking this box it ensures it is applied to all. This checkbox will only be enabled for multi valued attributes, for example `user.proxyaddresses`.
+3. (preview) `Treat source as multivalued` is a checkbox indicating if the transform should be applied to all values or just the first. By default, transformations will only be applied to the first element in a multi value claim, by checking this box it ensures it is applied to all. This checkbox will only be enabled for multi valued attributes, for example `user.proxyaddresses`.
 4. To apply multiple transformation, click on **Add transformation**. You can apply a maximum of two transformation to a claim. For example, you could first extract the email prefix of the `user.mail`. Then, make the string upper case.
 
    ![Multiple claims transformation](./media/active-directory-saml-claims-customization/sso-saml-multiple-claims-transformation.png)

articles/active-directory/develop/v2-oauth2-device-code.md

@@ -119,7 +119,7 @@ A successful token response will look like:
 
 | Parameter | Format | Description |
 | --------- | ------ | ----------- |
-| `token_type` | String| Always "Bearer. |
+| `token_type` | String| Always `Bearer`. |
 | `scope` | Space separated strings | If an access token was returned, this lists the scopes the access token is valid for. |
 | `expires_in`| int | Number of seconds before the included access token is valid for. |
 | `access_token`| Opaque string | Issued for the [scopes](v2-permissions-and-consent.md) that were requested.  |

articles/app-service/tutorial-custom-container.md

@@ -525,7 +525,7 @@ Your App Service app now can pull the container image securely from your private
     az webapp deployment container config --enable-cd true --name <app-name> --resource-group myResourceGroup --query CI_CD_URL --output tsv
     ```
 
-    `CI_CD_URL` is a URL that App Service generates for you. Your registry should this URL to notify App Service that an image push occurred. It doesn't actually create the webhook for you.
+    `CI_CD_URL` is a URL that App Service generates for you. Your registry should use this URL to notify App Service that an image push occurred. It doesn't actually create the webhook for you.
 
 1. Create a webhook in your container registry using the CI_CD_URL you got from the last step.