chore: rename configuration to settings (#11568)

# Which Problems Are Solved

naming inconsistencies: Configuration <-> Settings

# How the Problems Are Solved


# Additional Changes


# Additional Context

- Closes #11282

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

@@ -21,7 +21,7 @@ All that is required, is to create your API, create a private key and a personal
 
 ### Set up application and obtain keys
 
-Before we begin developing our API, we need to perform a few configuration steps in the ZITADEL Console.
+Before we begin developing our API, we need to perform a few setup steps in the ZITADEL Console.
 You'll need to provide some information about your app. We recommend creating a new app to start from scratch.
 
 Starting from the homepage of your management console, click on Create Application

apps/docs/content/examples/secure-api/java-spring.mdx

@@ -15,7 +15,7 @@ You can either create your own application or directly run the example by provid
 
 ## Set up application
 
-Before we begin developing our API, we need to perform a few configuration steps in the ZITADEL Console.
+Before we begin developing our API, we need to perform a few setup steps in the ZITADEL Console.
 You'll need to provide some information about your app. We recommend creating a new app to start from scratch. Navigate to your Project, then add a new application at the top of the page.
 Select the **API** application type and continue.
 
@@ -47,7 +47,7 @@ So in your application, create a `support/zitadel` package and in there the `Cus
 https://github.com/zitadel/zitadel-java/blob/main/api/src/main/java/demo/app/support/zitadel/CustomAuthorityOpaqueTokenIntrospector.java
 ```
 
-### Application server configuration
+### Application server settings
 
 As we have now our support class, we can now create and configure the application server itself.
 
@@ -59,7 +59,7 @@ It will also use the just created CustomAuthorityOpaqueTokenIntrospector for the
 https://github.com/zitadel/zitadel-java/blob/main/api/src/main/java/demo/app/config/WebSecurityConfig.java
 ```
 
-For the authorization (and the server in general) to work, the application needs some configuration, so please provide the following to your `application.yml` (resources folder):
+For the authorization (and the server in general) to work, the application needs some settings, so please provide the following to your `application.yml` (resources folder):
 
 ```yaml reference
 https://github.com/zitadel/zitadel-java/blob/main/api/src/main/resources/application.yml

apps/docs/content/examples/secure-api/nodejs-nestjs.mdx

@@ -23,7 +23,7 @@ The NestJS API includes a private endpoint `GET http://localhost:${APP_PORT}/api
 
 Make sure you have Node.js and npm installed on your machine.
 
-### ZITADEL Configuration for the API
+### ZITADEL Setup for the API
 
 1. Create a ZITADEL instance and a project by following the steps [here](/guides/start/quickstart#3-create-your-zitadel-instance).
 

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

@@ -14,7 +14,7 @@ By the end of this guide, your application will have three different endpoint wh
 
 ## ZITADEL setup
 
-Before we can start building our application, we have to do a few configuration steps in ZITADEL Management Console.
+Before we can start building our application, we have to do a few setup steps in ZITADEL Management Console.
 
 ### Create application
 
@@ -42,7 +42,7 @@ And the following from the Service Account:
 
 ## Setup new Pylon service
 
-Pylon allows you to create a new service using the `npm create pylon` command. This command creates a new Pylon project with a basic project structure and configuration.
+Pylon allows you to create a new service using the `npm create pylon` command. This command creates a new Pylon project with a basic project structure and settings.
 During the setup process, you can choose your preferred runtime, such as Bun, Node.js, or Cloudflare Workers.
 
 **This guide uses the Bun runtime.**
@@ -98,7 +98,7 @@ export default app;
 
 ### Add ZITADEL info to the service
 
-1. Create a `.env` file in the root folder of your project and add the following configuration:
+1. Create a `.env` file in the root folder of your project and add the following settings:
 
 ```bash
 AUTH_ISSUER='URL to the zitadel instance'

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

@@ -19,7 +19,7 @@ This documentation references our [example](https://github.com/zitadel/example-d
 
 ## ZITADEL setup
 
-Before we can start building our application, we have to do a few configuration steps in ZITADEL Management Console.
+Before we can start building our application, we have to do a few setup steps in ZITADEL Management Console.
 
 ### Create application
 
@@ -55,7 +55,7 @@ And the following from the Service Account:
 
 For this example we need the following dependencies:
 - `django`: to create an API with django
-- `python-dotenv`: to use environment variables in the configuration
+- `python-dotenv`: to use environment variables in the settings
 - `authlib`: client-side OAuth functionality
 - `requests`: HTTP requests for the introspection
 
@@ -85,7 +85,7 @@ There is info needed for the introspection calls, which we put into the settings
 https://github.com/zitadel/example-python-django-oauth/blob/main/myapi/settings.py#L125-L133
 ```
 
-and create a ".env"-file in the root folder with the configuration as an example:
+and create a ".env"-file in the root folder with the settings as an example:
 ```bash
 ZITADEL_INTROSPECTION_URL = 'URL to the introspection endpoint to verify the provided token'
 ZITADEL_DOMAIN = 'Domain used as audience in the token verification'

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

@@ -23,7 +23,7 @@ In this example we will use a service account with a [personal access token](/gu
 
 In order to run the example you need to have `python3` and `pip3` installed.
 
-### ZITADEL configuration for the API
+### ZITADEL settings for the API
 
 ![](../../../public/img/python-flask/2.png)
 
@@ -174,7 +174,7 @@ class ZitadelIntrospectTokenValidator(IntrospectTokenValidator):
         return res
 ```
 
-3. Create a new file named ".env" in the directory. Copy the configuration in the [".env.example"](https://github.com/zitadel/example-api-python3-flask/blob/main/.env.example) file to the newly created .env file. Set the values with your Custom Domain/Issuer URL, Client ID, and Client Secret from the previous steps. Obtain your Issuer URL by following [these steps](/guides/start/quickstart#5-collect-your-integration-keys).
+3. Create a new file named ".env" in the directory. Copy the settings in the [".env.example"](https://github.com/zitadel/example-api-python3-flask/blob/main/.env.example) file to the newly created .env file. Set the values with your Custom Domain/Issuer URL, Client ID, and Client Secret from the previous steps. Obtain your Issuer URL by following [these steps](/guides/start/quickstart#5-collect-your-integration-keys).
 
 ```python
 ZITADEL_DOMAIN = "https://custom-domain-abcdef.zitadel.cloud"
@@ -182,7 +182,7 @@ CLIENT_ID = "197....@projectname"
 CLIENT_SECRET = "NVAp70IqiGmJldbS...."
 ```
 
-### ZITADEL configuration to create a service account
+### ZITADEL settings to create a service account
 
 ![](../../../public/img/python-flask/3.png)