docs: correct misreadable and factually wrong reference prose (#2587)

This commit is contained in:
Hampus authored and GitHub committed 2026-09-08 15:36:50 +02:00
1 parent 43924e3ac5
commit 08c9fe9886
26 files changed
+37 -37

No files matched your search

@@ -58,7 +58,7 @@ An unrecognised scope value is rejected when the authorisation request is comple
Scope order has no semantic meaning, so a client MUST compare scopes as a set.
:::
The `scope` string of an [OAuth2 token](#oauth2-token-object) and of an [OAuth2 introspection](#oauth2-introspection-object) is sorted into the registry order above. The `scopes` array of a [current OAuth2 authorisation](#current-oauth2-authorisation-object) and of an [OAuth2 authorisation](#oauth2-authorisation-object) has the stored scopes in no defined order, with unrecognised values removed.
The `scope` string of an [OAuth2 token](#oauth2-token-object) and of an [OAuth2 introspection](#oauth2-introspection-object) is sorted into the registry order above. The `scopes` array of a [current OAuth2 authorisation](#current-oauth2-authorisation-object) has the stored scopes in no defined order, with unrecognised values removed. The `scopes` array of an [OAuth2 authorisation](#oauth2-authorisation-object) is in no defined order, and it can hold `bot` and an unrecognised value once more than one refresh token contributes.
## OAuth2 error response object