Add PS feedback to Databricks Destination

Author: rchinn1

src/connections/storage/catalog/databricks/index.md

@@ -29,8 +29,8 @@ A SQL warehouse is required for compute. Segment recommends the following size:
   - **Clusters**: Minimum of 2 - Maximum of 6
 
 > success ""
-> 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 when you hit the **Test Connection** button during setup.
-
+> 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.
+ 
 ## Set up Databricks in Segment
 
 Use the following steps to set up Databricks in Segment:
@@ -75,11 +75,14 @@ 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, 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 Storage Destinations"). Note the Application ID that Databricks generates for later use. Segment doesn't require Account admin or Marketplace admin roles.
-2. (*OAuth only*) 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 Storage Destinations"). 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. 
 
 
 Once connected, you'll see a confirmation screen with next steps and more info on using your warehouse.