diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index fd0aa1a..375d829 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -1,11 +1,18 @@
 # Laminas Project Maintainers
 
+Maintainers are trusted contributors who have GitHub's `maintainer` rights to one or more repositories under our GitHub organizations.
+
+Beyond driving fixes/improvements, we expect maintainers to:
+
+- Ensure project continuity, quality, and consistency
+- Review and merge relevant code modifications
+- Triage issues
+- Release new versions
+- Participate in technical discussions and decision-making
+
 We aim to have 2+ maintainers per repository.
-Maintainers have GitHub maintainer rights to the repository(ies) they maintain, which means the ability to push code to the repository, manage issues and pull requests, and manipulate selected repository settings.
 
-To become a maintainer, you must first have another maintainer or a TSC member nominate you to the TSC.
-Nominations are done by submitting an issue to this repository with a title prefix of `[NOMINATION][MAINTAINER]` (or select the "Maintainer Nomination" issue type when creating an issue on this repository).
-Maintainers are approved by a majority vote of the TSC, which will be held no later than 1 week following the nomination.
+## Current maintainers
 
 Current maintainers are found on the Teams page of each organization, on a team matching the repository name:
 
@@ -13,6 +20,20 @@ Current maintainers are found on the Teams page of each organization, on a team
 - [Laminas API Tools organization teams](https://github.com/orgs/laminas-api-tools/teams)
 - [Mezzio organization teams](https://github.com/orgs/mezzio/teams)
 
+## Becoming a Maintainer
+
+### Requirements
+
+- Consistent high-quality contributions (code changes, reviews, discussions, etc) over time
+- Demonstrated understanding of project goals and coding standards
+- Active participation in discussions and issue resolution
+
+### Process
+
+To become a maintainer, you must first have another maintainer or a TSC member nominate you to the TSC.
+Nominations are done by submitting an issue to this repository with a title prefix of `[NOMINATION][MAINTAINER]` (or select the "Maintainer Nomination" issue type when creating an issue on this repository).
+Maintainers are approved by a majority vote of the TSC, which will be held no later than 1 week following the nomination.
+
 ## Maintainers Guide
 
 This guide is intended for *maintainers* — anybody with commit access to one or more Laminas Project repositories.
@@ -185,7 +206,7 @@ Examples of scenarios where notes should be added:
 
 Releases are automatically performed by closing a milestone.
 **DO NOT** close the milestone without first closing all related issues and pull requests.
-The [automatic-releases workflow](https://github.com/laminas/automatic-releases) will fail in that scenario, and you will need to re-opend and re-close the milestone in order to create the release.
+The [automatic-releases workflow](https://github.com/laminas/automatic-releases) will fail in that scenario, and you will need to re-open and re-close the milestone in order to create the release.
 
 The automatic-releases workflow: