From 967eb884d59c39db6c2424d9ebd9803e7679c1d1 Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Thu, 30 Mar 2023 19:25:20 +0100
Subject: [PATCH] figure fix

---
 handbook/troggle/trogdjango.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/handbook/troggle/trogdjango.html b/handbook/troggle/trogdjango.html
index 989afcf55..e8d16b56d 100644
--- a/handbook/troggle/trogdjango.html
+++ b/handbook/troggle/trogdjango.html
@@ -28,9 +28,12 @@ note that the suffix on a name '<a href="https://docs.djangoproject.com/en/dev/t
 
 <li>Django has a good process for migrating both the python code and the SQL database to later versions of Django via <a href="https://docs.djangoproject.com/en/dev/topics/migrations/">'migrations'</a>. Note that even though Expo imports all the data from files and its database is ephemeral (but it is intensely used for cross-referencing), the database schema still needs to be migrated. 
 </ul>
+
 <h4>Django versions and deprecation</h4>
+
 <a href="https://www.djangoproject.com/download#supported-versions">
-<img  border="1" class="onright" width="250px" src='release-roadmap.3c7ece4f31b3.png'/></a></a>
+<img  border="1" class="onright" width="250px" src='django-v3.2-6.0-schedule.jpg'/></a>
+
 <ul>
 <li>Django has a mature and reliable release programme: <a href="https://docs.djangoproject.com/en/dev/releases/">docs.djangoproject.com<wbr>/en/<wbr>dev/<wbr>releases/</a>
 <li>Django pre-announces which features will be deprecated: <a href="https://docs.djangoproject.com/en/dev/internals/deprecation/">docs.djangoproject.com<wbr>/en/<wbr>dev/<wbr>internals/<wbr>deprecation/</a>