diff --git a/docs/guide/hpc/devito-virtual-machine-content.md b/docs/guide/hpc/devito-virtual-machine-content.md
index dc4a691450..329f189e5e 100644
--- a/docs/guide/hpc/devito-virtual-machine-content.md
+++ b/docs/guide/hpc/devito-virtual-machine-content.md
@@ -7,11 +7,13 @@ Devito is a functional language that you can implement as a Python package. With
 The following diagram shows a single-node architecture:
 
 :::image type="content" source="./media/hpc-devito-single-node.svg" alt-text="Diagram that shows the single-node architecture." lightbox="./media/hpc-devito-single-node.svg" border="false":::
+
 *Download a [Visio file](https://arch-center.azureedge.net/hpc-devito-single.vsdx) of this architecture.*
 
 The following diagram shows a multi-node architecture:
 
 :::image type="content" source="./media/hpc-devito-multi-node.svg" alt-text="Diagram that shows the multi-node architecture." lightbox="./media/hpc-devito-multi-node.svg" border="false":::
+
 *Download a [Visio file](https://arch-center.azureedge.net/hpc-devito-multi-node.vsdx) of this architecture.*
 
 ### Components
@@ -121,6 +123,8 @@ The following table shows the results for the CentOS-based 8.1 HPC image:
 | 96 | 132.86 | 293.25 | 1.39 |
 | 120 | 149.99 | 259.78 | 1.23 |
 
+:::image type="content" source="./media/speed-increase-graph-hbv3.png" alt-text="Graph that shows the relative speed increase for a HBv3-series VM.":::
+
 Note that for the single-node tests, the Devito operator is run on all HBv3-series VM configurations. The Standard_HB120-16rs_v3 VM runtime is used as the baseline to calculate the relative speed increase.
 
 #### Devito performance on a cluster (multi-node)
@@ -136,6 +140,8 @@ The following table shows the results for a cluster with 64 vCPUs per node:
 | 4 | 256 | 60.77 | 641.30 | 2.00 |
 | 8 | 512 | 51.94 | 750.40 | 2.34 |
 
+:::image type="content" source="./media/speed-increase-graph-64.png" alt-text="Graph that shows the relative speed increase for a 64-vCPU node.":::
+
 The following table shows the results for a cluster with 96 vCPUs per node:
 
 | VM configuration | Number of nodes | Number of vCPUs (cores) | Forward operator runtime (in seconds) | GFLOPS/second | Relative speed increase |
@@ -145,6 +151,8 @@ The following table shows the results for a cluster with 96 vCPUs per node:
 | Standard_HB120-96rs_v3 | 4 | 384 | 75.11 | 518.93 | 1.83 |
 | Standard_HB120-96rs_v3 | 8 | 768 | 69.38 | 561 | 1.98 |
 
+:::image type="content" source="./media/speed-increase-graph-96.png" alt-text="Graph that shows the relative speed increase for a 96-vCPU node.":::
+
 ## Azure cost
 
 The following table presents the wall-clock times for running the simulations. You can multiply these times by the Azure VM hourly costs for HB120rs_v3-series VMs to calculate costs. For the current hourly costs, see [Linux virtual machines pricing](https://azure.microsoft.com/pricing/details/virtual-machines/linux).
diff --git a/docs/guide/hpc/media/speed-increase-graph-64.png b/docs/guide/hpc/media/speed-increase-graph-64.png
new file mode 100644
index 0000000000..6eca97773a
Binary files /dev/null and b/docs/guide/hpc/media/speed-increase-graph-64.png differ
diff --git a/docs/guide/hpc/media/speed-increase-graph-96.png b/docs/guide/hpc/media/speed-increase-graph-96.png
new file mode 100644
index 0000000000..e8134dd201
Binary files /dev/null and b/docs/guide/hpc/media/speed-increase-graph-96.png differ
diff --git a/docs/guide/hpc/media/speed-increase-graph-hbv3.png b/docs/guide/hpc/media/speed-increase-graph-hbv3.png
new file mode 100644
index 0000000000..67baf773b4
Binary files /dev/null and b/docs/guide/hpc/media/speed-increase-graph-hbv3.png differ