From 01cefd58bd1fd76b82d51c9039578dbec65b921d Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 29 Oct 2024 18:28:17 -0400 Subject: [PATCH] Update databricks-configs.md Editorial changes --- .../docs/reference/resource-configs/databricks-configs.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/website/docs/reference/resource-configs/databricks-configs.md b/website/docs/reference/resource-configs/databricks-configs.md index 0d470fcec68..d08a75d65d5 100644 --- a/website/docs/reference/resource-configs/databricks-configs.md +++ b/website/docs/reference/resource-configs/databricks-configs.md @@ -636,11 +636,9 @@ insert into analytics.replace_where_incremental ### The `microbatch` strategy -The Databricks adapter implements the `microbatch` strategy using `replace_where`. -As such, please take note of the requirements and caution statements for `replace_where` above. -For general discussion of using this strategy, please see the [microbatch reference page](/docs/build/incremental-microbatch). +The Databricks adapter implements the `microbatch` strategy using `replace_where`. Note the requirements and caution statements for `replace_where` above. For more information about this strategy, see the [microbatch reference page](/docs/build/incremental-microbatch). -In the example below, the upstream table `events` has been annotated with an `event_time` column called `ts` in its schema file. +In the following example, the upstream table `events` have been annotated with an `event_time` column called `ts` in its schema file.