From e77f56b0d4dfc2446887087cfc7c35179badbae9 Mon Sep 17 00:00:00 2001 From: Ruchika Mittal Date: Tue, 8 Jul 2025 22:26:07 +0530 Subject: [PATCH] typo fix --- windows/deployment/do/mcc-ent-deploy-to-windows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index 791df591db..4aff369991 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -31,7 +31,7 @@ For Connected Cache deployment to succeed, you must allow direct calls to the De 1. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the archive onto the host machine. >[!Note] - >* The provisioning package should be extracted to a directory that isn't synced to OneDrive, as the sychronization process will interfere with the installation. It is recommended to extract the provisioning package to the root directory of the host machine (e.g. C:\mccInstaller) + >* The provisioning package should be extracted to a directory that isn't synced to OneDrive, as the synchronization process will interfere with the installation. It is recommended to extract the provisioning package to the root directory of the host machine (e.g. C:\mccInstaller) 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.