Update docs_user/modules/proc_adopting-the-identity-service.adoc

Co-authored-by: Katie Gilligan <[email protected]>

Author: xek

docs_user/modules/proc_adopting-the-identity-service.adoc

@@ -96,14 +96,12 @@ This involves two main steps:
 2. Patching the `OpenStackControlPlane` custom resource (CR) to enable domain-specific drivers for the {identity_service} and mount a secret that contains the LDAP configurations.
 
 
-.Create the keystone-domains Secret
-
-This secret stores the actual LDAP configuration files that Keystone will use. Each file within the secret corresponds to an LDAP domain.
+.Procedure
 
-The following example demonstrates creating a secret for a single LDAP domain. Replace `<namespace>` with the namespace where your {identity_service} is deployed.
-The filename `keystone.conf.ldap.DOMAIN_NAME` should be updated to reflect your actual domain name (e.g., `keystone.conf.ldap.myldapdomain`).
+. To create the `keystone-domains` secret that stores the actual LDAP configuration files that {identity_service} uses, create a local file that includes your LDAP configuration, for example, `keystone.conf.ldap.myldapdomain`:
 
-First, create a local file named `keystone.DOMAIN_NAME.conf` (adjust filename as needed) with your LDAP configuration:
+The following example file includes the configuration for a single LDAP domain. If you have multiple LDAP domains, create a configuration file for each, for example, `keystone.DOMAIN_ONE.conf`, `keystone.DOMAIN_TWO.conf`. 
++
 [source,ini]
 ----
 [ldap]