Profiles Sync format fixes

Author: rchinn1

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

@@ -3,22 +3,23 @@ title: Databricks Profiles Sync
 plan: unify
 ---
 
-With Databricks Profiles Sync, you can use Profiles Sync to sync Segment profiles into your Databricks Lakehouse.
+With Databricks Profiles Sync, you can use [Profiles Sync](/docs/unify/profiles-sync/overview/) to sync Segment profiles into your Databricks Lakehouse.
+
 
-<!-- 
-Use Databricks as a warehouse destination and materialized view for Profiles Sync Warehouses 
--->
 ## Getting started
 
-Before starting with the Databricks Profiles Sync destination, note the following prerequisites for setup.
+Before getting started with Databricks Profiles Sync, note the following prerequisites for setup.
 
 - The target Databricks workspace must be Unity Catalog enabled. Segment doesn't support the Hive metastore. Visit the Databricks guide [enabling the Unity Catalog](https://docs.databricks.com/en/data-governance/unity-catalog/enable-workspaces.html){:target="_blank"} for more information. 
-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 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.
 
-- Segment uses the service principal to access your Databricks workspace and associated APIs.
+#### 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:
+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
@@ -30,13 +31,16 @@ Segment creates [managed tables](https://docs.databricks.com/en/data-governance/
   - 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.
 
-- Segment supports only OAuth [(M2M)](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"}  for authentication.
-- A SQL warehouse is required for compute. Segment recommends the following size:
+
+
+#### Size and performance 
+
+A SQL warehouse is required for compute. Segment recommends the following size:
   - **Size**: small
   - **Type** Serverless otherwise Pro
   - **Clusters**: Minimum of 2 - Maximum of 6
 
-- To improve the query performance of the Delta Lake, Segment recommends to create compact jobs per table using OPTIMIZE following [Databricks recommendations](https://docs.databricks.com/en/delta/optimize.html#){:target="_blank"}.
+- 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"}.
 
 - 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. For a better experience, Segment recommends manually starting the warehouse in advance.
 
@@ -51,34 +55,34 @@ Segment creates [managed tables](https://docs.databricks.com/en/data-governance/
 
 ## Connect your Databricks warehouse
 
-Use the following five steps to connect your Databricks warehouse. 
+Use the five steps below to connect your Databricks warehouse. 
 
 > warning ""
 > To configure your warehouse, you'll need read and write permissions.
 
 ### 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 the destination settings (**Connections > Destinations > Settings**) page.
+Add a name to help you identify your 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.
+Check your browser's address bar when inside the workspace. The workspace URL should resemble: `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 
 
-This catalog is the target catalog where Segment lands your schemasand tablestables. 
+This catalog is the target catalog where Segment lands your schemas and tables. 
 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. 
 2. Select the catalog you've just created. 
-    1. Select the Permissions tab, then click **Grant** 
+    1. Select the Permissions tab, then click **Grant**. 
     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
 
 Next, add SQL warehouse details about your compute resource. 
-- **HTTP Path**: The connection details for your SQL warehouse
+- **HTTP Path**: The connection details for your SQL warehouse.
 - **Port**: The port number of your SQL warehouse.
 
 
@@ -100,6 +104,6 @@ Select tables to sync, then click **Next**. Segment creates the warehouse and co
 You can view sync status, and the tables you're syncing from the Profiles Sync overview page.
 
 
-Learn more about [using Selective Sync](/docs/unify/profiles-sync/using-selective-sync) with Profiles Sync.
+Learn more about [using selective sync](/docs/unify/profiles-sync/#using-selective-sync) with Profiles Sync.