Apply suggestion from @mirnawong1

matthewshaver · mirnawong1 · web-flow · commit 2cd1a18fda70 · 2026-02-09T09:56:46.000-05:00
Co-authored-by: Mirna Wong &lt;89008547+mirnawong1@users.noreply.github.com&gt;
diff --git a/website/snippets/_fusion-threads.md b/website/snippets/_fusion-threads.md
@@ -7,4 +7,4 @@
 
 For BigQuery and Redshift, setting `--threads 0` (or omitting the setting) allows Fusion to dynamically optimize parallelism.
 
-For Snowflake and Databricks, only `threads: 1` is respected. If you are seeing timeouts due to Fusion parallelism, try setting `threads: 1` to see if this resolves the issue.
+- For BigQuery and Redshift, <Constant name="fusion"/> respects user-set thread values to accommodate warehouse-specific limits. Setting `--threads 0` (or omitting the setting) allows <Constant name="fusion"/> to dynamically optimize parallelism.

Original file line number	Diff line number	Diff line change
`@@ -7,4 +7,4 @@`
`7`	`7`
`8`	`8`	For BigQuery and Redshift, setting `--threads 0` (or omitting the setting) allows Fusion to dynamically optimize parallelism.
`9`	`9`
`10`		-For Snowflake and Databricks, only `threads: 1` is respected. If you are seeing timeouts due to Fusion parallelism, try setting `threads: 1` to see if this resolves the issue.
	`10`	+- For BigQuery and Redshift, <Constant name="fusion"/> respects user-set thread values to accommodate warehouse-specific limits. Setting `--threads 0` (or omitting the setting) allows <Constant name="fusion"/> to dynamically optimize parallelism.