diff --git a/doc/HWReleaseProcess.md b/doc/HWReleaseProcess.md
index 7f21ee6..716fd03 100644
--- a/doc/HWReleaseProcess.md
+++ b/doc/HWReleaseProcess.md
@@ -19,7 +19,7 @@
 
 ## Major Releases
 
-1. Before finalizing an RTL release, the hardware team will follow the procedure described in [CaliptraReleaseChecklist.md](https://github.com/chipsalliance/caliptra-rtl/blob/cc37991e50f9213219d13f2e0d99b0ba5c7460e0/docs/CaliptraReleaseChecklist.md).
+1. Before finalizing an RTL release, the hardware team will follow the procedure described in [CaliptraReleaseChecklist.md](https://github.com/chipsalliance/caliptra-rtl/blob/main/docs/CaliptraReleaseChecklist.md).
   - Upon finalizing all release checklist items, the hardware team will generate a release tag on the RTL **main** branch, following the naming convention `v<major>.<minor>`.
   - When this is completed, the RTL team will create a new branch following the naming convention `patch_v<major>.<minor>`. This branch will exactly match the contents of the major release tag. Any future fixes that must be applied as patches to this release version will be committed to the `patch_v<major>.<minor>` branch. Branch **main** will continue to receive updated code for the subsequent planned release, and is not guaranteed to contain a valid release except as tagged.
 2. The software team will follow the [submodule update steps](#RTL-Submodule-Pointer-Update) to revise the RTL submodule pointer to consume the code from branch `patch_v<major>.<minor>` instead of from branch **main**.