Use release-notes.md for sanity check

doc/5.x-final.md

@@ -20,7 +20,7 @@ git push origin 5.X
 * Check regressions/criticals in Gitlab:
     * https://lab.civicrm.org/groups/dev/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=regression
     * https://lab.civicrm.org/groups/dev/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=prioritised
-* Check release notes: https://github.com/civicrm/civicrm-core/tree/5.X/release-notes
+* Check release notes: https://github.com/civicrm/civicrm-core/blob/5.X/release-notes.md
 * In Jenkins, review the scheduled tests for `5.X` and determine if anything should block the release.
     * https://test.civicrm.org/job/CiviCRM-Core-Matrix/
     * https://test.civicrm.org/job/CiviCRM-Ext-Matrix/

doc/5.x-patch.md

@@ -28,7 +28,7 @@ git push origin 5.X
 ## 3: Sanity checks
 
 * Check open PRs for `5.X`: https://github.com/civicrm/civicrm-core/pulls
-* Check release notes: https://github.com/civicrm/civicrm-core/tree/5.X/release-notes
+* Check release notes: https://github.com/civicrm/civicrm-core/blob/5.X/release-notes.md
 * In Jenkins, review the scheduled tests for `5.X` and determine if anything should block the release.
     * https://test.civicrm.org/job/CiviCRM-Core-Matrix/
     * https://test.civicrm.org/job/CiviCRM-Ext-Matrix/