From 48a1322964f10f3f9ca7cdccddbbbded6b2f3e7a Mon Sep 17 00:00:00 2001
From: richvdh <richvdh@users.noreply.github.com>
Date: Tue, 21 Dec 2021 18:12:53 +0000
Subject: deploy: 9ec46d6231c267a1aa25c96b5d86822c7da8fca9

---
 latest/deprecation_policy.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'latest/deprecation_policy.html')

diff --git a/latest/deprecation_policy.html b/latest/deprecation_policy.html
index aeaeebc548..a8076c06bf 100644
--- a/latest/deprecation_policy.html
+++ b/latest/deprecation_policy.html
@@ -191,8 +191,8 @@ drop support for versions in the future.</p>
 i.e. when a version reaches End of Life Synapse will withdraw support for that
 version in future releases.</p>
 <p>Details on the upstream support life cycles for Python and PostgreSQL are
-documented at https://endoflife.date/python and
-https://endoflife.date/postgresql.</p>
+documented at <a href="https://endoflife.date/python">https://endoflife.date/python</a> and
+<a href="https://endoflife.date/postgresql">https://endoflife.date/postgresql</a>.</p>
 <h2 id="context"><a class="header" href="#context">Context</a></h2>
 <p>It is important for system admins to have a clear understanding of the platform
 requirements of Synapse and its deprecation policies so that they can
-- 
cgit 1.5.1