edits

Author: katarzyna-koltun-mx

content/en/docs/appstore/use-content/platform-supported-content/modules/databricks-edc.md

@@ -13,31 +13,38 @@ This how-to describes the steps required to enable your app to use the External
 
 ## Prerequisites
 
-As an additional resource on how to use bring your own JDBC driver with the external database connector, see [External Database Connector](https://docs.mendix.com/appstore/modules/external-database-connector/#byod) although this explanation is more generic than what will follow in this documentation.
+For some general information on how to use bring your own JDBC driver with the external database connector, read [External Database Connector: Configure for Any Database](https://docs.mendix.com/appstore/modules/external-database-connector/#byod).
 
 ## Configuring the Connection Between Your Mendix App and Databricks
 
 To connect your Mendix application to Databricks with the External Database connector, follow these steps:
 
 1. Install the [External Database connector](https://marketplace.mendix.com/link/component/219862) version 5.1.1 or higher. 
-2. In the **Settings** of you module you can add a **Java Dependency** of the needed Databricks JDBC Driver, this way the dependency will be downloaded on running your project. To enable this you will need the following:
-   * **Group ID** - set to **com.databricks**
-   * **Artifact ID** - set to **databricks-jdbc**
-   * **Version** - set to **2.7.1**
+2. Ensure that you have the required Databricks JDBC Driver by choosing one of the following options:
+
+    * To have the dependency downloaded automatically on running your project, add a **Java Dependency** in the **Settings** of you module and provide the following information:    
+        * **Group ID** - set to **com.databricks**
+        * **Artifact ID** - set to **databricks-jdbc**
+        * **Version** - set to **2.7.1**
 
    {{< figure src="static/attachments/appstore/platform-supported-content/modules/databricks/JavaDependency.png" >}}
 
-   Or alternatively you can download version 2.7.1 of the [JDBC driver](https://www.databricks.com/spark/jdbc-drivers-archive) that Databricks provides and put the .jar file into the userlib of your Mendix project.
-3. Run you Mendix project and run the [Connect to Database wizard](/appstore/modules/external-database-connector/#configuration) and select **Other** as the database type.
+   * To install the dependency manually, download version 2.7.1 of the [JDBC driver](https://www.databricks.com/spark/jdbc-drivers-archive) that Databricks provides and put the .jar file into the *userlib* of your Mendix project.
+
+3. Run you Mendix project and run the [Connect to Database wizard](/appstore/modules/external-database-connector/#configuration), selecting **Other** as the database type.
 
    {{< figure src="static/attachments/appstore/platform-supported-content/modules/databricks/DatabricksConfig.png" >}}
 
 4. Provide a name for the database connection document.
-5. As a username use "token" and as your password use the personal access token (PAT) that you can generate via the user settings in Databricks:
+5. Enter the following connection details:
+
+    * **User name** - set to **token**
+    * **Password** - set to the personal access token (PAT) that you can generate through the user settings in Databricks:
 
    {{< figure src="static/attachments/appstore/platform-supported-content/modules/databricks/PAT.png" >}}
 
-7. In your Databricks account find the JDBC URL related to the SQL Warehouse or Cluster you are using and copy it into the JDBC URL field and add UID=token;PWD=**PAT** where **PAT** should be replaced with your actual PAT.
+7. In your Databricks account find the JDBC URL related to the SQL warehouse or cluster which you are using.
+8. Copy the URL into the **JDBC URL** field and add *UID=token;PWD=`PAT`*, where `PAT` is your actual PAT.
 
    {{< figure src="static/attachments/appstore/platform-supported-content/modules/databricks/JDBC_URL.png" >}}
 
@@ -51,7 +58,11 @@ You can now configure the queries that you need to run on your Databricks databa
 
 ## Configuring a Basic Query
 
-In this section we will show you a very basic example of how to use the database connector to execute a query on your Databricks data. To do this you can create some data in your Databricks workspace. Navigate to the SQL Editor in your workspace and run the folowing sql command:
+This section shows a basic example of how to use the database connector to execute a query on your Databricks data. 
+
+### Creating Data in your Databricks Workspace
+
+If you do not have any test customer data in your Databricks workspace, you can create it by running the following SQL command in your workspace's SQL Editor:
 
 ```sql
 CREATE TABLE customerData (
@@ -73,10 +84,12 @@ INSERT INTO customerData (name, address, postal_code, gender) VALUES
     ('Thomas Mulder', 'Sterrenhof 7, Hemelrijk', '9012RS', 'Male'),
     ('Sophie Jansen', 'Kersenstraat 12, Fruitdorp', '0123TU', 'Female');
 ```
-The following image shows where to find the SQL Editor in Databricks:
+
 {{< figure src="static/attachments/appstore/platform-supported-content/modules/databricks/SQL_Editor.png" >}}
 
-This should have created a table with some entries that can now be queried from your Mendix application.
+### Querying the Data
+
+After you have created a table with some entries, you can now be query from your Mendix application.
 
 1. In your Mendix app, in the **App Explorer**, find and open the external connection document that you created with the Connect to Database wizard.
 2. In the **Name** field, enter a name for your query, for example, *CustomerData_Get*.
@@ -107,4 +120,4 @@ This should have created a table with some entries that can now be queried from
 
     {{< figure src="static/attachments/appstore/platform-supported-content/modules/databricks/JA_Query.png" >}}
 
-7. Use the microflow behind a microflow button and use the debugger to test if the objects are properly returned (or build a quick interface).
+7. Link the microflow to a microflow button and use the Debugger to test if the objects are properly returned.