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/ddl/function.mdx

@@ -23,7 +23,7 @@ Parameter and result types are Arrow type names, not SQL ones: `int64`,
 unless it is declared `NOT NULL`.
 
 The body is Python source. Its dependencies are declared with it and are part
-of the **immutable function version** -- changing one produces a new version
+of the **immutable function version**. Changing one produces a new version
 rather than altering the registered one, so a column filled by an earlier
 version is unaffected.
 
@@ -40,7 +40,7 @@ version is unaffected.
 | | |
 | --- | --- |
 | `LANGUAGE` other than `python` | refused |
-| `pip` and `conda` together | refused -- pick one |
+| `pip` and `conda` together | refused (pick one) |
 | `conda_channels` without `conda` | refused |
 | `gpu` set to anything but `'true'` | refused |
 | An empty body | refused |
@@ -69,13 +69,13 @@ DROP FUNCTION IF EXISTS embed WITH (version = '1')
 DROP FUNCTION embed WITH (version = '1', cascade = 'true')
 ```
 
-`version` is required -- a function is a set of immutable versions, and
+`version` is required: a function is a set of immutable versions, and
 dropping is always of one specific version, never "the function" as a whole.
 
 <Warning>
 Without `cascade = 'true'`, dropping a version that a column still pins fails
 rather than breaking that column silently. Passing it drops the version and
-lets columns pinned to it stop refreshing -- they keep their last-filled
+lets columns pinned to it stop refreshing. They keep their last-filled
 values, per [Guarantees](/basics/guarantees#jobs).
 </Warning>
 

docs/web/sql/ddl/index.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Index"
 sidebarTitle: "Index"
-description: "CREATE INDEX and DROP INDEX — one column, with the algorithm chosen by USING."
+description: "CREATE INDEX and DROP INDEX: one column, with the algorithm chosen by USING."
 icon: bolt
 keywords: ["create index", "drop index", "sql"]
 ---

docs/web/sql/ddl/job.mdx

@@ -8,8 +8,8 @@ keywords: ["show jobs", "show errors", "pause job", "resume job", "cancel job",
 
 <Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
-A [job](/basics/jobs) is not a catalog object -- it has no schema and is not
-namespaced -- but it has its own SQL statements, grouped here the same way the
+A [job](/basics/jobs) is not a catalog object (it has no schema and is not
+namespaced), but it has its own SQL statements, grouped here the same way the
 catalog objects are.
 
 ## SHOW JOBS {#show}
@@ -18,7 +18,7 @@ catalog objects are.
 SHOW JOBS
 ```
 
-Every job the server knows about -- id, type, state, creation time. The SQL
+Every job the server knows about: id, type, state, creation time. The SQL
 counterpart of `list_jobs`.
 
 ## SHOW ERRORS {#errors}
@@ -44,7 +44,7 @@ fewer filled rows than you expected.
 | Tables the server does not open directly | not supported |
 
 Without `FOR JOB` this surveys recent failures and stops at 32 jobs. When the
-listing stops at your `LIMIT`, the message says so -- narrow with `FOR JOB`
+listing stops at your `LIMIT`, the message says so. Narrow with `FOR JOB`
 rather than raising the limit blindly.
 
 ## PAUSE JOB {#pause}
@@ -66,7 +66,7 @@ CANCEL JOB 'j-ci-abc-def'
 ```
 
 The job id is always a quoted string literal. All three take exactly one and
-nothing after it -- a second token on the line is a syntax error rather than
+nothing after it: a second token on the line is a syntax error rather than
 being ignored.
 
 <Note>

docs/web/sql/ddl/materialized-view.mdx

@@ -8,8 +8,8 @@ keywords: ["materialized view", "create materialized view", "show materialized v
 
 <Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
-A materialized view stores a query's result as rows, kept current by a refresh
--- the counterpart to a [view](/sql/ddl/view), which stores only the query.
+A materialized view stores a query's result as rows, kept current by a refresh.
+It is the counterpart to a [view](/sql/ddl/view), which stores only the query.
 
 <Note>
 Materialized views are off by default in LanceDB Enterprise and have to be enabled
@@ -51,7 +51,7 @@ and compatibility notes for older server versions.
 ## Dropping one {#drop}
 
 A materialized view **is** a table, so it is dropped with
-[`DROP TABLE`](/sql/ddl/table#drop) -- which is also why dropping one removes
+[`DROP TABLE`](/sql/ddl/table#drop). For the same reason, dropping one removes
 stored rows, unlike dropping a [view](/sql/ddl/view#drop).
 
 <Note>

docs/web/sql/ddl/namespace.mdx

@@ -1,14 +1,14 @@
 ---
 title: "Namespace"
 sidebarTitle: "Namespace"
-description: "CREATE SCHEMA and DROP SCHEMA — the SQL spelling of namespace DDL."
+description: "CREATE SCHEMA and DROP SCHEMA: the SQL spelling of namespace DDL."
 icon: folder-tree
 keywords: ["namespace", "schema", "create schema", "drop schema", "sql"]
 ---
 
 <Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
-A [namespace](/management/namespace) is addressed in SQL as a `SCHEMA` -- the
+A [namespace](/management/namespace) is addressed in SQL as a `SCHEMA`, the
 standard's name for the same concept.
 
 ## CREATE SCHEMA {#create}
@@ -39,8 +39,8 @@ DROP SCHEMA `a$b` RESTRICT
 <Warning>
 `CASCADE` is rejected: **"DROP SCHEMA CASCADE is not supported; drop the
 objects inside first."** A namespace's tables, views and other objects must be
-dropped explicitly before the namespace itself can go. `RESTRICT` -- the
-default -- states that requirement rather than changing it.
+dropped explicitly before the namespace itself can go. `RESTRICT` (the
+default) states that requirement rather than changing it.
 </Warning>
 
 ## What to read next {#next}

docs/web/sql/ddl/table.mdx

@@ -15,7 +15,7 @@ CREATE TABLE documents (id BIGINT, title VARCHAR, created_at TIMESTAMP)
 CREATE TABLE recent AS SELECT * FROM documents WHERE created_at > now() - INTERVAL '7 days'
 ```
 
