Update dataset snapshots documentation

api-reference/add-media-to-existing-dataset.mdx

@@ -4,7 +4,7 @@
 ---
 
 <Card title="How This Helps" icon="hand-platter">
   Incrementally add new media (images or videos) to an already-indexed dataset without re-processing everything from scratch. New media is processed as an independent batch and becomes immediately visible. When ready, trigger a full reindex to re-cluster the entire dataset.
 </Card>
 
 <Note>
@@ -50,7 +50,7 @@
 
 | Parameter | Type | Default | Description |
 |-----------|------|---------|-------------|
 | `auto_reindex` | boolean | `false` | Automatically run a full reindex after the partial update completes |
 | `assume_role` | string | `null` | AWS IAM role ARN to assume for cross-account S3 access |
 | `batch_n_videos` | integer | `null` | Override auto-calculated video count (for resource allocation) |
 | `batch_n_images` | integer | `null` | Override auto-calculated image count (for resource allocation) |
@@ -146,7 +146,7 @@
   https://app.visual-layer.com/api/v1/dataset/<dataset_id>/add_media
 ```
 
 This runs a combined workflow: **partial update** (process new media) followed by **reindex** (re-cluster everything). The dataset returns to `READY` when complete.
 
 <Tip>
 Use `auto_reindex=true` when you want a single API call to handle everything. Omit it if you plan to add multiple batches before re-clustering.
@@ -154,9 +154,9 @@
 
 ---
 
 ## Manual Reindex
 
 If you added media without `auto_reindex`, the dataset enters `PARTIAL INDEX` status. You can trigger a manual reindex when ready:
 
 ```bash
 curl -X POST \
@@ -167,7 +167,7 @@
 **Response:** `HTTP 202 Accepted`
 
 <Note>
 The reindex endpoint only accepts datasets in `PARTIAL INDEX` status. If the dataset is still processing (`READ ONLY`), wait for it to finish before triggering reindex.
 </Note>
 
 ---
@@ -279,14 +279,14 @@
 | **400** | Bad Request | Invalid request parameters | Missing embedding config, invalid S3 URI, no media source provided, or multiple media sources in one request |
 | **403** | Forbidden | Feature disabled or insufficient permissions | `ADD_MEDIA_ENABLED` is false, or user lacks write access to the dataset |
 | **404** | Not Found | Dataset not found | Dataset does not exist, or the authenticated user does not have access to it |
 | **409** | Conflict | Dataset state incompatible | Dataset status is not `READY` or `PARTIAL INDEX`, or another add media / reindex operation is already running |
 | **500** | Internal Server Error | Server-side failure | File upload to S3 failed, or pipeline trigger failed |
 
 ### Reindex (`POST /api/v1/dataset/{dataset_id}/reindex`)
 
 | HTTP Code | Status | Meaning | Common Cause |
 |-----------|--------|---------|--------------|
 | **202** | Accepted | Reindex started successfully | Request valid, reindex pipeline triggered |
 | **404** | Not Found | Dataset not found | Dataset does not exist or user lacks access |
 | **409** | Conflict | Dataset state incompatible | Dataset status is not `PARTIAL INDEX` |
 | **500** | Internal Server Error | Server-side failure | Pipeline trigger failed |
@@ -331,14 +331,14 @@
 |-------|--------------|
 | Before | `READY` |
 | Processing | `READ ONLY` |
 | Awaiting Reindex | `PARTIAL INDEX` |
 | Reindexing | `READ ONLY` → `INDEXING` |
 | Complete | `READY` |
 
 For a description of each status value, see [Retrieve Dataset Status](/api-reference/retrieve-dataset-status).
 
 <Tip>
 With `auto_reindex=true`, the flow goes directly from `UPDATING` through reindexing back to `READY` without stopping at `PARTIAL INDEX`.
 </Tip>
 
 ---
@@ -365,5 +365,24 @@
 ```
 
 <Note>
 On-premises add media uses local file paths instead of S3 URIs. The `path` parameter must be an absolute path accessible from the pipeline container.
 </Note>
+
+---
+
+## Related Resources
+
+<CardGroup cols={2}>
+  <Card title="Saved Views API" icon="file-code-2" href="/api-reference/saved-views">
+    Create monitored views that automatically evaluate new media as it arrives.
+  </Card>
+  <Card title="Notifications API" icon="file-code-2" href="/api-reference/notifications">
+    Retrieve alerts generated when new media matches saved view filters.
+  </Card>
+  <Card title="Monitoring and Alerts" icon="blend" href="/docs/advanced-features/notifications">
+    Understand how adding media triggers monitoring evaluation and alert delivery.
+  </Card>
+  <Card title="Task Manager API" icon="list-checks" href="/api-reference/task-manager">
+    Track add media and reindex tasks programmatically.
+  </Card>
+</CardGroup>

api-reference/enrichment.mdx

@@ -87,7 +87,7 @@
 
 ---
 
 ## Check Applied Enrichments
 
 Retrieve the enrichment configuration currently applied to a dataset.
 
@@ -164,7 +164,7 @@
 }
 ```
 
-The response returns the `dataset_id` of the **new enriched copy**. Poll this new dataset's status endpoint until `status_new` reaches `READY` before running search or export operations on it.
+The response returns the `dataset_id` of the **new enriched copy**. Poll the status endpoint for this new dataset until `status_new` reaches `READY` before running search or export operations on it.
 
 <Note>
 The source dataset enters `READ ONLY` status while enrichment runs. The enriched copy is a separate dataset — it has its own `dataset_id` and appears as a new entry in your dataset inventory.

api-reference/exporting-a-dataset-via-curl-from-visual-layer.mdx

@@ -4,7 +4,7 @@ description: Export dataset metadata and media using the Visual Layer API—supp
 ---
 
 <Card title="How This Helps" icon="hand-platter">
-  Export your dataset's metadata, labels, and media files for use in training pipelines, annotation tools, or downstream analysis. Both full and selective exports are supported.
+  Export your dataset metadata, labels, and media files for use in training pipelines, annotation tools, or downstream analysis. Both full and selective exports are supported.
 </Card>
 
 ## Prerequisites