diff --git a/website/docs/how-to/how-to-use-the-admin-api.md b/website/docs/how-to/how-to-use-the-admin-api.md
index f993e5ea32..e4a001b577 100644
--- a/website/docs/how-to/how-to-use-the-admin-api.md
+++ b/website/docs/how-to/how-to-use-the-admin-api.md
@@ -20,12 +20,12 @@ If you need an API token to use in a client SDK you should create a client token
 
 Now that you have an access token with admin privileges, you can use it to make changes in your Unleash instance.
 
-In the example below we will use the [Unleash Admin API](/reference/api/legacy/unleash/admin/features.md) to enable the `Demo` feature flag using curl.
+In the example below we will use the [Unleash Admin API](/reference/api/legacy/unleash/admin/features.md) to enable the `checkout-flow` feature flag in `development` using curl.
 
 ```sh
 curl -X POST -H "Content-Type: application/json" \
      -H "Authorization: <your-token>" \
-     https://app.unleash-hosted.com/demo/api/admin/features/Demo/toggle/on
+     https://app.unleash-hosted.com/docs-demo/api/admin/projects/docs-project/features/checkout-flow/environments/development/on
 ```
 
 We have now enabled the feature flag. We can also verify that it was actually changed by the API user by navigating to [Event Log](/reference/events#event-log) and filtering events for this feature flag.
diff --git a/website/docs/reference/api-tokens-and-client-keys.mdx b/website/docs/reference/api-tokens-and-client-keys.mdx
index 08713e4601..5d9967c30d 100644
--- a/website/docs/reference/api-tokens-and-client-keys.mdx
+++ b/website/docs/reference/api-tokens-and-client-keys.mdx
@@ -48,7 +48,7 @@ When you use a personal access token to modify resources, the events record the
 
 Personal access tokens with a lifetime expire and stop working after their expiration date. Although you can set the token to not expire, we recommend using tokens with expiration dates to follow security best practices.
 
-Personal access tokens are not suitable for client SDKs, as they cannot read flag data from multiple environments, they may expire, or their permissions may change. Use [client tokens](#client-tokens) instead.
+Personal access tokens are not suitable for client SDKs, as they are not bound to an environment, they may expire, or their permissions may change. Use [client tokens](#client-tokens) instead.
 
 ### Service account tokens
 
diff --git a/website/docs/reference/front-end-api.md b/website/docs/reference/front-end-api.md
index 32847fc623..b1c03982ea 100644
--- a/website/docs/reference/front-end-api.md
+++ b/website/docs/reference/front-end-api.md
@@ -37,7 +37,7 @@ The client needs to point to the correct API endpoint. The Frontend API is avail
 
 ### API token
 
-The client needs a frontend [token](../reference/api-tokens-and-client-keys.mdx#front-end-tokens) to interacting with the Frontend API.
+The client needs a frontend [token](../reference/api-tokens-and-client-keys.mdx#front-end-tokens) to interact with the Frontend API.
 
 ### Refresh interval for tokens
 
diff --git a/website/docs/reference/service-accounts.md b/website/docs/reference/service-accounts.md
index dc78d4cfdf..231334cfa2 100644
--- a/website/docs/reference/service-accounts.md
+++ b/website/docs/reference/service-accounts.md
@@ -8,7 +8,7 @@ title: Service Accounts
 
 :::
 
-Service accounts provide an identity for integration and automation tools to access the Unleash API. You can assign tokens to service accounts which give them a granular set of permissions. Service accounts do not have a password and, as such, cannot access the Unleash Admin UI.
+Service accounts provide an identity for integration and automation tools to access the Unleash API. You can assign a role to a service account, granting it a specific set of permissions. Service accounts authenticate using tokens. They do not have a password and cannot access the Unleash Admin UI.
 
 ## Create a service account