From 770621ba415f58a04a91733df335fd8e09826fd9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= Date: Fri, 22 May 2026 20:10:45 +0200 Subject: [PATCH] docs: u{p => t}most typo --- docsite/docs/configuration/clients/discord/discord-headless.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/docs/configuration/clients/discord/discord-headless.mdx b/docsite/docs/configuration/clients/discord/discord-headless.mdx index ea7c308d..db2d8ea5 100644 --- a/docsite/docs/configuration/clients/discord/discord-headless.mdx +++ b/docsite/docs/configuration/clients/discord/discord-headless.mdx @@ -22,7 +22,7 @@ Check the [main Discord docs page](/configuration/clients/discord) for a compari -Multi-scrobbler does its upmost to implement, to-spec, [Gateway API communication](https://docs.discord.com/developers/events/gateway) and respect usage. It requires no [permissions](https://docs.discord.com/developers/events/gateway#gateway-intents) and reads no data other than monitoring what other user sessions are active. +Multi-scrobbler does its utmost to implement, to-spec, [Gateway API communication](https://docs.discord.com/developers/events/gateway) and respect usage. It requires no [permissions](https://docs.discord.com/developers/events/gateway#gateway-intents) and reads no data other than monitoring what other user sessions are active. Aside from the on-paper violation of using a user token programmatically (on your behalf), there is no misuse of the API to achieve rich presence. -- 2.51.2