More feedback from Profiles Sync EM

Author: rchinn1

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

@@ -14,25 +14,6 @@ Before getting started with Databricks Profiles Sync, note the following prerequ
 - Segment creates [managed tables](https://docs.databricks.com/en/data-governance/unity-catalog/create-tables.html#managed-tables){:target="_blank"} in the Unity catalog. 
 - Segment supports only [OAuth (M2M)](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"}  for authentication.
 
-#### Service principal requirements and setup
-
-Segment uses the service principal to access your Databricks workspace and associated APIs.
-  -  Use 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 Application ID that Databricks generates for later use. Segment doesn't require `Account admin` or `Marketplace admin` roles.
-
-The service principal needs the following setup:
-  - OAuth secret tocken generated. Follow the [Databricks guide for generating 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 for later use. Once you navigate away from the page the secret is no longer visible. If you lose or forget the secret, you can delete the existing secret and create a new one. 
-  - [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:
-    - USE CATALOG
-    - USE SCHEMA
-    - MODIFY
-    - SELECT
-    - CREATE SCHEMA
-    - CREATE TABLE
-  - 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.
-
-
-
 #### Warehouse size and performance 
 
 A SQL warehouse is required for compute. Segment recommends the following size:
@@ -42,7 +23,7 @@ A SQL warehouse is required for compute. Segment recommends the following size:
 
 
 > success ""
-> To improve the query performance of the Delta Lake, Segment recommends creating compact jobs per table using OPTIMIZE following [Databricks recommendations](https://docs.databricks.com/en/delta/optimize.html#){:target="_blank"}. <br>
+> To improve the query performance of the Delta Lake, Segment recommends creating compact jobs per table using OPTIMIZE following [Databricks recommendations](https://docs.databricks.com/en/delta/optimize.html#){:target="_blank"}. 
 
 > info ""
 > Segment recommends manually starting your SQL warehouse in advance. If the SQL warehouse isn't running, Segment attempts to start the SQL warehouse to validate the connection and may experience a timeout when you hit the **Test Connection** button during setup.
@@ -89,15 +70,25 @@ Next, add SQL warehouse details about your compute resource.
 - **Port**: The port number of your SQL warehouse.
 
 
-### Step 5: Add the principal service client ID and client secret
+### 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 in this step for later use.
+> 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 for later use. 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 for later use. 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. 
+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. 
 
+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:
+    - USE CATALOG
+    - USE SCHEMA
+    - MODIFY
+    - SELECT
+    - CREATE SCHEMA
+    - CREATE TABLE
+  - 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.
 
 
 Once you've configured your warehouse, test the connection and click **Next**.