From a9d0024ab63a3a0d64ccea2421fd1be1ecc5c47c Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 3 Oct 2024 15:24:24 -0700 Subject: [PATCH] revise example script --- windows/deployment/do/mcc-ent-manage-cache-using-CLI.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md b/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md index b5328c44fb..67c078e27f 100644 --- a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md +++ b/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md @@ -137,7 +137,7 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script. ### Example script: -Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and five MCC cache nodes. +Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and multiple MCC cache nodes.