chore: Service Account Naming Consistency (#11557)

# Which Problems Are Solved

Inconsistent naming of service account, found in the following
variations:

  - Machine User
  - machine user
  - Service User
  - Machine Account
  - Technical Account
  - User: Type Machine

# How the Problems Are Solved

Attentive search and replace.

Localizations have been translated using Copilot

# Additional Changes

Some unused methods have been removed from the Go code.

# Additional Context

- Closes #11285

apps/docs/content/examples/secure-api/go.mdx

@@ -17,7 +17,7 @@ At the end of the guide you should have an API with a protected endpoint.
 ## Prerequisites
 
 This will handle the OAuth 2.0 introspection request including authentication using JWT with Private Key using our [Go SDK](https://github.com/zitadel/zitadel-go).
-All that is required, is to create your API, create a private key and a personal access token for a service user.
+All that is required, is to create your API, create a private key and a personal access token for a service account.
 
 ### Set up application and obtain keys
 
@@ -54,15 +54,15 @@ And make sure to download it, as you won't be able to retrieve it again.
 
 Now we need to create a *Personal Access Token* to authenticate the application requests.
 
-On the user view, switch to *Service Users* and create a new one.
+On the user view, switch to *Service Accounts* and create a new one.
 
 ![](../../../public/img/go/api-service_user_panel.png)
 
-Give the service user a name and a username. Select `Bearer` as *Access Token Type*.
+Give the service account a name and a username. Select `Bearer` as *Access Token Type*.
 
 ![](../../../public/img/go/api-create_service_user.png)
 
-### Create service user and personal access token (PAT)
+### Create service account and personal access token (PAT)
 
 Once done, from the left panel of the user management, click on Personal Access Token and create a new one.
 

apps/docs/content/examples/secure-api/pylon.mdx

@@ -4,8 +4,8 @@ sidebar_label: Pylon
 ---
 
 import AppJWT from "../imports/_app_jwt.mdx";
-import ServiceuserJWT from "../imports/_serviceuser_jwt.mdx";
-import ServiceuserRole from "../imports/_serviceuser_role.mdx";
+import ServiceAccountJWT from "../imports/_serviceaccount_jwt.mdx";
+import ServiceAccountRole from "../imports/_serviceaccount_role.mdx";
 
 This integration guide demonstrates the recommended way to incorporate ZITADEL into your [Pylon](https://pylon.cronit.io) service.
 It explains how to check the token validity in the API and how to check for permissions.
@@ -20,13 +20,13 @@ Before we can start building our application, we have to do a few configuration
 
 <AppJWT components={props.components}  />
 
-### Create Serviceuser
+### Create Service Account
 
-<ServiceuserJWT components={props.components}  />
+<ServiceAccountJWT components={props.components}  />
 
-### Give Serviceuser an authorization
+### Give Service Account an authorization
 
-<ServiceuserRole components={props.components}  />
+<ServiceAccountRole components={props.components}  />
 
 ### Prerequisites
 
@@ -36,9 +36,9 @@ At the end you should have the following for the API:
 - `.json`-key-file for the API, from the application
 - ID of the project
 
-And the following from the Serviceuser:
+And the following from the Service Account:
 
-- `.json`-key-file from the serviceuser
+- `.json`-key-file from the service account
 
 ## Setup new Pylon service
 
@@ -263,7 +263,7 @@ To call the API you need an access token, which is then verified by ZITADEL.
 Please follow [this guide here](/guides/integrate/token-introspection/private-key-jwt), ignoring the first step as we already have the `.json`-key-file from the serviceaccount.
 
 <Callout>
-You can also create a PAT for the serviceuser and use it to test the API. For this, follow [this guide](/guides/integrate/service-accounts/personal-access-token#create-a-service-user-with-a-pat).
+You can also create a PAT for the service account and use it to test the API. For this, follow [this guide](/guides/integrate/service-accounts/personal-access-token#create-a-service-account-with-a-pat).
 </Callout>
 
 Optionally set the token as an environment variable:

apps/docs/content/examples/secure-api/python-django.mdx

@@ -4,8 +4,8 @@ sidebar_label: Django
 ---
 
 import AppJWT from '../imports/_app_jwt.mdx';
-import ServiceuserJWT from '../imports/_serviceuser_jwt.mdx';
-import ServiceuserRole from '../imports/_serviceuser_role.mdx';
+import ServiceAccountJWT from '../imports/_serviceaccount_jwt.mdx';
+import ServiceAccountRole from '../imports/_serviceaccount_role.mdx';
 import SetupPython from '../imports/_setup_python.mdx';
 
 This integration guide demonstrates the recommended way to incorporate ZITADEL into your Django Python application.
@@ -25,13 +25,13 @@ Before we can start building our application, we have to do a few configuration
 
 <AppJWT components={props.components} />
 
-### Create Serviceuser
+### Create Service Account
 
-<ServiceuserJWT components={props.components} />
+<ServiceAccountJWT components={props.components} />
 
-### Give Serviceuser an authorization
+### Give Service Account an authorization
 
-<ServiceuserRole components={props.components} />
+<ServiceAccountRole components={props.components} />
 
 ### Prerequisites
 
@@ -42,8 +42,8 @@ At the end you should have the following for the API:
 - `.json`-key-file for the API, from the application
 - ID of the project
 
-And the following from the Serviceuser:
-- `.json`-key-file from the serviceuser
+And the following from the Service Account:
+- `.json`-key-file from the service account
 
 ## Setup new Django application
 

apps/docs/content/examples/secure-api/python-flask.mdx

@@ -182,13 +182,13 @@ CLIENT_ID = "197....@projectname"
 CLIENT_SECRET = "NVAp70IqiGmJldbS...."
 ```
 
-### ZITADEL configuration to create a service user
+### ZITADEL configuration to create a service account
 
 ![](../../../public/img/python-flask/3.png)
 
-1. Create a service user and a Personal Access Token (PAT) for that user by following [this guide](/guides/integrate/service-accounts/personal-access-token#create-a-service-user-with-a-pat).
+1. Create a service account and a Personal Access Token (PAT) for that user by following [this guide](/guides/integrate/service-accounts/personal-access-token#create-a-service-account-with-a-pat).
 2. To enable authorization, follow [this guide](/guides/manage/console/roles) to create a role `read:messages` on your project.
-3. Next, create an authorization for the service user you created by adding the role `read:messages` to the user. Follow this [guide](/guides/manage/console/roles#authorizations) for more information on creating an authorization.
+3. Next, create an authorization for the service account you created by adding the role `read:messages` to the user. Follow this [guide](/guides/manage/console/roles#authorizations) for more information on creating an authorization.
 
 ### Run the API
 
@@ -222,7 +222,7 @@ curl --request GET \
 
 You should get a response with Status Code 401 and an error message.
 
-Now let's add an authorization header to your request. Save the personal access token for your service user to a variable by running the following command. Replace the value with the PAT you obtained earlier.
+Now let's add an authorization header to your request. Save the personal access token for your service account to a variable by running the following command. Replace the value with the PAT you obtained earlier.
 
 `PAT=nr9vnUTkQkn4rxWk...`
 
@@ -252,4 +252,4 @@ You should get a response with Status Code 200 and the following message.
 
 `{"message":"Private, scoped route - You need to be authenticated and have the role read:messages to see this."}`
 
-You can remove the role from the service user in ZITADEL and try again. You should then get a Status Code 403, Forbidden error.
+You can remove the role from the service account in ZITADEL and try again. You should then get a Status Code 403, Forbidden error.