Update links in Databricks

Author: rchinn1

src/connections/storage/catalog/databricks-delta-lake/index.md

@@ -16,11 +16,11 @@ Before getting started with the Databricks Destination, note the following prere
 
 - 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. The service account needs access to create schemas on the catalog and can delete, drop, or vacuum tables.
-- Segment supports only OAuth [(M2M)](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"}  for authentication.
+- Segment supports only [OAuth (M2M)](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"}  for authentication.
 
 #### Warehouse size
 
-- A SQL warehouse is required for compute. Segment recommends the following size:
+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
@@ -59,7 +59,7 @@ Check your browser's address bar when inside the workspace. The workspace URL sh
 ### Step 3: Enter a Unity catalog name 
 
 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. 
+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** 
     2. Select the Segment service principal from the dropdown, and check `ALL PRIVILEGES`.
@@ -75,8 +75,8 @@ Next, add SQL warehouse details about your compute resource.
 ### 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 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 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. 
 
 
 Once connected, you'll see a confirmation screen with next steps and more info on using your warehouse.