Profiles Sync edits

Author: rchinn1

src/connections/storage/catalog/databricks-delta-lake/databricks-profiles-sync.md

@@ -19,7 +19,7 @@ Segment creates [managed tables](https://docs.databricks.com/en/data-governance/
   -  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 teh existing secret and create a new one. 
+  - 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
@@ -58,16 +58,15 @@ Use the following five steps to connect your Databricks warehouse.
 
 ### Step 1: Name your destination
 
-Add a name to help you identify this warehouse in Segment. You can change this name at any time by navigating to (???
+Add a name to help you identify this warehouse in Segment. You can change this name at any time by navigating to the destination settings (**Connections > Destinations > Settings**) page.
 
 ### Step 2: Enter the Databricks compute resources URL
 
-
 You'll use the Databricks workspace URL, along with Segment, to access your workspace API. 
 
 Check your browser's address bar when inside the workspace. The workspace URL will look something like: `https://<workspace-deployment-name>.cloud.databricks.com`. Remove any characters after this portion and note the URL for later use.
 
-### Step 3: Enter a Unity catalog name. 
+### Step 3: Enter a Unity catalog name 
 
 This catalog is the target catalog where Segment lands your schemasand tablestables. 
 1. Follow the Databricks guide for [creating a catalog](https://docs.databricks.com/en/data-governance/unity-catalog/create-catalogs.html#create-a-catalog){:target="_blank"}. Be sure to select the storage location created earlier. You can use any valid catalog name (for example, "Segment"). Note this name for later use. 
@@ -76,14 +75,14 @@ This catalog is the target catalog where Segment lands your schemasand tablestab
     2. Select the Segment service principal from the dropdown, and check `ALL PRIVILEGES`.
     3. Click **Grant**.
 
-### Step 4: Add the SQL warehouse details from your Databricks warehouse.
+### Step 4: Add the SQL warehouse details from your Databricks warehouse
 
 Next, add SQL warehouse details about your compute resource. 
-- **HTTP Path**: Get connection detials for a SQL warehouse
+- **HTTP Path**: The connection details for your SQL warehouse
 - **Port**: The port number of your SQL warehouse.
 
 
-### Step 5: Add the principal service client ID and client secret.
+### Step 5: Add the principal service client ID and client secret
 
 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 Application ID that Databricks generates for later use. Segment doesn't require Account admin or Marketplace admin roles.