diff --git a/doc/img/testing-log.dot.svg b/doc/img/testing-log.svg
similarity index 100%
rename from doc/img/testing-log.dot.svg
rename to doc/img/testing-log.svg
diff --git a/doc/img/testing-phy.dot.svg b/doc/img/testing-phy.svg
similarity index 100%
rename from doc/img/testing-phy.dot.svg
rename to doc/img/testing-phy.svg
diff --git a/doc/test-arch.md b/doc/test-arch.md
index dd8437b9..04f63c5d 100644
--- a/doc/test-arch.md
+++ b/doc/test-arch.md
@@ -108,7 +108,7 @@ DHCP server, and the other two as DHCP clients - with all three having
 a management connection to the host PC running the test.  In other
 words, the test requires a _logical_ topology like the one below.
 
-<img align="right" src="img/testing-log.dot.svg" alt="Example Logical Topology">
+![Example Logical Topology](img/testing-log.svg){ align=right width="360" }
 
 ```dot
 graph "dhcp-client-server" {
@@ -155,7 +155,7 @@ degrees), we can deploy well-known algorithms to find such subgraphs.
 Continuing our example, let's say we want to run our DHCP test on the
 _physical_ topology below.
 
-<img align="right" src="img/testing-phy.dot.svg" alt="Example Physical Topology">
+![Example Physical Topology](img/testing-phy.svg){ align=right width="360" }
 
 ```dot
 graph "quad-ring" {