Merge pull request #182599 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/fundamentals/security-operations-applications.md

@@ -207,7 +207,7 @@ Alert any time these changes are detected outside of approved change management
 
 The following are links to useful resources:
 
-* Github Azure AD toolkit - [https://github.com/microsoft/AzureADToolkit](https://github.com/microsoft/AzureADToolkit)
+* GitHub Azure AD toolkit - [https://github.com/microsoft/AzureADToolkit](https://github.com/microsoft/AzureADToolkit)
 
 * Azure Key Vault security overview and security guidance - [Azure Key Vault security overview](../../key-vault/general/security-features.md)
 

articles/active-directory/hybrid/how-to-connect-install-custom.md

@@ -347,7 +347,7 @@ When you select the domain that you want to federate, Azure AD Connect provides
 
 ## Configuring federation with PingFederate
 You can configure PingFederate with Azure AD Connect in just a few clicks. The following prerequisites are required:
-- PingFederate 8.4 or later.  For more information, see [PingFederate integration with Azure Active Directory and Microsoft 365](https://docs.pingidentity.com/bundle/O365IG20_sm_integrationGuide/page/O365IG_c_integrationGuide.html).
+- PingFederate 8.4 or later.  For more information, see [PingFederate integration with Azure Active Directory and Microsoft 365](https://docs.pingidentity.com/bundle/pingfederate-azuread-office365-integration/).
 - A TLS/SSL certificate for the federation service name that you intend to use (for example, sts.contoso.com).
 
 ### Verify the domain

articles/active-directory/hybrid/tshoot-connect-sync-errors.md

@@ -218,7 +218,8 @@ Below are some examples which demonstrate the different weighs of attributes lik
 3. If a similar synchronized user with 10 UserCertificates plus for instance 4 subscriptions assigned (with all Service Plans enabled), the maximum number of ProxyAddresses decreases to 311.
 4. Now let’s take the above user which already holds the maximum number of ProxyAddresses, and say you need to add 1 more smtp address - to achieve 312 ProxyAddresses you would need to remove at least 3 UserCertificates (depending on the size of the certificate).
 
-> [NOTE] These numbers can vary slightly. As a rule of thumb, it is safer to assume that the limit of smtp addresses in ProxyAddresses is approximately 300 addresses to leave the room for the future growth of the object and its populated attributes. 
+>[!NOTE]
+> These numbers can vary slightly. As a rule of thumb, it is safer to assume that the limit of smtp addresses in ProxyAddresses is approximately 300 addresses to leave the room for the future growth of the object and its populated attributes. 
 
 ### How to fix
 

articles/data-factory/create-azure-ssis-integration-runtime-powershell.md

@@ -575,7 +575,7 @@ if(![string]::IsNullOrEmpty($ExpressCustomSetup))
         -ExpressCustomSetup $setups
 }
 
-# Add self-hosted integration runtime parameters if you configure a proxy for on-premises data accesss
+# Add self-hosted integration runtime parameters if you configure a proxy for on-premises data access
 if(![string]::IsNullOrEmpty($DataProxyIntegrationRuntimeName) -and ![string]::IsNullOrEmpty($DataProxyStagingLinkedServiceName))
 {
     Set-AzDataFactoryV2IntegrationRuntime -ResourceGroupName $ResourceGroupName `

articles/dms/known-issues-mongo-cosmos-db.md

@@ -1,5 +1,5 @@
 ---
-title: "Known issues: Migrate from MongoDB to Azure CosmosDB"
+title: "Known issues: Migrate from MongoDB to Azure Cosmos DB"
 titleSuffix: Azure Database Migration Service
 description: Learn about known issues and migration limitations with migrations from MongoDB to Azure Cosmos DB using the Azure Database Migration Service.
 services: database-migration
@@ -45,4 +45,4 @@ Known issues and limitations associated with migrations from MongoDB to Cosmos D
 ## Next steps
 
 * View the tutorial [Migrate MongoDB to Azure Cosmos DB's API for MongoDB online using DMS](tutorial-mongodb-cosmos-db-online.md).
-* View the tutorial [Migrate MongoDB to Azure Cosmos DB's API for MongoDB offline using DMS](tutorial-mongodb-cosmos-db.md).
+* View the tutorial [Migrate MongoDB to Azure Cosmos DB's API for MongoDB offline using DMS](tutorial-mongodb-cosmos-db.md).

articles/firewall-manager/policy-overview.md

@@ -11,7 +11,7 @@ ms.author: victorh
 
 # Azure Firewall Manager policy overview
 
-Firewall Policy the recommended method to configure your Azure Firewall. It's a global resource that can be used across multiple Azure Firewall instances in Secured Virtual Hubs and Hub Virtual Networks. Policies work across regions and subscriptions.
+Firewall Policy is the recommended method to configure your Azure Firewall. It's a global resource that can be used across multiple Azure Firewall instances in Secured Virtual Hubs and Hub Virtual Networks. Policies work across regions and subscriptions.
 
 ![Azure Firewall Manager policy](media/policy-overview/policy-overview.png)
 

articles/postgresql/flexible-server/concepts-logical.md

@@ -43,7 +43,7 @@ Logical decoding:
 
 1. Go to server parameters page on the portal.
 2. Set the server parameter `wal_level` to `logical`.
-3. If you want to use pglogical extension, search for the `shared_preload_libaries` parameter, and select `pglogical` from the drop-down box.
+3. If you want to use pglogical extension, search for the `shared_preload_libraries` parameter, and select `pglogical` from the drop-down box.
 4. Update `max_worker_processes` parameter value to at least 16. Otherwise, you may run into issues like `WARNING: out of background worker slots`.
 5. Save the changes and restart the server to apply the `wal_level` change.
 6. Confirm that your PostgreSQL instance allows network traffic from your connecting resource.