re-organize step 5

Author: rchinn1

src/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync.md

@@ -72,12 +72,11 @@ Next, add SQL warehouse details about your compute resource.
 
 ### Step 5: Add the service principal client ID and client secret
 
-> warning ""
-> Be sure to note the principal ID and the client secret Databricks generates, as you'll need to enter them in this step.
-
 Segment uses the service principal to access your Databricks workspace and associated APIs.
-1. Follow the [Databricks guide for adding a service principal to your account](https://docs.databricks.com/en/administration-guide/users-groups/service-principals.html#manage-service-principals-in-your-account){:target="_blank"}. This name can be anything, but Segment recommends something that identifies the purpose (for example, "Segment Profiles Sync"). Note the principal application ID that Databricks generates to use in this step. Segment doesn't require `Account admin` or `Marketplace admin` roles.
-2. Follow the [Databricks instructions to generate an OAuth secret](https://docs.databricks.com/en/dev-tools/authentication-oauth.html#step-2-create-an-oauth-secret-for-a-service-principal){:target="_blank"}. Note the secret generated by Databricks to use in this step. Once you navigate away from this page, the secret is no longer visible. If you lose or forget the secret, delete the existing secret and create a new one. 
+
+#### Service principal client ID
+
+Follow the [Databricks guide for adding a service principal to your account](https://docs.databricks.com/en/administration-guide/users-groups/service-principals.html#manage-service-principals-in-your-account){:target="_blank"}. This name can be anything, but Segment recommends something that identifies the purpose (for example, "Segment Profiles Sync").  Segment doesn't require `Account admin` or `Marketplace admin` roles.
 
 The service principal needs the following setup:
   - [Catalog level priveleges](https://docs.databricks.com/en/data-governance/unity-catalog/manage-privileges/privileges.html#general-unity-catalog-privilege-types){:target="_blank"} which include:
@@ -90,6 +89,10 @@ The service principal needs the following setup:
   - Databricks [SQL access entitlement](https://docs.databricks.com/en/administration-guide/users-groups/service-principals.html#manage-workspace-entitlements-for-a-service-principal){:target="_blank"} at the workspace level.
   - [CAN USE permissions](https://docs.databricks.com/en/security/auth-authz/access-control/sql-endpoint-acl.html#sql-warehouse-permissions){:target="_blank"} on the SQL warehouse that will be used for the sync.
 
+#### Client secret
+
+Follow the [Databricks instructions to generate an OAuth secret](https://docs.databricks.com/en/dev-tools/authentication-oauth.html#step-2-create-an-oauth-secret-for-a-service-principal){:target="_blank"}.
+
 
 Once you've configured your warehouse, test the connection and click **Next**.