diff --git a/libsigner/release-process.md b/libsigner/release-process.md
index 57ebf2c4b..599d8c7af 100644
--- a/libsigner/release-process.md
+++ b/libsigner/release-process.md
@@ -46,7 +46,7 @@ For example, if there is a stacks-core release of 2.6.0.0.0, `stacks-signer` wil
 
 1. The release must be timed so that it does not interfere with a _prepare
    phase_. The timing of the next Stacking cycle can be found
-   [here](https://stx.eco/dao/tools). A release should happen
+   [here](https://stx.eco/dao/tools?tool=2). A release should happen
    at least 48 hours before the start of a new cycle, to avoid interfering
    with the prepare phase.
 
@@ -82,4 +82,4 @@ For example, if there is a stacks-core release of 2.6.0.0.0, `stacks-signer` wil
    page. Announcements will then be shared in the `#stacks-core-devs` channel in the
    Stacks Discord, as well as the [mailing list](https://groups.google.com/a/stacks.org/g/announce).
 
-9. Finally, the release branch `release/signer-X.Y.Z.A.n.x` will be PR'ed into the `master` branch, and once merged, a PR for `master->develop` will be opened. 
\ No newline at end of file
+9. Finally, the release branch `release/signer-X.Y.Z.A.n.x` will be PR'ed into the `master` branch, and once merged, a PR for `master->develop` will be opened.