ci: fix docs lints
diff --git a/docs/openstack/keycloak.md b/docs/openstack/keycloak.md
index 5202ed0..f9ad0f9 100644
--- a/docs/openstack/keycloak.md
+++ b/docs/openstack/keycloak.md
@@ -20,24 +20,24 @@
##### Obtain the Redirect URI from Keycloak
-4. Log into the Keycloak admin console using your administrator credentials.
-5. Switch to the `atmosphere` realm where you'll be configuring Azure AD.
-6. In the **Identity Providers** section, select **Add provider** and choose **Microsoft**.
-7. Keycloak will generate a **Redirect URI** which you will use in the Azure AD application registration process to ensure that authentication responses are correctly routed.
+1. Log into the Keycloak admin console using your administrator credentials.
+2. Switch to the `atmosphere` realm where you'll be configuring Azure AD.
+3. In the **Identity Providers** section, select **Add provider** and choose **Microsoft**.
+4. Keycloak will generate a **Redirect URI** which you will use in the Azure AD application registration process to ensure that authentication responses are correctly routed.
##### Finalize Azure AD Application Registration
-8. Return to the Azure AD application registration page and input the Redirect URI from Keycloak.
-9. After the application is registered, navigate to **Certificates & secrets** to create a client secret.
-10. Record the **Client ID** and **Client Secret** provided, as they will be needed to configure Keycloak.
+1. Return to the Azure AD application registration page and input the Redirect URI from Keycloak.
+2. After the application is registered, navigate to **Certificates & secrets** to create a client secret.
+3. Record the **Client ID** and **Client Secret** provided, as they will be needed to configure Keycloak.
#### Configure Keycloak
With the Client ID and Client Secret in hand, you can now set up Keycloak to use Azure AD as an identity provider.
-11. In the Keycloak admin console, navigate back to the `atmosphere` realm's **Identity Providers** section.
-12. For the Microsoft provider configuration, enter the **Client ID** and **Client Secret** obtained from Azure AD.
-13. Adjust any additional settings according to your requirements, such as the default scopes, mappers, and other provider-specific configurations.
-14. Save your changes to finalize the integration.
+1. In the Keycloak admin console, navigate back to the `atmosphere` realm's **Identity Providers** section.
+2. For the Microsoft provider configuration, enter the **Client ID** and **Client Secret** obtained from Azure AD.
+3. Adjust any additional settings according to your requirements, such as the default scopes, mappers, and other provider-specific configurations.
+4. Save your changes to finalize the integration.
By integrating Azure AD with Keycloak, you enable users to authenticate with their corporate credentials across all applications that are secured by Keycloak. This provides a consistent and secure user experience, leveraging the robust features of Azure AD within the flexible framework of Keycloak. For a deeper dive into the Azure AD configuration within Keycloak, consult the [Keycloak Microsoft Identity Provider documentation](https://www.keycloak.org/docs/latest/server_admin/#_microsoft).