diff --git a/content/ci/actions.md b/content/ci/actions.md
index a8ee317..1a74d40 100644
--- a/content/ci/actions.md
+++ b/content/ci/actions.md
@@ -49,7 +49,7 @@ determine where your Runner will accept workflows from.
 
 ## Installing Forgejo Runner
 
-For the installation of the runner, see the [Forgejo documentation](https://forgejo.org/docs/next/admin/actions/runner-installation/).
+For the installation of the runner, see the [Forgejo documentation](https://forgejo.org/docs/latest/admin/actions/runner-installation/).
 
 ## References
 
diff --git a/content/codeberg-pages/forgejo-actions.md b/content/codeberg-pages/forgejo-actions.md
index fceb7c6..8be884c 100644
--- a/content/codeberg-pages/forgejo-actions.md
+++ b/content/codeberg-pages/forgejo-actions.md
@@ -44,7 +44,7 @@ The `token` will automatically be filled by Forgejo Actions with a secret token,
 
 If you use branches to test out new features, write draft blog posts, etc., you should either limit the whole workflow, or this step only, to pushes to a default branch (usually `main` or `master`) to ensure that only finalized content is published to your site.
 
-To do this, either add a [`on.push.branches` list](https://forgejo.org/docs/next/user/actions/reference/#onpush) to the whole workflow, or add [an `if` condition to the step](https://forgejo.org/docs/next/user/actions/reference/#jobsjob_idstepsif-1) (or [to the whole job](https://forgejo.org/docs/next/user/actions/reference/#jobsjob_idif)) like this:
+To do this, either add a [`on.push.branches` list](https://forgejo.org/docs/latest/user/actions/reference/#onpush) to the whole workflow, or add [an `if` condition to the step](https://forgejo.org/docs/latest/user/actions/reference/#jobsjob_idstepsif-1) (or [to the whole job](https://forgejo.org/docs/latest/user/actions/reference/#jobsjob_idif)) like this:
 
 {% raw %}