From 27d3db56eb2e0610931653c08fc34ba6876934c8 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 25 Sep 2024 20:08:27 +0200 Subject: [PATCH] Update content/client-server-api/_index.md Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- 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 dcbaf776..0453a9c2 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -1440,8 +1440,8 @@ Server administrators may apply locks to prevent users from usefully using their accounts, for instance, due to safety or security concerns. In contrast to account deactivation, locking is a non-destructive action that can be reversed. This specification describes the behaviour of clients -and servers when an account is locked but deliberately leaves the creation -and removal of locks as a server implementation detail. +and servers when an account is locked. It deliberately leaves the methods +for locking and unlocking accounts as a server implementation detail. When an account is locked, servers MUST return a `401 Unauthorized` error response with an `M_USER_LOCKED` error code and [`soft_logout`](#soft-logout)