More edits [netlify-build]

Author: rchinn1

src/connections/storage/databricks-delta-lake/databricks-delta-lake-aws.md

@@ -27,25 +27,25 @@ Segment supports both OAuth and personal access token (PAT) for authentication.
 
 As you set up Databricks, keep the following key terms in mind. 
 - **Databricks Workspace URL**: The base URL for your Databricks workspace.
-- **Service principal Application ID**: The ID tied to the service principal you'll create for Segment. 
+- **Service Principal Application ID**: The ID tied to the service principal you'll create for Segment. 
 - **Service Principal Secret/Token**: The client secret or PAT you'll create for the service principal. 
 - **Target Unity Catalog**: The catalog where Segment lands your data. 
 - **Workspace Admin Token** (*PAT only*): The access token you'll generate for your Databricks workspace admin.
 
 ## Setup
 
-Use the following nine steps to set up your Databricks destination with AWS.
+Use the following nine steps to set up your Databricks Delta Lake destination with AWS.
 
 ### Step 1: Find your Databricks Workspace URL 
 
-The workspace URL is used by you and Segment to access your workspace API. 
+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 2: Create a service principal 
 
-The service principal is used by Segment to access your Databricks workspace and associated APIs.
-1. Follow the Databricks [guide](https://docs.databricks.com/en/administration-guide/users-groups/service-principals.html#manage-service-principals-in-your-account){:target="_blank"} for adding a service principal to your account and assigning to the workspace. 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, you can delete the existing secret and create a new one. 
+Segment uses the service principal to access your Databricks workspace and associated APIs.
+1. Follow the Databricks [guide](https://docs.databricks.com/en/administration-guide/users-groups/service-principals.html#manage-service-principals-in-your-account){:target="_blank"} for adding a service principal to your account. 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. 
 
 ### Step 3: Enable entitlements for the service principal on the workspace 
 

src/connections/storage/databricks-delta-lake/databricks-delta-lake-azure.md

@@ -28,11 +28,11 @@ As you set up Databricks, keep the following key terms in mind.
 
 ## Set up Databricks with Azure
 
-Use the following eight steps to setup your Databricks destination with Azure.
+Use the following eight steps to setup your Databricks Delta Lake destination with Azure.
 
 ### Step 1: Find your Databricks Workspace URL 
 
-Your Databricks Workspace URL is used by you and Segment to access your workspace API.
+You'll use the Databricks workspace URL, along with Segment, to access your workspace API.
 
 Check your browser's address bar when in your workspace. The workspace URL will look something like: `https://<workspace-deployment-name>.azuredatabricks.net`. Remove any characters after this portion and note this value for later use. 
 
@@ -108,7 +108,7 @@ This catalog is the target catalog where Segment lands your schemas/tables.
 1. Follow the Databricks guide for [creating a catalog](https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/create-catalogs){:target="_blank"}. 
 - Select the storage location you created earlier. The catalog name can be any valid catalog name (for example, "Segment"). Note this name for later use. 
 2. Select the newly-created catalog. 
-    1. Click the Permissions tab, then **Grant**. 
+    1. Click the Permissions tab, then click **Grant**. 
     2. Select the Segment service principal from the dropdown.
     3. Check `ALL PRIVILEGES`, then click **Grant**.
 
@@ -118,4 +118,4 @@ This step links a Segment source to your Databricks workspace/catalog.
 1. Navigate to `https://app.segment.com/<WORKSPACE_SLUG>/destinations/catalog/databricks-delta-lake`. 
 2. Click **Add Destination**, select a source, then click **Next**.
 3. Enter the name for your destination, then click **Create destination**.
-4. Enter the connection settings using the values noted above (leave the Service Principal fields blank).
+4. Enter the connection settings using the values noted above (leave the service principal fields blank).