-Column types are Arrow types under SQL names -- see [Data types](/sql/data-types).
+Column types are Arrow types under SQL names. See [Data types](/sql/data-types).
 A table inside a [namespace](/sql/ddl/namespace) is written as a dotted path:
 `prod.events.clicks`.
 
@@ -25,7 +25,7 @@ A table inside a [namespace](/sql/ddl/namespace) is written as a dotted path:
 DESCRIBE documents
 ```
 
-The table's columns and types, without a plan -- the SQL counterpart of
+The table's columns and types, without a plan. The SQL counterpart of
 `table.schema`.
 
 ## ALTER TABLE {#alter}
@@ -37,7 +37,7 @@ name.
 
 SQL `ADD COLUMN` requires an `AS` binding, so a plain column such as
 `ALTER TABLE t ADD COLUMN c INT` is rejected. Add an empty, nullable column
-with the SDK instead -- see
+with the SDK instead. See
 [Add nullable columns](/management/table#schema-add-nullable-columns).
 
 ### A computed column {#computed-column}
@@ -47,7 +47,7 @@ ALTER TABLE t ADD COLUMN doubled AS value * 2
 ```
 
 `AS <expression>` declares a [computed column](/feature-engineering/add-computed-column).
-The column is committed empty and the expression is stored, not evaluated --
+The column is committed empty and the expression is stored, not evaluated:
 declaring one on a billion-row table costs what declaring one on an empty table
 costs. [`REFRESH COLUMN`](/sql/dml/refresh) fills it.
 
@@ -129,9 +129,9 @@ rows a sample would draw from are not all in the fragments yet.
 | --- | --- |
 | `ALTER TABLE ... DROP COLUMN` | not supported |
 
-Dropping, renaming, or retyping a column is an SDK operation --
-[`drop_columns`](/management/table#schema) and
-[`alter_columns`](/management/table#schema) -- not a SQL statement.
+Dropping, renaming, or retyping a column is an SDK operation
+([`drop_columns`](/management/table#schema) and
+[`alter_columns`](/management/table#schema)), not a SQL statement.
 
 ## CLONE {#clone}
 
@@ -147,7 +147,7 @@ copying them, so it costs one metadata commit regardless of the source's size.
 
 `AT` pins the point in the source's history to clone. A bare integer is a
 version and a bare quoted string is a timestamp; `VERSION`, `TAG` and
-`TIMESTAMP` say so explicitly, and a tag always needs its keyword -- a bare
+`TIMESTAMP` say so explicitly, and a tag always needs its keyword: a bare
 quoted string cannot be both a tag name and a timestamp.
 
 <Warning>

docs/web/sql/ddl/view.mdx

@@ -1,7 +1,7 @@
 ---
 title: "View"
 sidebarTitle: "View"
-description: "CREATE VIEW and DROP VIEW — a saved query, evaluated when read."
+description: "CREATE VIEW and DROP VIEW: a saved query, evaluated when read."
 icon: eye
 keywords: ["create view", "drop view", "sql", "catalog"]
 ---
@@ -9,7 +9,7 @@ keywords: ["create view", "drop view", "sql", "catalog"]
 <Badge color="red">Enterprise</Badge> [SQL runs in LanceDB Enterprise.](/sql)
 
 A view stores a **query**, not rows. Reading it runs the query against current
-data, so a view is never stale -- and never faster than the query it wraps. It
+data, so a view is never stale, and never faster than the query it wraps. It
 is the counterpart to a [materialized view](/sql/ddl/materialized-view), which
 stores rows and is brought up to date by a refresh; both are
 [catalog objects](/basics/catalog) defined by a query, differing only in when
@@ -27,8 +27,8 @@ FROM "documents" AS t1
 INNER JOIN "categories" AS t2 ON t1.ints = t2.ints
 ```
 
-The statement returns the view's schema -- column name, data type, nullability
--- resolved from the query at creation time. Anything the
+The statement returns the view's schema (column name, data type, nullability),
+resolved from the query at creation time. Anything the
 [dialect](/sql/functions) supports can define one: joins, predicates,
 aggregates, window functions.
 
@@ -50,7 +50,7 @@ the view would have produced and then discarded.
 DROP VIEW "recent_matches"
 ```
 
-Removes the saved query. Unlike dropping a table, no data is removed -- there
+Removes the saved query. Unlike dropping a table, no data is removed: there
 was none to begin with.
 
 ## Listing {#listing}
@@ -62,10 +62,10 @@ catalog distinguishes them:
 | --- | --- |
 | view names | the views in the database |
 | table names | the tables |
-| relation names | everything queryable -- both |
+| relation names | everything queryable (both) |
 
 Use the relation listing when the question is "what can I select from," and the
-separate listings when the distinction matters -- before dropping, for
+separate listings when the distinction matters: before dropping, for
 instance, since dropping a view removes only the saved query while dropping a
 table removes data.