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(s3): document the refresh_skip parameter An accelerated single-object S3 dataset is wrapped in S3SingleFileCached, which HEADs the object before each full/append refresh and skips the refresh when the version ID or ETag still matches. The knob that controls this, `refresh_skip`, was undocumented on every page and in every snapshot, even though the metric that counts its effect (`dataset_acceleration_refresh_data_fetches_skipped`) was already documented. - add a `refresh_skip` row to the S3 params table - add a 'Refresh Skipping for Single-File Datasets' section to the S3 deployment guide covering the params: scope, the refresh_mode gating, the refresh_sql override reset, and the skip counter The parameter and its gate are unchanged from v1.10 through trunk, so this lands in vNext plus every snapshot that has it.