Fixups

Author: eseliger

docs/admin/access_control/index.mdx

@@ -40,7 +40,7 @@ You can read about the specific permission types available for each RBAC-enabled
 
 - [Batch Changes](/admin/access_control/batch_changes)
 - [Ownership](/admin/access_control/ownership)
-- [Service accounts](/admin/access_control/service_accounts)
+- [Service accounts](/admin/service_accounts)
 
 ### Deleting a role
 

docs/admin/auth/index.mdx

@@ -31,7 +31,7 @@ The authentication providers are configured in the [`auth.providers`](/admin/con
 
 ## Programmatic authentication
 
-For automated systems, CI/CD pipelines, and API integrations that need to authenticate without human interaction, use [service accounts](/admin/access_control/service_accounts). Service accounts are specialized user accounts designed for automation that authenticate using access tokens rather than passwords.
+For automated systems, CI/CD pipelines, and API integrations that need to authenticate without human interaction, use [service accounts](/admin/service_accounts). Service accounts are specialized user accounts designed for automation that authenticate using access tokens rather than passwords.
 
 ## Login form configuration
 

docs/admin/oauth_apps.mdx

@@ -11,7 +11,7 @@ This makes OAuth the preferred choice for any multi-user integration like browse
 
 OAuth Apps follow standards [RFC 6749](https://tools.ietf.org/html/rfc6749), [RFC 7636 (PKCE)](https://tools.ietf.org/html/rfc7636), and [RFC 8628 (Device Authorization Grant)](https://tools.ietf.org/html/rfc8628).
 
-Consider using **M2M (client-credentials) service-account tokens** or traditional [access tokens](/admin/access_control/access_tokens) for server-to-server communication, automated scripts, CI/CD pipelines, or single-user applications that do not require per-user permission checks. See [service accounts](/admin/access_control/service_accounts#m2m-oauth-credentials-client-credentials-flow) for details.
+Consider using **M2M (client-credentials) service-account tokens** or traditional [access tokens](/admin/access_control/access_tokens) for server-to-server communication, automated scripts, CI/CD pipelines, or single-user applications that do not require per-user permission checks. See [service accounts](/admin/service_accounts#m2m-oauth-credentials-client-credentials-flow) for details.
 
 ## Creating an OAuth App
 

docs/api/graphql/index.mdx

@@ -44,7 +44,7 @@ Both authentication methods will return a response like this:
 
 <Callout type="note">OAuth access tokens are always short-lived and must be refreshed using refresh tokens before expiration. Check the `expires_in` field and refresh proactively.</Callout>
 
-For automated scripts, CI/CD pipelines, and production integrations, use [service accounts](/admin/access_control/service_accounts) instead of personal access tokens. Service accounts are designed specifically for programmatic API access and provide better security and audit capabilities.
+For automated scripts, CI/CD pipelines, and production integrations, use [service accounts](/admin/service_accounts) instead of personal access tokens. Service accounts are designed specifically for programmatic API access and provide better security and audit capabilities.
 
 ## Documentation & tooling