From 7ce3fb5968d96752f4b41df03464e2c5bd6d59e5 Mon Sep 17 00:00:00 2001
From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
Date: Wed, 14 Aug 2024 19:05:40 +0200
Subject: [PATCH] PR feedback

Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com>
---
 content/_index.md | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/content/_index.md b/content/_index.md
index 06d867e8..7b54de46 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -99,10 +99,7 @@ services - be that for instant messages, VoIP call setups, or any other
 objects that need to be reliably and persistently pushed from A to B in
 an interoperable and federated manner.
 
-### Bindingness of requirements
-
-As a standards document, the Matrix Spec needs to signify the bindingness of the
-individual features, APIs, procedures, or other requirements it describes.
+### Requirement levels
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" across all parts of the
@@ -110,10 +107,11 @@ specification are to be interpreted as described in
 [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
 
 Some entire sections of the specification might be optional depending on the
-circumstances, for example the
-[modules of the client-server API](/client-server-api/#modules) apply depending
-on the use case. The bindingness of the above key words appearing in such a
-section is only relevant if the section itself is applicable.
+circumstances. For example, the
+[modules of the client-server API](/client-server-api/#modules)
+apply depending on the use case. The requirement level expressed by the above
+key words appearing in such a section is only relevant if the section itself is
+applicable.
 
 ### Spec Change Proposals