added more screenshots, and added clarity to instructions in sign up

windows/deployment/do/mcc-isp-create-provision-deploy.md

@@ -71,6 +71,8 @@ BGP (Border Gateway Protocol) routing is another method offered for client routi
     > [!NOTE]
     > **Prefix count** and **IP Space** will stop displaying `0` when BGP is successfully established.
 
+1. After you are finished configuring your server, don't forget to press **Save** to save your configurations.
+
 ## Deploy cache node software to server  
 
 Once the user executes the cache server provisioning script, resources are created behind the scenes resulting in the successful cache node installation. The script takes the input of different IDs outlined below to register the server as an Azure IoT Edge device. Even though Microsoft Connected Cache scenario isn't related to IoT, Azure IoT Edge is installed for container management and communication operation purposes.
@@ -113,7 +115,7 @@ There are five IDs that the device provisioning script takes as input in order t
 
 1. Copy and paste the script command line shown in the Azure portal.
 
-1. Run the script in your server terminal for your cache node by . The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
+1. Run the script in your server terminal for your cache node. The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
 
     > [!NOTE]
     > The same script can be used to provision multiple cache nodes, but the command line is unique per cache node. Additionally, if you need to re-provision your server or provision a new server or VM for the cache node, you must copy the command line from the Azure portal again as the "registrationkey" value is unique for each successful execution of the provisioning script.
@@ -135,7 +137,7 @@ There are five IDs that the device provisioning script takes as input in order t
 
 | Field Name | Expected Value| Description |
 |---|---|---|
-| **Cache drive folder** | File path string | Up to 9 drive folders accessible by the cache node can be configured for each cache node to configure cache storage. Enter the file path to each drive. For example: `/dev/folder/` Each cache drive should have read/write permissions configured. |
+| **Cache drive folder** | File path string | Up to 9 drive folders accessible by the cache node can be configured for each cache node to configure cache storage. Enter the location of the folder in Ubuntu where the external physical drive is mounted. For example: `/dev/folder/` Each cache drive should have read/write permissions configured. |
 | **Cache drive size in gigabytes** | Integer in GB | Set the size of each drive configured for the cache node. |
 
 ### Client routing fields

windows/deployment/do/mcc-isp-signup.md

@@ -41,10 +41,21 @@ Before you begin sign up, ensure you have the following components:
 
    :::image type="content" source="./images/mcc-isp-search.png" alt-text="Screenshot of the Azure portal that shows the Microsoft Connected Cache resource in Azure marketplace.":::
 
-1. Select **Create** to create a **Microsoft Connected Cache**. When prompted, enter a name for your cache resource.  
+1. Select **Create** to create a **Microsoft Connected Cache**. When prompted, choose the subscription, resource group, and location of your cache node. Also, enter a name for your cache node.
+
+   :::image type="content" source="./images/mcc-isp-create-resource-fields.png" alt-text="Screenshot of the Azure portal that shows the Microsoft Connected Cache resource creation step.":::
 
    > [!IMPORTANT]
    > After your resource has been created, we need some information to verify your network operator status and approve you to host Microsoft Connected Cache nodes. Please ensure that your [Peering DB](https://www.peeringdb.com/) organization information is up to date as this information will be used for verification. The NOC contact email will be used to send verification information.
+
+After a few moments, you will see a "Validation successful" message, indicating you can move onto the next step and select **Create**.
+
+   :::image type="content" source="./images/mcc-isp-create-resource-validated.png" alt-text="Screenshot of the Azure portal that shows a green validation successful message for the creation of the Microsoft Connected Cache resource.":::
+
+1. The creation of the cache node may take a few minutes. After a successful creation, you will see a **Deployment complete** page as below:
+
+    :::image type="content" source="./images/mcc-isp-create-deployment-complete.png" alt-text="Screenshot of the Azure portal that shows a green validation successful message for the creation of the Microsoft Connected Cache resource.":::
+
 1. Navigate to **Settings** > **Sign up**. Enter your organization ASN. Indicate whether you're a transit provider. If so, additionally, include any ASN(s) for downstream network operators that you may transit traffic for.
 
    :::image type="content" source="./images/mcc-isp-sign-up.png" alt-text="Screenshot of the sign up page in the Microsoft Connected Cache resource page in Azure portal." lightbox="./images/mcc-isp-sign-up.png":::
@@ -58,7 +69,7 @@ Before you begin sign up, ensure you have the following components:
 
    **Can't find the verification email in your inbox?** Check your NOC email is correct in [Peering DB](https://www.peeringdb.com/). Search for an email from the sender **microsoft-noreply@microsoft.com** with the email subject: **Here’s your Microsoft Connected Cache verification code** in your Spam folders. Still can't find it? Ensure that your email admin rules allow emails from the sender **microsoft-noreply@microsoft.com**.
 
-1. Once verified, follow the instructions in [Create, provision, and deploy cache node](mcc-isp-create-provision-deploy.md) to create your cache node.
+1. Once verified, you are ready to move to the next step! Next, follow the instructions in **[Create, provision, and deploy cache node](mcc-isp-create-provision-deploy.md)** to create your cache node.
 
 <!--## Traffic estimation
 

windows/deployment/do/mcc-isp-vm-performance.md

@@ -13,7 +13,37 @@ ms.collection: M365-modern-desktop
 ms.topic: reference
 ---
 
-# Enhancing virtual machine performance
+# Enhancing cache performance
+
+To make sure you're maximizing the performance of your cache node, review the following information:
+
+#### OS requirements
+
+The Microsoft Connected Cache module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice.
+
+#### NIC requirements
+
+- Multiple NICs on a single MCC instance are supported using a *link aggregated* configuration.
+- 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
+
+#### Drive performance
+
+The maximum number of disks supported is 9. When configuring your drives, we recommend SSD drives as cache read speed of SSD is superior to HDD. In addition, using multiple disks is recommended to improve cache performance. 
+
+RAID disk configurations are discouraged as cache performance will be impacted. If using RAID disk configurations, ensure striping.
+
+### Hardware configuration example
+
+There are many hardware configurations that suit Microsoft Connected Cache. As an example, a customer has deployed the following hardware configuration and is able to achieve a peak egress of about 35 Gbps:
+
+**Dell PowerEdge R330**
+
+- 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40 GHz, total 32 core
+- 48 GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s
+- 4 - Transcend SSD230s 1 TB SATA Drives
+- Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
+
+### Enhancing virtual machine performance
 
 In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change two settings.