From d89166a16fac5d5fafb746b56762c7f4f1515a4b Mon Sep 17 00:00:00 2001
From: NewSoupVi <57900059+NewSoupVi@users.noreply.github.com>
Date: Thu, 5 Sep 2024 12:33:46 +0200
Subject: [PATCH] Update world maintainer.md

---
 docs/world maintainer.md | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/docs/world maintainer.md b/docs/world maintainer.md
index 0d70d46dea..a6d571897f 100644
--- a/docs/world maintainer.md	
+++ b/docs/world maintainer.md	
@@ -30,15 +30,13 @@ nominate someone else (i.e. there are multiple devs).
 
 ### Being added as a maintainer to an existing implementation
 
-At any point, a world maintainer can authorize the addition of another world maintainer to their world.  
+At any point, a world maintainer can approve the addition of another world maintainer to their world.  
 This can be done through an update of the [CODEOWNERS](/docs/CODEOWNERS) document.  
 Specifically, one of the involved parties should open a pull request with a change to this document. This PR must be
-approved by all existing maintainers of the world, the new world maintainer candidate, and one core maintainer.
+approved by all existing maintainers of the world and the new world maintainer candidate.  
+Finally, the PR must be approved by one core maintainer. It is recommended that you add some information to the PR
+description about what contributions the new world maintainer has made to help the core maintainer make this final call.
 
-This should usually be a quick process, but core reserves its right to make their own assessment.  
-For example, adding 5 people who we have never heard of might raise some questions.  
-Adding some information to the PR description about contributions the new world maintainer candidate has made should
-help in this regard.
 
 ### Getting Voted