diff --git a/handbook/troggle/trogdjango.html b/handbook/troggle/trogdjango.html
index 30e90441d..8ae267f33 100644
--- a/handbook/troggle/trogdjango.html
+++ b/handbook/troggle/trogdjango.html
@@ -40,8 +40,11 @@
 <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>
 <li>Django release schedule: <a href="https://www.djangoproject.com/download/">supported versions timetable</a>
 <li>Significant new Django versions are released every 8 months. Deprecated features after removed after the two subsequent versions.
+  <li>There is now a long history of very reliable and non-breaking version upgrades. <a href="https://www.djangoproject.com/weblog/2025/nov/19/twenty-years-of-django-releases/">This is what decades’ worth of a stable framework looks like</a>.
 </ul>
-<p>This may seem overly pedantic and heavyweight, but this is exactly what we need when we are supporting software over decades. When we use software in troggle which is not so well organised, we really feel the pain.
+<p>This may seem overly pedantic and heavyweight, but 
+  <b><em>this is exactly what we need</em></b>
+ when we are supporting software over decades. When we use software in troggle which is not so well organised, we really feel the pain.
 
 <h4>Django plugins</h4>
 <p>We do not just use our own code and django. We also use django plugins (known as "apps") too. These can do such things as  image re-sizing, user authentication with captchas, PayPal processing or mailing list integration. Unfortunately django plugins are volunteer efforts and do not have the same defined update management process as django itself, so release schedules are rather random. They cause merry hell when upgrading troggle to use a new version of django.