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

articles/active-directory/hybrid/how-to-connect-selective-password-hash-synchronization.md

@@ -36,7 +36,7 @@ To reduce the configuration administrative effort, you should first consider the
 > Configuring selective password hash synchronization directly influences password writeback. Password changes or password resets that are initiated in Azure Active Directory write back to on-premises Active Directory only if the user is in scope for password hash synchronization. 
 
 ### The adminDescription attribute
-Both scenarios rely on setting the adminDescription attribute of users to a specific value.  This allows the the rules to be applied and is what makes selective PHS work.
+Both scenarios rely on setting the adminDescription attribute of users to a specific value.  This allows the rules to be applied and is what makes selective PHS work.
 
 |Scenario|adminDescription value|
 |-----|-----|
@@ -78,7 +78,7 @@ The following section describes how to enable selective password hash synchroniz
 - Set the attribute value, in active directory, that was defined as scoping attribute on the users you want to allow in password hash synchronization. 
 
 >[!Important]
->The steps provided to configure selective password hash synchronization will only effect user objects that have 
+>The steps provided to configure selective password hash synchronization will only affect user objects that have 
 the attribute **adminDescription** populated in Active Directory with the value of **PHSFiltered**.
 >If this attribute is not populated or the value is something other than **PHSFiltered** then these rules will not be applied to the user objects.
 
@@ -92,7 +92,7 @@ the attribute **adminDescription** populated in Active Directory with the value
  3.	The first rule will disable password hash sync.
  Provide the following name to the new custom rule: **In from AD - User AccountEnabled - Filter Users from PHS**.
  Change the precedence value to a number lower than 100 (for example **90** or whichever is the lowest value available in your environment).
- Make sure the checkboxes **Enable Password Sync** and **Disabled** are unchecked and c.
+ Make sure the checkboxes **Enable Password Sync** and **Disabled** are unchecked.
  Click **Next**.
      ![Edit inbound](media/how-to-connect-selective-password-hash-synchronization/exclude-3.png)
  4.	In **Scoping filter**, click **Add clause**.
@@ -152,7 +152,7 @@ The following is a summary of the actions that will be taken in the steps below:
 - Set the attribute value, in active directory, that was defined as scoping attribute on the users you want to allow in password hash synchronization. 
 
 >[!Important]
->The steps provided to configure selective password hash synchronization will only effect user objects that have 
+>The steps provided to configure selective password hash synchronization will only affect user objects that have 
 the attribute **adminDescription** populated in Active Directory with the value of **PHSIncluded**.
 >If this attribute is not populated or the value is something other than **PHSIncluded** then these rules will not be applied to the user objects.
 

articles/azure-signalr/signalr-resource-faq.md

@@ -57,13 +57,13 @@ For new applications, only default and serverless mode should be used. The main
 
 Classic mode is designed for backward compatibility for existing applications so should not be used for new applications.
 
-For more information about service mode in [this doc](concept-service-mode.md).
+For more information about service mode, see [Service mode in Azure SignalR Service](concept-service-mode.md).
 
 ## Can I send message from client in serverless mode?
 
 You can send message from client if you configure upstream in your SignalR instance. Upstream is a set of endpoints that can receive messages and connection events from SignalR service. If no upstream is configured, messages from client will be ignored.
 
-For more information about upstream see [this doc](concept-upstream.md).
+For more information about upstream, see [Upstream settings](concept-upstream.md).
 
 Upstream is currently in public preview.
 
@@ -82,4 +82,4 @@ You can configure Azure SignalR Service for different service modes: `Classic`,
 
 ## Where does my data reside?
 
-Azure SignalR Service works as a data processor service. It won't store any customer content, and data residency is included by design. If you use Azure SignalR Service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
+Azure SignalR Service works as a data processor service. It won't store any customer content, and data residency is included by design. If you use Azure SignalR Service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.

articles/certification/program-requirements-edge-secured-core.md

@@ -41,7 +41,7 @@ Edge Secured-core is an incremental certification in the Azure Certified Device
 |Name|SecuredCore.Encryption.Storage|
 |:---|:---|
 |Status|Required|
-|Description|The purpose of the test to validate that sensitive data can be encrypted on non-volitile storage.|
+|Description|The purpose of the test to validate that sensitive data can be encrypted on non-volatile storage.|
 |Target Availability|2021|
 |Applies To|Any device|
 |OS|Agnostic|

articles/container-registry/container-registry-tasks-multi-step.md

@@ -60,7 +60,7 @@ steps:
     build: -t $Registry/hello-world:$ID .
     when: ["-"]
   - id: build-tests
-    build -t $Registry/hello-world-tests ./funcTests
+    build: -t $Registry/hello-world-tests ./funcTests
     when: ["-"]
   - id: push
     push: ["$Registry/helloworld:$ID"]
@@ -161,4 +161,4 @@ You can find multi-step task reference and examples here:
 <!-- LINKS - Internal -->
 [az-acr-task-create]: /cli/azure/acr/task#az-acr-task-create
 [az-acr-run]: /cli/azure/acr#az-acr-run
-[az-acr-task]: /cli/azure/acr/task
+[az-acr-task]: /cli/azure/acr/task

articles/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell.md

@@ -29,7 +29,7 @@ To upload your VHD to Azure, you'll need to create an empty managed disk that is
 
 This kind of managed disk has two unique states:
 
-- ReadToUpload, which means the disk is ready to receive an upload but, no [secure access signature](../../storage/common/storage-sas-overview.md) (SAS) has been generated.
+- ReadyToUpload, which means the disk is ready to receive an upload but, no [secure access signature](../../storage/common/storage-sas-overview.md) (SAS) has been generated.
 - ActiveUpload, which means that the disk is ready to receive an upload and the SAS has been generated.
 
 > [!NOTE]