diff --git a/scrbl/rktwebviewqt-internals.scrbl b/scrbl/rktwebviewqt-internals.scrbl
index c5e7edb..dbaf6a1 100644
--- a/scrbl/rktwebviewqt-internals.scrbl
+++ b/scrbl/rktwebviewqt-internals.scrbl
@@ -1,4 +1,5 @@
 #lang scribble/manual
+@(require racket/runtime-path)
 
 @title{Qt WebView Backend Architecture}
 @author[@author+email["Hans Dijkema" "hans@dijkewijk.nl"]]
@@ -8,8 +9,14 @@
 It would, of course, be preferable to place everything within a single process,
 under a unified structure. This would be elegant. It is not how things are.
 
+@(define-runtime-path img-path ".")
+@(define img (path->string (build-path img-path
+                                       "rktwebview-shared-memory-diagram-simple.svg"
+                                       )))
+@(displayln (format "image: '~a'"  img))
+
 @centered{
-  @image[#:scale 0.45]{rktwebview-shared-memory-diagram-simple.svg}
+  @image[#:scale 0.45]{@img}
 }
 
 Qt WebEngine establishes its own order: threads, event loops, internal state.