From f0735cece2e137ba794895b5a7d867a0595e3e62 Mon Sep 17 00:00:00 2001
From: Michael Zetune <30369272+MichaelZetune@users.noreply.github.com>
Date: Thu, 23 Feb 2023 16:01:53 -0500
Subject: [PATCH] Fix release link on releasing.md

---
 docs/contributor-guide/developer-guide/releasing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/contributor-guide/developer-guide/releasing.md b/docs/contributor-guide/developer-guide/releasing.md
index d80dd232..6f6e5a10 100644
--- a/docs/contributor-guide/developer-guide/releasing.md
+++ b/docs/contributor-guide/developer-guide/releasing.md
@@ -1,6 +1,6 @@
 # Releasing
 
-See [Upgrading to a New Release](it-manual/sre-playbook/upgrading-to-a-new-release.md) for an overview of CiviForm release practices.
+See [Upgrading to a New Release](https://docs.civiform.us/it-manual/sre-playbook/upgrading-to-a-new-release) for an overview of CiviForm release practices.
 
 Releases are created weekly by the on-call engineer on Wednesday before 12pm. The on-call engineer may use the production meeting time to create the release if desired. Out-of-schedule releases may be created if requested by a civic entity (e.g. for an urgent bugfix).