diff --git a/windows/deployment/do/delivery-optimization-test.md b/windows/deployment/do/delivery-optimization-test.md
index 1cad399007..2b6316d222 100644
--- a/windows/deployment/do/delivery-optimization-test.md
+++ b/windows/deployment/do/delivery-optimization-test.md
@@ -20,7 +20,7 @@ Delivery Optimization is a powerful and useful tool to help enterprises manage b
## Monitoring The Results
-Since Delivery Optimization is on by default, you'll be able to monitor the value either through the Windows Settings for ‘Delivery Optimization’, using Delivery Optimization PowerShell [cmdlets](waas-delivery-optimization-setup.md), and/or via the [Windows Update for Business Report](../update/wufb-reports-workbook.md) experience in Azure.
+Since Delivery Optimization is on by default, you'll be able to monitor the value either through the Windows Settings for ‘Delivery Optimization’, using Delivery Optimization PowerShell [cmdlets.](waas-delivery-optimization-setup.md), and/or via the [Windows Update for Business Report.](../update/wufb-reports-workbook.md) experience in Azure.
In the case where Delivery Optimization isn't working in your environment, it's important to investigate to get to the root of the problem. We recommend a test environment be created to easily evaluate typical devices to ensure Delivery Optimization is working properly. For starters, ‘Scenario 1: Basic Setup’ should be created to test the use of Delivery Optimization between two machines. This scenario is designed to eliminate any noise in the environment to ensure there's nothing preventing Delivery Optimization from working on the devices. Once you have a baseline, you can expand the test environment for more sophisticated tests.
@@ -28,15 +28,15 @@ In the case where Delivery Optimization isn't working in your environment, it's
The focus of the testing scenarios in this article is primarily centered on demonstrating the Delivery Optimization policies centered around the successful downloading of bytes using P2P. More specifically, the goal will be to show peer to peer is working as expected, using the following criteria:
-* Peers can find each other (for example on the same LAN / subnet / Group – matching your Download Mode policy).
-* Files are downloading in the expected Download Mode (validates connectivity to DO cloud, HTTP, and local configs).
+* Peers can find each other (for example on the same LAN / subnet / Group – matching your 'Download Mode' policy).
+* Files are downloading in the expected 'Download Mode' policy setting (validates connectivity to DO cloud, HTTP, and local configs).
* At least some downloads happening via P2P (validates connectivity between peers).
Several elements that influence overall peering, using Delivery Optimization. The most common, impactful environment factors should be considered.
* **The number of files in the cache and** **the** **number of devices have a big effect on overall peering.** There's a set number of files available for peering at a time, from each client, so the peering device may not be serving a particular file.
* **File size** **and** **internet connection** **reliability matter.** There's a Delivery Optimization setting to determine the minimum file size to use P2P. In addition, an internet connection must be open and reliable enough to let the Delivery Optimization client make cloud service API calls and download metadata files before starting a file download.
-* **Delivery Optimization Policies can play a role.** In general, it's important to familiarize yourself with the Delivery Optimization settings and defaults [Delivery Optimization reference - Windows Deployment | Microsoft Docs](waas-delivery-optimization-reference.md).
+* **Delivery Optimization Policies can play a role.** In general, it's important to familiarize yourself with the Delivery Optimization settings and defaults [Delivery Optimization reference - Windows Deployment | Microsoft Docs.](waas-delivery-optimization-reference.md).
### Delivery Optimization is a Hybrid P2P Platform
@@ -69,7 +69,7 @@ Machine 1 will download zero bytes from peers, Machine 2 will download 50 - 99%
|Pause Windows Updates | This controls the test environment so no other content is made available during the test, and potentially altering the outcome of the test. If there are problems and no peering happens, use 'Get-DeliveryOptimizationStatus' on the first machine to return a real-time list of the connected peers.
|Ensure all Store apps are up to date | This will help prevent any new, unexpected updates to download during testing.
|Delivery Optimization 'Download Mode' Policy | 2 (Group)(set on each machine)
-|Delivery Optimization 'GroupID' Policy | Set the *same* 'GUID' on each test machine. A GUID is a required value, which can be generated using PowerShell, ‘[[guid]::NewGuid()](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’.
+|Delivery Optimization 'GroupID' Policy | Set the *same* 'GUID' on each test machine. A GUID is a required value, which can be generated using PowerShell, ‘[[guid]::NewGuid().](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’.
|**Required on Windows 11 devices only** set Delivery Optimization 'Restrict Peer Selection' policy | 0-NAT (set on each machine). The default behavior in Windows 11 is set to '2-Local Peer Discovery'. For testing purposes, this needs to be scoped to the NAT.
#### Test Instructions
@@ -87,7 +87,7 @@ The following set of instructions will be used for each machine:
|Windows 10 | Windows 11
|--------|-------------------------------|
-||
+| :::image type="content" source="images/test-scenarios/win10/m1-basic-complete.png" alt-text="Windows 10 21H2 - Machine 1 - Basic Test." lightbox="images/test-scenarios/win10/m1-basic-complete.png"::: | :::image type="content" source="images/test-scenarios/win11/m1-basic-complete.png" alt-text="Windows 11 21H2 - Machine 1 - Basic Test." lightbox="images/test-scenarios/win11/m1-basic-complete.png"::: |
| **Observations** | |
| * No peers were found on the first machine downloading the content.
* 'TotalBytesDownloaded' is equal to the file size.
* Status is set to 'Caching' the content so future peers can use it.
* Download was happening in the foreground.
* DownloadMode is set to 'Group' and no peers were found.
* No distinct observations seen between Window 10 and Windows 11 devices.
@@ -99,7 +99,7 @@ The following set of instructions will be used for each machine:
|Windows 10 | Windows 11
|--------|--------------------------------|
-|||
+| :::image type="content" source="images/test-scenarios/win10/m2-basic-complete.png" alt-text="Windows 10 21H2 - Machine 2 - Basic Test." lightbox="images/test-scenarios/win10/m2-basic-complete.png"::: | :::image type="content" source="images/test-scenarios/win11/m2-basic-complete.png" alt-text="Windows 11 21H2 - Machine 2 - Basic Test." lightbox="images/test-scenarios/win11/m2-basic-complete.png":::|
| **Observations** | **Observations**|
| * A peer was found for the content and 87% of total bytes came from the peer.
* One peer was found for the piece of content, which is expected as there are only two devices in the peering group.
* Download mode was set to 'Group', but since group mode includes both LAN and Group devices, Delivery Optimization prioritizes LAN peers, if found. Therefore, 'BytesFromLanPeers' shows bytes where 'BytesFromGroupPeers' doesn't.
* 'DownloadDuration' is roughly the same between machines.|* A peer was found for the content and 90% of total bytes came from the peer.
* All other points are the same as Windows 10 results.
@@ -108,7 +108,7 @@ The following set of instructions will be used for each machine:
**Goal:**
Demonstrate how Delivery Optimization peer-to-peer technology works in a non-controlled environment, expanding to three machines
**Expected Results:**
-Machine 1 will download zero bytes from peers, Machine 2 will find a peers and download 50 - 99% from peers. Machine 3 will find two peers and download 50 - 99% from peers.
+Machine 1 will download zero bytes from peers, Machine 2 will find peers and download 50 - 99% from peers. Machine 3 will find two peers and download 50 - 99% from peers.
#### Test Machine Setup
@@ -121,7 +121,7 @@ Machine 1 will download zero bytes from peers, Machine 2 will find a peers and d
|Disk size|127 GB
|Network | Connected to same network, one that is representative of the corporate network.
|Delivery Optimization 'Download Mode' Policy| 2 (Group)(set on each machine)
-|Delivery Optimization 'Group ID' Policy| Set the *same* 'GUID' on each test machine. A GUID is required value, which can be generated using PowerShell, ‘[[guid]::NewGuid()](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’
+|Delivery Optimization 'Group ID' Policy| Set the *same* 'GUID' on each test machine. A GUID is required value, which can be generated using PowerShell, ‘[[guid]::NewGuid().](https://blogs.technet.microsoft.com/heyscriptingguy/2013/07/25/powertip-create-a-new-guid-by-using-powershell/)’
|Delivery Optimization 'Delay background download from http' Policy | 60 (set on each machine)
|Delivery Optimization 'Delay foreground download from http Policy |60 (set on each machine)
@@ -139,7 +139,7 @@ The following set of instructions will be used for each machine:
**Output: Windows 10 (21H2)**
-
+
**Observations**
@@ -155,7 +155,7 @@ The following set of instructions will be used for each machine:
**Output** Windows 10 (21H2)
-
+
**Observations**
@@ -170,7 +170,7 @@ The following set of instructions will be used for each machine:
**Output:** Windows 10 (21H2)
-
+
**Observations**
@@ -186,19 +186,19 @@ As mentioned, the distributed nature of the Delivery Optimization technology is
'BytesToPeers' sourced from Machine 1 are '5704426044'. This represents the total number of bytes, downloaded by the two peers in the group.
-
+
**Output:** Machine 2
'BytesToPeers' sourced from Machine 2 are '1899143740'. When there are two peers in the group with bytes available, notice that the distribution of bytes comes from either Machine 1 or Machine 2.
-
+
**Output:** Machine 3
'BytesToPeers' sourced from Machine 3 are '0'. This means that no other peers are downloading bytes from this peer, which is expected since it was the last machine in the group.
-
+
## Conclusion
@@ -206,4 +206,4 @@ Using Delivery Optimization can help make a big impact in customer environments
The testing scenarios found in this document help to show a controlled test environment, helping to prevent updates from interrupting the peering results. The other, a more real-world case, to demonstrate how content available across peers will both be used as the source of the content.
-If there are issues found while testing, the Delivery Optimization PowerShell [cmdlets](waas-delivery-optimization-setup.md) can be a helpful tool to help explain what is happening in the environment.
+If there are issues found while testing, the Delivery Optimization PowerShell [cmdlets.](waas-delivery-optimization-setup.md) can be a helpful tool to help explain what is happening in the environment.
diff --git a/windows/deployment/do/images/test-scenarios/Win10/M1-Adv-BytesToPeers.png b/windows/deployment/do/images/test-scenarios/Win10/m1-adv-bytes-to-peers.png
similarity index 100%
rename from windows/deployment/do/images/test-scenarios/Win10/M1-Adv-BytesToPeers.png
rename to windows/deployment/do/images/test-scenarios/Win10/m1-adv-bytes-to-peers.png
diff --git a/windows/deployment/do/images/test-scenarios/Win10/M2-Adv-BytesToPeers.PNG b/windows/deployment/do/images/test-scenarios/Win10/m2-adv-bytes-to-peers.png
similarity index 100%
rename from windows/deployment/do/images/test-scenarios/Win10/M2-Adv-BytesToPeers.PNG
rename to windows/deployment/do/images/test-scenarios/Win10/m2-adv-bytes-to-peers.png
diff --git a/windows/deployment/do/images/test-scenarios/Win10/M3-Adv-BytesToPeers.PNG b/windows/deployment/do/images/test-scenarios/Win10/m3-adv-bytes-to-peers.png
similarity index 100%
rename from windows/deployment/do/images/test-scenarios/Win10/M3-Adv-BytesToPeers.PNG
rename to windows/deployment/do/images/test-scenarios/Win10/m3-adv-bytes-to-peers.png