Merge branch 'MicrosoftDocs:main' into main

Author: eak13

articles/deployment-environments/how-to-configure-managed-identity.md

@@ -124,7 +124,7 @@ You can set up your key vault to use either a [key vault access policy](/azure/k
 
 ### Key vault access policy
 
-[!INCLUDE [contributor-role-warning.md](~/reusable-content/ce-skilling/azure/includes/key-vault/includes/key-vault-contributor-role-warning.md)]
+[!INCLUDE [contributor-role-warning.md](~/reusable-content/ce-skilling/azure/includes/key-vault/key-vault-contributor-role-warning.md)]
 
 If the key vault is configured to use a key vault access policy:
 

articles/private-link/private-endpoint-overview.md

@@ -80,7 +80,7 @@ A private-link resource is the destination target of a specified private endpoin
 | Azure Batch | Microsoft.Batch/batchAccounts | batchAccount, nodeManagement |
 | Azure Cache for Redis | Microsoft.Cache/Redis | redisCache |
 | Azure Cache for Redis Enterprise | Microsoft.Cache/redisEnterprise | redisEnterprise |
-| Azure Container Apps | Microsoft.App/ManagedEnvironments | managedEnvironment |
+| Azure Container Apps | Microsoft.App/ManagedEnvironments | managedEnvironments |
 | Azure Container Registry | Microsoft.ContainerRegistry/registries | registry |
 | Azure Cosmos DB | Microsoft.AzureCosmosDB/databaseAccounts | SQL, MongoDB, Cassandra, Gremlin, Table |
 | Azure Cosmos DB for MongoDB vCore | Microsoft.DocumentDb/mongoClusters | mongoCluster |

articles/redis/architecture.md

@@ -63,10 +63,10 @@ The **Non-Clustered (preview)** clustering policy stores data on each node witho
 
 The considerations for using Non-Clustered (Preview) policy are:
 
-- It only applies to Azure Managed Redis tiers less than or equal to 25 GB.
-- It’s not as performant as other clustering policies because CPUs can only multi-thread with Redis Enterprise software when it’s sharded.
-- If you want to scale up your Azure Managed Redis cache, you must firs change the cluster policy.
-- If you're moving from Basic, Standard, or Premium non-clustered topology, consider to using OSS clusters to accelerate performance. Non-clustered should only be considered if the application program can't work with either OSS or Enterprise topologies.
+- This only applies to Azure Managed Redis tiers that are less than or equal to 25 GB.
+- It’s not as performant as other clustering policies, because CPUs can only multi-thread with Redis Enterprise software when the cache is sharded.
+- If you want to scale up your Azure Managed Redis cache, you must first change the cluster policy.
+- If you're moving from a Basic, Standard, or Premium non-clustered topology, consider using OSS clusters to improve performance. Non-clustered configurations should only be used if the application cannot support either OSS or Enterprise topologies.
 
 ### Scaling out or adding nodes
 

articles/role-based-access-control/built-in-roles/security.md

@@ -423,7 +423,7 @@ Manage key vaults, but does not allow you to assign roles in Azure RBAC, and doe
 
 [Learn more](/azure/key-vault/general/security-features)
 
-[!INCLUDE [contributor-role-warning.md](~/reusable-content/ce-skilling/azure/includes/key-vault/includes/key-vault-contributor-role-warning.md)]
+[!INCLUDE [contributor-role-warning.md](~/reusable-content/ce-skilling/azure/includes/key-vault/key-vault-contributor-role-warning.md)]
 
 > [!div class="mx-tableFixed"]
 > | Actions | Description |
@@ -1605,4 +1605,4 @@ View permissions for Microsoft Defender for Cloud. Can view recommendations, ale
 
 ## Next steps
 
-- [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal)
+- [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal)