From 734be5165bd9ddddf1d5d86e6fdf55a93800e561 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Fri, 4 Dec 2020 14:46:11 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Kitsune Ral --- specification/appendices/identifier_grammar.rst | 2 +- specification/proposals_intro.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/specification/appendices/identifier_grammar.rst b/specification/appendices/identifier_grammar.rst index d9e56714..f8b2aef5 100644 --- a/specification/appendices/identifier_grammar.rst +++ b/specification/appendices/identifier_grammar.rst @@ -379,7 +379,7 @@ are picked is left as an implementation detail, however the current recommendati to pick 3 unique servers based on the following criteria: * The first server should be the server of the highest power level user in the room, - provided they are at least power level 50. If no user meets these criteria, pick the + provided they are at least power level 50. If no user meets this criterion, pick the most popular server in the room (most joined users). The rationale for not picking users with power levels under 50 is that they are unlikely to be around into the distant future while higher ranking users (and therefore servers) are less likely diff --git a/specification/proposals_intro.rst b/specification/proposals_intro.rst index a54f7bca..4749457b 100644 --- a/specification/proposals_intro.rst +++ b/specification/proposals_intro.rst @@ -383,7 +383,7 @@ unclear if an MSC will require an implementation proof, ask in `#matrix-spec:mat `_. Early release of an MSC/idea -~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To help facilitate early releases of software dependent on a spec release, implementations are required to use the following process to ensure that the official Matrix namespace