add img and rn

website/docs/docs/dbt-versions/release-notes.md

@@ -20,6 +20,7 @@ Release notes are grouped by month for both multi-tenant and virtual private clo
 
 ## October 2024
 
+- **New**: Use the `event_time` configuration to specify when an event occurred. This configuration is required for [Incremental mircrobatch](/docs/build/incremental-microbatch) and can be added to ensure you're comparing overlapping times in [Advanced CI's compare changes](/docs/deploy/advanced-ci). Available in dbt Cloud Versionless and dbt Core v1.9 and higher. Refer to [event_time](/docs/reference/resource-configs/event-time) for more information.
 - **Fix:** Previously, POST requests to the Jobs API with invalid `cron` strings would return HTTP response status code 500s but would update the underlying entity. Now, POST requests to the Jobs API with invalid `cron` strings will result in status code 400s, without the underlying entity being updated.
 - **Fix:** Fixed an issue where the `Source` view page in dbt Explorer did not correctly display source freshness status if older than 30 days.
 - **Fix:** The UI now indicates when the description of a model is inherited from a catalog comment.

website/docs/docs/deploy/advanced-ci.md

@@ -36,10 +36,12 @@ You can set a [event_time](/reference/resource-configs/event-time) for a model,
 
 When configured, `event_time` enables compare changes to:
 
-- Compare data in CI vs. production for overlapping times only, reducing false discrepancies.
+- Compare data in CI versus production for overlapping times only, reducing false discrepancies.
 - Handle scenarios where CI contains fresher data than production by using only the overlapping timeframe, which avoids incorrect row-count changes.
 - Account for subset data builds in CI without flagging filtered-out rows as "deleted" when compared with production.
-- Coming soon, you'll be able to add a flag to the `dbt compare` command to select the specific time slice to compare.
+- Coming soon, you'll be able to add a flag to the command list allowing you to select the specific time slice to compare.
+
+<Lightbox src="/img/docs/deploy/apples_to_apples.png" title="event_time ensures the same time-slice of data is accurately compared between your CI and production environments." />
 
 ## About the cached data
 

website/docs/reference/resource-configs/event-time.md

@@ -141,7 +141,7 @@ sources:
 
 Set the `event_time` to the name of the field that represents the timestamp of the event, as opposed to a date like data loading date.  You can configure `event_time` for a [model](/docs/build/models), [seed](/docs/build/seeds), or [source](/docs/build/sources) in your `dbt_project.yml` file, property YAML file, or config block. 
 
-`event_time` is required for [Incremental mircrobatch](/docs/build/incremental-microbatch) and [Advanced CI compare changes](/docs/deploy/advanced-ci) in CI/CD workflows, where it ensures the same time-slice of data is correctly compared between your CI and production environments.
+`event_time` is required for [Incremental mircrobatch](/docs/build/incremental-microbatch) and [Advanced CI's compare changes](/docs/deploy/advanced-ci) in CI/CD workflows, where it ensures the same time-slice of data is correctly compared between your CI and production environments.
 
 When you configure `event_time`, it enables compare changes to: