Reword "UI Authorization" to "User-Interactive Authentication" (#2667)

Signed-off-by: Aaron Raimist <aaron@raim.ist>

api/client-server/logout.yaml

@@ -54,11 +54,12 @@ paths:
         for the user are also deleted. `Device keys <#device-keys>`_ for the device are
         deleted alongside the device.
 
-        This endpoint does not require UI authorization because UI authorization is
+        This endpoint does not use the `User-Interactive Authentication API`_ because
-        designed to protect against attacks where the someone gets hold of a single access
+        User-Interactive Authentication is designed to protect against attacks where the
-        token then takes over the account. This endpoint invalidates all access tokens for
+        someone gets hold of a single access token then takes over the account. This
-        the user, including the token used in the request, and therefore the attacker is
+        endpoint invalidates all access tokens for the user, including the token used in
-        unable to take over the account in this way.
+        the request, and therefore the attacker is unable to take over the account in
+        this way.
       operationId: logout_all
       security:
         - accessToken: []

changelogs/client_server/2667.clarification

@@ -0,0 +1 @@
+Reword "UI Authorization" to "User-Interactive Authentication" to be more clear.

specification/client_server_api.rst

@@ -1090,8 +1090,7 @@ Login
 
 A client can obtain access tokens using the ``/login`` API.
 
-Note that this endpoint does `not` currently use the user-interactive
+Note that this endpoint does `not` currently use the `User-Interactive Authentication API`_.
-authentication API.
 
 For a simple username/password login, clients should submit a ``/login``
 request as follows: