From 8d3574f47dee2e2a9654cb8cf0001634b1291bf6 Mon Sep 17 00:00:00 2001
From: Meghan Stewart <33289333+mestew@users.noreply.github.com>
Date: Mon, 28 Oct 2024 14:38:26 -0700
Subject: [PATCH] edits

---
 windows/deployment/do/mcc-ent-create-resource-and-cache.md | 4 ++--
 windows/deployment/do/mcc-ent-deploy-to-linux.md           | 2 +-
 windows/deployment/do/mcc-ent-deploy-to-windows.md         | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md
index 889d3c2fd8..3f022ca166 100644
--- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md
+++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md
@@ -299,7 +299,7 @@ az mcc ent node list --mcc-resource-name <mymccresource> --resource-group <myrg>
 ### Delete Connected Cache resource
 
 # [Azure portal](#tab/portal)
-Navigate to the Connected Cache resource to delete, then select the **Delete** button on top.
+Navigate to the Connected Cache resource to delete, then select the **Delete** option on top.
 
 
 # [Azure CLI](#tab/cli)
@@ -319,7 +319,7 @@ az mcc ent node delete --cache-node-name <mycachenode> --mcc-resource-name <mymc
 ### Delete cache node
 
 # [Azure portal](#tab/portal)
-On the left pane, select **Cache Nodes** under **Cache Node Management** to see all the cache nodes under the Connected Cache resource. Select the cache node you wish to delete and select the **Delete** button on top of the page.
+On the left pane, select **Cache Nodes** under **Cache Node Management** to see all the cache nodes under the Connected Cache resource. Select the cache node you wish to delete and select the **Delete** option on top of the page.
 
 
 # [Azure CLI](#tab/cli)
diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md
index 1dccafb769..b7cfb00596 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-linux.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md
@@ -24,7 +24,7 @@ Before deploying Connected Cache to a Linux host machine, ensure that the host m
 # [Azure portal](#tab/portal)
 
 1. Within the Azure portal, navigate to the **Provisioning** tab of your cache node and copy the provisioning command.
-1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
+1. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the package onto the host machine.
 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
 1. Run the provisioning command on the host machine.
diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md
index bc519d2815..d5180ee2f1 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-windows.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md
@@ -26,7 +26,7 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
 # [Azure portal](#tab/portal)
 
 1. Within the Azure portal, navigate to the **Provisioning** tab of your cache node and copy the provisioning command.
-1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process.
+1. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the package onto the host machine. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process.
 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run.
 1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account.