Clarify the behavior of refresh_on_startup: auto

website/docs/features/data-acceleration/data-refresh.md

@@ -313,16 +313,16 @@ In this example a query against `accelerated_dataset` within Spice like `SELECT
 | Required                    | No     |
 | Default Value               | `auto` |
 
-Controls whether Spice refreshes the dataset when the service starts.
+Controls the refresh behavior of an accelerated dataset across restarts.
 
 `refresh_on_startup` Options:
 
-- `auto` (Default) – Skips the refresh on startup if the dataset is already accelerated and:
-  - The refresh interval hasn't elapsed, or  
-  - No refresh interval is defined.  
-- `always` – Forces a dataset refresh on every startup, regardless of the existing acceleration state.  
+- `auto` (Default) – Maintains refresh state across restarts:
+  - With `refresh_check_interval`: Schedules next refresh based on last successful refresh time, triggering immediately if interval has already elapsed
+  - Without `refresh_check_interval`: No refresh (on-demand only)
+- `always` – Forces a dataset refresh on every startup, regardless of the existing acceleration state.
 
-Setting `refresh_on_startup: always` ensures that accelerated data is always refreshed to match the source when the service restarts. This is useful in **development environments** or when **data consistency is critical** after deployment.  
+Setting `refresh_on_startup: always` ensures that accelerated data is always refreshed to match the source when the service restarts. This is useful in **development environments** or when **data consistency is critical** after deployment.
 
 Example Configuration:
 

website/docs/reference/spicepod/datasets.md

@@ -287,14 +287,14 @@ Optional. Defines the maximum number of retry attempts when refresh retries are
 
 ## `acceleration.refresh_on_startup`
 
-Optional. Controls whether Spice refreshes the dataset when the service starts. Defaults to `auto`.
+Optional. Controls the refresh behavior of an accelerated dataset across restarts. Defaults to `auto`.
 
 ### Supported Values
 
-- **`auto` (Default)** – Skips the refresh on startup if the dataset is already accelerated and:
-  - The refresh interval hasn't elapsed, or  
-  - No refresh interval is defined.  
-- **`always`** – Forces a dataset refresh on every startup, regardless of the existing acceleration state.  
+- **`auto` (Default)** – Maintains refresh state across restarts:
+  - With `refresh_check_interval`: Schedules next refresh based on last successful refresh time, triggering immediately if interval has already elapsed
+  - Without `refresh_check_interval`: No refresh (on-demand only)
+- **`always`** – Forces a dataset refresh on every startup, regardless of the existing acceleration state.
 
 Setting `refresh_on_startup: always` ensures that accelerated data is always refreshed to match the source when the service restarts. This is useful in **development environments** or when **data consistency is critical** after deployment.