docs: clean up prose flagged by the shared Vale rules (#4596)

The existing docs have 254 findings from our shared Vale rules.
Contributors would otherwise inherit these when editing the same lines.

Clean up the prose across 80 pages: correct product names and a repeated
word, simplify a few phrases, and replace dashes with punctuation that
fits each sentence. The pinned Vale scan now reports zero findings, with
no suppressions.

docs/web/sql/dml/copy.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Copy"
 sidebarTitle: "Copy"
-description: "COPY ... TO — writing a query result to object storage as files."
+description: "COPY ... TO: writing a query result to object storage as files."
 icon: file-export
 keywords: ["copy", "export", "parquet", "sql"]
 ---
@@ -17,7 +17,7 @@ COPY (SELECT id, title FROM documents) TO 's3://bucket/export/' STORED AS PARQUE
 ```
 
 Writes a query result to object storage. This is the export path when the
-consumer is another engine rather than an application -- results land as files
+consumer is another engine rather than an application: results land as files
 rather than streaming to a client.
 
 ## What to read next {#next}

docs/web/sql/dml/delete.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Delete"
 sidebarTitle: "Delete"
-description: "DELETE FROM ... WHERE — rows are marked, not erased."
+description: "DELETE FROM ... WHERE: rows are marked, not erased."
 icon: trash
 keywords: ["delete", "sql"]
 ---
@@ -21,7 +21,7 @@ for as long as the version holding it survives
 [retention](/maintenance/cleanup).
 
 Commits a new table version, so [versioning](/management/table#versioning) and
-the [write guarantees](/basics/guarantees#writes) apply -- including that the
+the [write guarantees](/basics/guarantees#writes) apply, including that the
 version advances even when the statement affects zero rows.
 
 ## What to read next {#next}

docs/web/sql/dml/insert.mdx

@@ -18,7 +18,7 @@ INSERT INTO archive SELECT * FROM documents WHERE created_at < '2026-01-01'
 server-side, without a round trip through your process.
 
 Commits a new table version, so [versioning](/management/table#versioning) and
-the [write guarantees](/basics/guarantees#writes) apply -- including that the
+the [write guarantees](/basics/guarantees#writes) apply, including that the
 version advances even when the statement affects zero rows.
 
 ## What to read next {#next}
@@ -28,6 +28,6 @@ version advances even when the statement affects zero rows.
     The SDK equivalent.
   </Card>
   <Card title="Merge Insert" icon="code-merge" href="/ingestion/merge-insert">
-    Upsert -- matching incoming rows against existing keys -- has no SQL form.
+    Upsert (matching incoming rows against existing keys) has no SQL form.
   </Card>
 </CardGroup>

docs/web/sql/dml/refresh.mdx

@@ -27,7 +27,7 @@ REFRESH COLUMN embedding ON documents WHERE created_at > '2026-01-01'
 
 A refresh gives values to rows that lack them, recomputes rows whose inputs
 changed, and **leaves other filled rows alone**. That makes it idempotent, cheap
-to repeat as data arrives, and safe to re-run after a failure -- though a re-run
+to repeat as data arrives, and safe to re-run after a failure, though a re-run
 can recompute values the failed run had already written.
 
 `WHERE` scopes the refresh, which is how you fill a slice and check it before

docs/web/sql/dml/update.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Update"
 sidebarTitle: "Update"
-description: "UPDATE ... SET ... WHERE — and why it does not recompute derived columns."
+description: "UPDATE ... SET ... WHERE, and why it does not recompute derived columns."
 icon: pen
 keywords: ["update", "sql"]
 ---
@@ -19,12 +19,12 @@ clause every row is updated.
 <Warning>
 An update does not recompute [computed columns](/feature-engineering/add-computed-column)
 that derive from the column you changed. Those rows keep the value computed from
-the old input until the next refresh recomputes them -- see
+the old input until the next refresh recomputes them. See
 [Guarantees](/basics/guarantees#jobs).
 </Warning>
 
 Commits a new table version, so [versioning](/management/table#versioning) and
-the [write guarantees](/basics/guarantees#writes) apply -- including that the
+the [write guarantees](/basics/guarantees#writes) apply, including that the
 version advances even when the statement affects zero rows.
 
 ## What to read next {#next}