docs(website): describe runtime rejection and checking for any warehouse

The first problem card and the Check step on the landing page named
Snowflake as if it were the product. They now speak of the warehouse in
general, and the Check step says Snowflake is the dialect it checks
today. The SQ0201 example still shows real Snowflake behaviour.

Author: kvlonge

website/public/index.html

@@ -102,8 +102,8 @@ <h2>Where SQL translation goes wrong</h2>
 					</div>
 					<div class="problem">
 						<div class="card">
-							<h3>Snowflake rejects it at runtime</h3>
-							<p>Invalid Snowflake SQL only shows up when the query runs on the warehouse, often mid-pipeline.</p>
+							<h3>The warehouse rejects it at runtime</h3>
+							<p>Invalid SQL only shows up when the query runs on the warehouse, often mid-pipeline.</p>
 						</div>
 						<div class="card">
 							<h3>Tests pass for the wrong engine</h3>
@@ -132,8 +132,8 @@ <h2>From warehouse SQL to DuckDB SQL</h2>
 						<div class="step">
 							<div class="step-text">
 								<span class="num">01 · Check</span>
-								<h3>Catch what Snowflake would reject</h3>
-								<p>Parses Snowflake SQL and reports the syntax Snowflake would reject. No schema needed. Each error has a code and the exact span; rejections also come with a fix.</p>
+								<h3>Catch what the warehouse would reject</h3>
+								<p>Snowflake today: parses Snowflake SQL and reports the syntax Snowflake would reject. No schema needed. Each error has a code and the exact span; rejections also come with a fix.</p>
 								<p class="more"><a href="/docs/cli/check/">How checking works →</a></p>
 							</div>
 <pre class="terminal"><span class="cmd">sqlquack check</span>