Merge branch 'current' into update-timespine

website/docs/docs/build/incremental-microbatch.md

@@ -35,8 +35,8 @@ The `page_view_start` column in `page_views` is configured as that model's `even
 ```yaml
 models:
   - name: page_views
-     config:
-       event_time: page_view_start
+    config:
+      event_time: page_view_start
 ```
 </File>
 We run the `sessions` model on October 1, 2024, and then again on October 2. It produces the following queries:
@@ -52,7 +52,8 @@ We run the `sessions` model on October 1, 2024, and then again on October 2. It
     materialized='incremental',
     incremental_strategy='microbatch',
     event_time='session_start',
-    begin='2020-01-01'
+    begin='2020-01-01',
+    batch_size='day'
 ) }}
 
 with page_views as (
@@ -152,7 +153,7 @@ Several configurations are relevant to microbatch models, and some are required:
 |----------|------|---------------|---------|
 | `event_time` | Column  (required)   | The column indicating "at what time did the row occur." Required for your microbatch model and any direct parents that should be filtered.          | N/A     |
 | `begin`      | Date (required)   | The "beginning of time" for the microbatch model. This is the starting point for any initial or full-refresh builds. For example, a daily-grain microbatch model run on `2024-10-01` with `begin = '2023-10-01` will process 366 batches (it's a leap year!) plus the batch for "today."        | N/A     |
-| `batch_size` | String (optional)  | The granularity of your batches. The default is `day` (and currently this is the only granularity supported).             | `day`   |
+| `batch_size` | String (required)  | The granularity of your batches. The default is `day` (and currently this is the only granularity supported).             | `day`   |
 | `lookback`   | Integer (optional) | Process X batches prior to the latest bookmark to capture late-arriving records.                                         | `0`     |
 
 <Lightbox src="/img/docs/building-a-dbt-project/microbatch/event_time.png" title="The event_time column configures the real-world time of this record"/>
@@ -267,8 +268,8 @@ Where you’ve also set an `event_time` for the model’s direct parents - in th
 ```yaml
 models:
   - name: stg_events
-     config:
-       event_time: my_time_field
+    config:
+      event_time: my_time_field
 ```
 
 </File>

website/docs/docs/cloud-integrations/avail-sl-integrations.md

@@ -29,7 +29,7 @@ import AvailIntegrations from '/snippets/_sl-partner-links.md';
 
 - <span><a href="https://docs.getdbt.com/docs/dbt-cloud-apis/sl-api-overview" target="_self">{frontMatter.meta.api_name}</a></span> to learn how to integrate and query your metrics in downstream tools.
 - [dbt Semantic Layer API query syntax](/docs/dbt-cloud-apis/sl-jdbc#querying-the-api-for-metric-metadata) 
-- [Hex dbt Semantic Layer cells](https://learn.hex.tech/docs/logic-cell-types/transform-cells/dbt-metrics-cells) to set up SQL cells in Hex.
+- [Hex dbt Semantic Layer cells](https://learn.hex.tech/docs/explore-data/cells/data-cells/dbt-metrics-cells) to set up SQL cells in Hex.
 - [Resolve 'Failed APN'](/faqs/Troubleshooting/sl-alpn-error) error when connecting to the dbt Semantic Layer.
 - [dbt Semantic Layer on-demand course](https://learn.getdbt.com/courses/semantic-layer)
 - [dbt Semantic Layer FAQs](/docs/use-dbt-semantic-layer/sl-faqs)

website/docs/docs/cloud-integrations/set-up-snowflake-native-app.md

@@ -144,7 +144,7 @@ Check that the SL user has been granted access to the `dbt_sl_llm` schema and ma
 
 <Expandable alt_header="Need to update the dbt configuration options used by the Native App" >
 
-If there's been an update to the dbt Cloud account ID, access URL, or API service token, you need to update the configuration for the dbt Snowflake Native App. In Snowflake, navigate to the app's configuration page and delete the existing configurations. Add the new configuration and then run `CALL app_public.restart_ap ();` in the application database in Snowsight. 
+If there's been an update to the dbt Cloud account ID, access URL, or API service token, you need to update the configuration for the dbt Snowflake Native App. In Snowflake, navigate to the app's configuration page and delete the existing configurations. Add the new configuration and then run `CALL app_public.restart_app();` in the application database in Snowsight. 
 </Expandable>
 
 <Expandable alt_header="Are environment variables supported in the Native App?" >

website/docs/reference/resource-properties/constraints.md

@@ -47,7 +47,7 @@ models:
         columns: [first_column, second_column, ...]
       - type: foreign_key # multi_column
         columns: [first_column, second_column, ...]
-        to: "{{ ref('other_model_name') }}"
+        to: ref('other_model_name')
         to_columns: [other_model_first_column, other_model_second_columns, ...]
       - type: check
         columns: [first_column, second_column, ...]
@@ -64,7 +64,7 @@ models:
           - type: not_null
           - type: unique
           - type: foreign_key
-            to: "{{ ref('other_model_name') }}"
+            to: ref('other_model_name')
             to_columns: other_model_column
           - type: ...
 ```