fix sso auth block (#36038)

Author: Hesperide

docs/enterprise-setup/implementation-guide.md

@@ -235,29 +235,14 @@ license-key: # license key provided by Airbyte team
 
 4. Add your Airbyte Self-Managed Enterprise license key to your `airbyte.yml` in the `license-key` field.
 
-### Step 3: Configure your Deployment
-
-1. Inside your `airbyte` directory, create an empty `values.yml` file.
-
-2. Paste the following into your newly created `values.yml` file. This is required to deploy Airbyte Self-Managed Enterprise:
-
-```yml
-global:
-  edition: enterprise
-```
-
-3. The following subsections help you customize your deployment to use SSO, an external database, log storage, and more. To skip this and deploy a minimal, local version of Self-Managed Enterprise, [jump to Step 4](#step-4-deploy-self-managed-enterprise). 
-
-#### Configure User Authentication
-
-To enable SSO authentication, add [SSO auth details](/access-management/sso) to your `values.yml` file. 
+5. To enable SSO authentication, add [SSO auth details](/access-management/sso) to your `airbyte.yml` file. 
 
 <details>
-    <summary>Configuring auth in your values.yml file</summary>
+<summary>Configuring auth in your airbyte.yml file</summary>
 
 <Tabs>
 <TabItem value="Okta" label="Okta">
-To configure SSO with Okta, add the following at the end of your `values.yml` file:
+To configure SSO with Okta, add the following at the end of your `airbyte.yml` file:
 
 ```yaml
 auth:   
@@ -293,10 +278,23 @@ See the [following guide](/access-management/sso-providers/azure-entra-id) on ho
 
 To modify auth configurations on an existing deployment (after Airbyte has been installed at least once), you will need to `helm upgrade` Airbyte with the additional environment variable `--set keycloak-setup.env_vars.KEYCLOAK_RESET_REALM=true`. As this also resets the list of Airbyte users and permissions, please use this with caution.
 
-To deploy Self-Managed Enterprise without SSO, exclude the entire `auth:` section from your values.yml config file. You will authenticate with the instance admin user and password included in your `values.yml`. Without SSO, you cannot currently have unique logins for multiple users.
+To deploy Self-Managed Enterprise without SSO, exclude the entire `auth:` section from your values.yml config file. You will authenticate with the instance admin user and password included in your `airbyte.yml`. Without SSO, you cannot currently have unique logins for multiple users.
 
 </details>
 
+### Step 3: Configure your Deployment
+
+1. Inside your `airbyte` directory, create an empty `values.yml` file.
+
+2. Paste the following into your newly created `values.yml` file. This is required to deploy Airbyte Self-Managed Enterprise:
+
+```yml
+global:
+  edition: enterprise
+```
+
+3. The following subsections help you customize your deployment to use an external database, log storage, dedicated ingress, and more. To skip this and deploy a minimal, local version of Self-Managed Enterprise, [jump to Step 4](#step-4-deploy-self-managed-enterprise). 
+
 #### Configuring the Airbyte Database
 
 For Self-Managed Enterprise deployments, we recommend using a dedicated database instance for better reliability, and backups (such as AWS RDS or GCP Cloud SQL) instead of the default internal Postgres database (`airbyte/db`) that Airbyte spins up within the Kubernetes cluster.