docs: name the job types a deployment reports for index builds and drops

Sophon v1.8.1 runs an index build as reindex_<algorithm> unless the request is create-only, which runs as create_<algorithm>, and tears a dropped table down as drop_table or drop_object depending on how the deployment stores its catalog. Say so rather than naming a single type.

docs/web/management/table.mdx

@@ -229,11 +229,11 @@ does not support it refuses every clone.
 </Warning>
 
 <Note>
-**Enterprise job type:** `drop_table`. On a deployment that drops tables in the
-background, fences the table's directory with a marker and deletes its content
-as a job -- see
-[Background jobs](/maintenance/background-jobs#teardown) for the namespace
-and view equivalent.
+**Enterprise job type:** on a deployment that drops tables in the background,
+the teardown runs as a job: `drop_table`, which fences the table's directory
+with a marker and deletes its content, or `drop_object`, depending on how the
+deployment stores its catalog. See
+[Background jobs](/maintenance/background-jobs#teardown).
 </Note>
 
 ## Dropping {#drop}

docs/web/sql/ddl/index.mdx

@@ -28,9 +28,11 @@ multi-column index, use the SDK's [`create_index`](/indexing).
 </Note>
 
 <Note>
-**Enterprise job type:** `create_ivf_pq`, `create_btree`, `create_fts`, and one
-more per algorithm -- the type names which algorithm is building, not a
-different feature. See [Build & Repair](/indexing/reindexing).
+**Enterprise job type:** `reindex_` followed by the algorithm, such as
+`reindex_btree` or `reindex_ivf_pq`; the name says which algorithm is building,
+not a different feature. An SDK build that must not replace an existing index
+runs as `create_` followed by the algorithm instead. See
+[Build & Repair](/indexing/reindexing).
 </Note>
 
 ## DROP INDEX {#drop}

docs/web/sql/ddl/table.mdx

@@ -167,7 +167,8 @@ Removes the table and every version of it. There is no undrop.
 </Warning>
 
 <Note>
-**Enterprise job type:** `drop_table`. See
+**Enterprise job type:** `drop_table` or `drop_object`, depending on how the
+deployment stores its catalog. See
 [Background jobs](/maintenance/background-jobs#teardown).
 </Note>