diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0643e9a86f..66bb31ea88 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -57,7 +57,7 @@ Regardless of your familiarity with this project, documentation help is always
 appreciated.
 
 Once you found an issue that interests you, post a comment to the issue, asking
-the maintainers to assign it to you.
+the [maintainers](MAINTAINERS.md) to assign it to you.
 
 ### Coding Standard
 
@@ -131,7 +131,7 @@ In general, smaller pull requests are easier to review and merge than bigger
 ones. It's always a good idea to collaborate with the maintainers to determine
 how best to break up a big pull request.
 
-Once the maintainers approve your PR, they will label it as `kueue`. The
+Once the [maintainers](MAINTAINERS.md) approve your PR, they will label it as `kueue`. The
 `mergify` bot will then squash the commits in your PR, and add it to the merge
 queue. The bot will auto-merge your work when it's ready.
 
diff --git a/README.md b/README.md
index 1c6760a05b..d0eb256a65 100644
--- a/README.md
+++ b/README.md
@@ -86,7 +86,7 @@ If you have any questions or run into issues, feel free to reach out to us on
 GitHub issues or pull requests that have been inactive for more than 60 days
 will be labeled as stale. If they remained inactive for another 30 days, they
 will be automatically closed. To be exempted from the issue lifecycle, discuss
-with a maintainer the reasons behind the exemption, and add the `frozen` label
+with a [maintainer](MAINTAINERS.md) the reasons behind the exemption, and add the `frozen` label
 to the issue or pull request.
 
 If you discovered any security issues, refer to our [`SECURITY.md`](SECURITY.md)
diff --git a/SECURITY.md b/SECURITY.md
index 980e40efa6..54c1b16a07 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -9,7 +9,7 @@ You can report a new vulnerability using
 
 Alternatively you can report it via kanisterio google group "Contact owners and managers" button: https://groups.google.com/g/kanisterio/about
 
-The maintainers will help diagnose the severity of the issue and determine how
+The [maintainers](MAINTAINERS.md) will help diagnose the severity of the issue and determine how
 to address the issue. Issues deemed to be non-critical will be filed as GitHub
 issues. Critical issues will receive immediate attention and be fixed as quickly
 as possible. The maintainers will then coordinate a release date with you.
diff --git a/releasenotes/README.md b/releasenotes/README.md
index fc5389c99f..238ea23fa4 100644
--- a/releasenotes/README.md
+++ b/releasenotes/README.md
@@ -18,7 +18,7 @@ When reviewing a PR, a reviewer should check if there are release notes added if
 
 ## Generating changelogs
 
-Changelogs would be generated for each release by maintainers as a part of the release process.
+Changelogs would be generated for each release by [maintainers](../MAINTAINERS.md) as a part of the release process.
 
 Changelog can be generated using: