From 8dea69ffd8afbbd15252b7da0a1312b44782d905 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Wed, 11 Jun 2025 09:38:35 +0100 Subject: [PATCH] Apply suggestions from code review --- content/client-server-api/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 6bc8b0c3..f7a5489b 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -1525,7 +1525,7 @@ This specification defines the following scope tokens: | Scope | Purpose | |---------------------------|---------------------------------------------| -| `urn:matrix:client:api:*` | Grants full access to the Client-Server API | +| `urn:matrix:client:api:*` | Grants full access to the Client-Server API. | {{% boxes/note %}} This token matches the behavior of the legacy authentication API. Future MSCs @@ -1537,7 +1537,7 @@ could introduce more fine-grained scope tokens like | Scope | Purpose | |----------------------------------------|----------------------------------------------------------------------------------------------| -| `urn:matrix:client:device:` | Allocates the given `device_id` and associates it to the generated access and refresh tokens | +| `urn:matrix:client:device:` | Allocates the given `device_id` and associates it to the generated access and refresh tokens. | Contrary to the legacy login and registration APIs where the homeserver is typically the one generating a `device_id` and providing it to the client, with