chore: update menu of RESPONSIBILITIES.md

Signed-off-by: Pierre-Yves Lapersonne <pierreyves.lapersonne@orange.com>

Author: pylapp

.github/RESPONSIBILITIES.md

@@ -2,27 +2,17 @@
 - [Current Maintainers](#current-maintainers)
 - [Maintainer Responsibilities](#maintainer-responsibilities)
   - [Uphold Code of Conduct](#uphold-code-of-conduct)
-  - [Prioritize Security](#prioritize-security)
   - [Review Pull Requests](#review-pull-requests)
   - [Triage Open Issues](#triage-open-issues)
     - [Automatically Label Issues](#automatically-label-issues)
   - [Be Responsive](#be-responsive)
   - [Maintain Overall Health of the Repo](#maintain-overall-health-of-the-repo)
     - [Keep Dependencies up to Date](#keep-dependencies-up-to-date)
-  - [Manage Roadmap](#manage-roadmap)
-  - [Add Continuous Integration Checks](#add-continuous-integration-checks)
   - [Use Semver](#use-semver)
   - [Release Frequently](#release-frequently)
   - [Promote Other Maintainers](#promote-other-maintainers)
   - [Describe the Repo](#describe-the-repo)
 - [Becoming a Maintainer](#becoming-a-maintainer)
-  - [Nomination](#nomination)
-  - [Interest](#interest)
-  - [Addition](#addition)
-- [Removing a Maintainer](#removing-a-maintainer)
-  - [Moving On](#moving-on)
-  - [Inactivity](#inactivity)
-  - [Negative Impact on the Project](#negative-impact-on-the-project)
 
 ## Overview
 
@@ -90,5 +80,4 @@ Make sure the repo has a well-written, accurate, and complete description.
 
 ### Becoming or not a Maintainer
 
-The repository admins, seens as top maintainer, are the only ones able to choose whether or not somebody can be named as maintainer, in the way they want.
-
+The repository admins, seens as top maintainer, are the only ones able to choose wether or not somebody can be named as maintainer, in the way they want.