diff --git a/handbook/troggle/legacy-replace.jpg b/handbook/troggle/legacy-replace.jpg
new file mode 100644
index 000000000..b84eaf68d
Binary files /dev/null and b/handbook/troggle/legacy-replace.jpg differ
diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index 77d19e121..b59f137ba 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -7,6 +7,7 @@
 </head>
 <body>
 <style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
+<style>figure {font-weight: bold; font-size: small; font-family: sans-serif;font-variant-caps: small-caps;}</style>
 <h2 id="tophead">CUCC Expedition Handbook</h2>
 <h1>Troggle in 2025-2030</h1>
 
@@ -24,6 +25,18 @@ there is such a lot going on we would create a large volume of software even if
   <h3>[ Update March 2024 ]</h3>
 "Legacy displacement" is now a fairly mature part of software engineering, though most computer science graduates won't have heard of it. There are standard ways of partially and incrementally retiring old systems and replacing them, while maintaining a live service to users throughout. See <a href="https://martinfowler.com/articles/patterns-legacy-displacement/">Legacy Displacement</a>.
 
+<div class="onright">
+<figure  >
+<a href="https://martinfowler.com/articles/patterns-legacy-displacement/">
+<img width=350 src="legacy-replace.jpg"></a>
+<br><figcaption>Legacy Replacement underway</figcaption>
+</figure>
+</div>
+
+
+
+</a>
+
 <h3>Option 2</h2>
 <p>
 We keep the same architecture as now, and incrementally replace modules that use django/SQL with direct object storage of collections using pickle(), shelve() and json().
