edits, remove unused png files

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

@@ -13,7 +13,7 @@ appliesto:
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for ISPs</a>	
-ms.date: 07/27/2023
+ms.date: 03/21/2024
 ---
 
 # Microsoft Connected Cache for ISPs overview
@@ -39,9 +39,10 @@ Microsoft Connected Cache uses Delivery Optimization as the backbone for Microso
 
 #### Are you already peering with 8075?
 
-MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. cannot be served via 8075. So, even if you are peering with Microsoft, you can benefit from installing MCC!
+MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing MCC.
+
+:::image type="content" source="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png" alt-text="Chart containing Peering vs Cache Content Traffic." lightbox="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png":::
 
-![mcc-isp-peeringvsmcc](media/mcc-isp-overview/mcc-isp-peeringvsmcc.png)
 For the full list of content endpoints that Microsoft Connected Cache for ISPs supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).
 
 ## How MCC works
@@ -74,18 +75,18 @@ The following steps describe how MCC is provisioned and used:
 1. Subsequent requests from end-user devices for content will be served from cache.
 
 1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
-### __Hardware recommendation__
 
-Below are the hardware recommendations based on traffic ranges.
+### Hardware recommendation
 
+The following are recommended hardware configurations based on traffic ranges:
 
 | Microsoft Connected Cache Machine Class | Scenario |Traffic Range| VM/Hardware Recommendation|
 | -------- | -------- | -------- | -------- |
-| Edge   | For smaller ISPs or remote sites part of a larger network. |< 5 Gbps Peak|VM Up to 8 Cores</br></br>Up to 16 GB Memory</br></br>1 500 GB SSD|
-| Metro POP   | For ISPs, IXs, or Transit Providers serving a moderate amount of traffic in a network that may require one of more cache nodes.   |5 - 20 Gbps Peak|VM or Hardware</br></br>16 Cores*</br></br>32 GB Memory</br></br>2 - 3 500 GB SSDs each|
-|Data Center|For ISPs, IXs, or Transit Providers serving a large amount traffic daily and may require deployment of multiple cache nodes.|20 - 40 Gbps Peak|Hardware (see sample spec below)</br></br>32 or More Cores*</br></br>64 or more GB Memory</br></br>4 - 6 500 - 1 TB SSDs** each|
+| Edge   | For smaller ISPs or remote sites part of a larger network. |< 5 Gbps Peak| **VM** </br> </br>Up to 8 cores</br></br>Up to 16-GB memory</br></br>1 500 GB SSD|
+| Metro POP   | For ISPs, IXs, or Transit Providers serving a moderate amount of traffic in a network that might require one of more cache nodes.   |5 to 20 Gbps Peak| **VM or hardware**</br></br>16 cores*</br></br>32-GB memory</br></br>2 - 3 500-GB SSDs each|
+|Data Center|For ISPs, IXs, or Transit Providers serving a large amount traffic daily and might require deployment of multiple cache nodes.|20 to 40 Gbps Peak| **Hardware**, see sample spec below:</br></br> 32 or more cores*</br></br>64 or more GB memory</br></br>4 - 6 500 - 1-TB SSDs** each |
 
-*Requires systems (chipset, CPU, motherboard) with PCIe version 3 or higher
+*Requires systems (chipset, CPU, motherboard) with PCIe version 3, or higher.
 
-**Drive speeds are important and to achieve higher egress we recommend SSD NVMe in m.2 PCIe slot (version 4 or higher)
+**Drive speeds are important and to achieve higher egress, we recommend SSD NVMe in m.2 PCIe slot (version 4, or higher).