diff --git a/server_admin/topics/clients/oidc/service-accounts.adoc b/server_admin/topics/clients/oidc/service-accounts.adoc
index 6e49031aeb..a5b00adf99 100644
--- a/server_admin/topics/clients/oidc/service-accounts.adoc
+++ b/server_admin/topics/clients/oidc/service-accounts.adoc
@@ -12,7 +12,7 @@ To use it you must have registered a valid `confidential` Client and you need to
 In tab `Service Account Roles` you can configure the roles available to the service account retrieved on behalf of this client.
 Don't forget that you need those roles to be available in Scopes of this client as well (unless you have `Full Scope Allowed` on). As in normal login, roles from access token are the intersection of scopes and the service account roles.
 
-The REST URL to invoke on is `/\{server-root-usualy-auth}/realms/\{realm-name}/protocol/openid-connect/token`.
+The REST URL to invoke on is `/auth/realms/\{realm-name}/protocol/openid-connect/token`.
 Invoking on this URL is a POST request and requires you to post the client credentials.
 By default, client credentials are represented by clientId and clientSecret of the client in `Authorization: Basic` header, but you can also authenticate the client with a signed JWT assertion or any other custom mechanism for client authentication.
 You also need to use the parameter `grant_type=client_credentials` as per the OAuth2 specification.