Spec for MSC4312: Resetting cross-signing keys in the OAuth world

Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>

changelogs/client_server/newsfragments/2227.clarification

@@ -1 +0,0 @@
-Fix various typos throughout the specification.

changelogs/client_server/newsfragments/2233.clarification

@@ -1 +0,0 @@
-Add `m.login.terms` to enumeration of authentication types.

changelogs/internal/newsfragments/2238.clarification

@@ -1 +0,0 @@
-Silence failing redocly-cli rule.

content/client-server-api/_index.md

@@ -906,7 +906,6 @@ This specification defines the following auth types:
 -   `m.login.msisdn`
 -   `m.login.dummy`
 -   `m.login.registration_token`
--   {{% added-in v="1.11" %}} `m.login.terms`
 -   {{% added-in v="1.17" %}} `m.oauth`
 
 ###### Password-based

content/client-server-api/modules/rich_replies.md

@@ -20,9 +20,9 @@ Previously, a rich reply could only reference another `m.room.message` event.
 {{% boxes/note %}}
 {{% changed-in v="1.13" %}}
 In previous versions of the specification, rich replies could include a fallback
-representation of the original message in the `body` (using a prefix sequence)
-and `formatted_body` (using a custom HTML element) for clients that do not
-support rich replies. This is no longer the case, but clients SHOULD still
+representation of the original message message in the `body` (using a prefix
+sequence) and `formatted_body` (using a custom HTML element) for clients that do
+not support rich replies. This is no longer the case, but clients SHOULD still
 remove this fallback before rendering the event.
 
 To strip the fallback on the `body`, the client should iterate over each

redocly.yaml

@@ -9,6 +9,3 @@ rules:
   no-path-trailing-slash: off
   operation-2xx-response: off
   spec-strict-refs: error
-  # $ref in examples are not spec-compliant, yet we find them useful. Disable this rule
-  # and instead check example schema using `check-event-schema-examples.py`
-  no-invalid-schema-examples: off