From f891b13d125b95f92c3f8d9c0a7137bc573760de Mon Sep 17 00:00:00 2001
From: chrisjlin <36452239+chrisjlin@users.noreply.github.com>
Date: Mon, 2 Dec 2024 16:42:28 -0800
Subject: [PATCH] Specify host machine type in pem file docs

---
 windows/deployment/do/mcc-ent-deploy-to-linux.md   | 2 +-
 windows/deployment/do/mcc-ent-deploy-to-windows.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md
index 6ca1ef6192..8280d47b34 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-linux.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md
@@ -28,7 +28,7 @@ Before deploying Connected Cache to a Linux host machine, ensure that the host m
 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 
     >[!Note]
-    >* If you are deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add `proxyTlsCertificatePath="/path/to/pem/file"` to the provisioning command.
+    >* If you are deploying your cache node to a Linux host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add `proxyTlsCertificatePath="/path/to/pem/file"` to the provisioning command.
 
 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 105def16cf..d55902c2ac 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-windows.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md
@@ -34,7 +34,7 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 
    >[!Note]
-   >* If you are deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add `-proxyTlsCertificatePemFileName "path/to/pem/file"` to the provisioning command.
+   >* If you are deploying your cache node to a Windows host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add `-proxyTlsCertificatePemFileName "path/to/pem/file"` to the provisioning command.
 
 1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run.
 1. Create a `$User` PowerShell variable containing the username of the account you intend to designate as the Connected Cache runtime account.