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/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'