docs(task_history): the acceleration refresh task is acceleration_refresh Eighteen deployment guides (and their 2.0.x-2.3.x snapshots) told readers to correlate object reads and accelerator spans with a task named accelerated_table_refresh. No release has ever recorded that name: the refresh span is declared as "acceleration_refresh" in the accelerated-table refresh task, and the task column is the span name unless a task_override label is present. The name a reader pastes into a task_history query has to match exactly, so a fabricated one returns no rows. cli/reference/trace.md already carried the correct name on these same snapshots.

docs(duckdb): document duckdb_threads (#2156) `ParameterSpec::component("threads")` has shipped on the DuckDB accelerator since v2.1.3 (spiceai/spiceai#12276), but no docs page names it: `grep -rn duckdb_threads website/` returned nothing. Without it, the only way to stop each DuckDB instance sizing a node-sized thread pool in a CPU-constrained container is to change the whole CPU entitlement. Add the parameter to the DuckDB accelerator's Configuration Parameters list and note the entitlement-derived sizing in the page's CPU section. Present in v2.2.1 as well as trunk, so the version-2.2.x snapshot gets the same rows. Co-authored-by: claudespice <claudespice@users.noreply.github.com>