again

Author: Jeadie

website/docs/components/data-connectors/mongodb.md

@@ -27,41 +27,6 @@ datasets:
 
 ## Configuration
 
-### Real-Time Change Data Capture (CDC) with MongoDB Change Streams
-
-Spice supports real-time Change Data Capture (CDC) from MongoDB using native [MongoDB Change Streams](https://www.mongodb.com/docs/manual/changeStreams/). This enables streaming inserts, updates, and deletes from your MongoDB collections directly into Spice accelerators, without requiring Debezium or Kafka.
-
-#### Enabling CDC with `refresh_mode: changes`
-
-To enable real-time CDC, set `refresh_mode: changes` in your dataset configuration:
-
-```yaml
-datasets:
-  - from: mongodb:my_collection
-    name: my_collection
-    params:
-      host: my-cluster.mongodb.net
-      db: mydb
-    acceleration:
-      enabled: true
-      engine: duckdb
-      refresh_mode: changes
-```
-
-- `refresh_mode: changes` tells Spice to use MongoDB Change Streams for this dataset.
-- No Debezium or Kafka is required—Spice connects directly to MongoDB.
-- Changes are streamed in real time into the configured accelerator (e.g., DuckDB, Arrow).
-
-#### Use Cases
-- Real-time analytics on operational data
-- Low-latency dashboards and event-driven pipelines
-
-#### Notes
-- Requires MongoDB 4.0+ and a replica set or sharded cluster.
-- Ensure your MongoDB user has `changeStream` privileges.
-
----
-
 ### `from`
 
 The `from` field takes the form `mongodb:{table_name}` where `table_name` is the table identifer in the MongoDB server to read from.
@@ -300,6 +265,32 @@ datasets:
       mongodb_pool_max: 10
 ```
 
+### Using MongoDB Change Streams
+
+Spice supports real-time Change Data Capture (CDC) from MongoDB using native [MongoDB Change Streams](https://www.mongodb.com/docs/manual/changeStreams/). This enables streaming inserts, updates, and deletes from your MongoDB collections directly into Spice accelerators.
+
+To enable real-time CDC, set `refresh_mode: changes` in the dataset's configuration:
+
+```yaml
+datasets:
+  - from: mongodb:my_collection
+    name: my_collection
+    params:
+      host: my-cluster.mongodb.net
+      db: mydb
+    acceleration:
+      enabled: true
+      engine: duckdb
+      refresh_mode: changes
+```
+
+#### Notes
+- Requires MongoDB 4.0+ and a replica set or sharded cluster.
+- Ensure your MongoDB user has `changeStream` privileges.
+
+---
+
+
 ## Secrets
 
 Spice integrates with multiple secret stores to help manage sensitive data securely. For detailed information on supported secret stores, refer to the [secret stores documentation](../secret-stores). Additionally, learn how to use referenced secrets in component parameters by visiting the [using referenced secrets guide](../secret-stores#using-secrets).

website/docs/features/observability/index.md

@@ -22,7 +22,6 @@ Spice provides monitoring and observability through three mechanisms:
 - [New Relic](../monitoring/new-relic)
 - [Zipkin](../monitoring/zipkin)
 
-
 ## Prometheus Metrics Endpoint
 
 Spice exposes a Prometheus-compatible metrics endpoint that monitoring systems can scrape. The endpoint serves metrics in the [Prometheus exposition format](https://prometheus.io/docs/instrumenting/exposition_formats/), which is supported by most enterprise monitoring platforms including Datadog, New Relic, Chronosphere, Grafana Cloud, and others.

website/docs/reference/sql/dml.md

@@ -9,6 +9,7 @@ Data Manipulation Language (DML) statements are used to insert, update, and dele
 
 :::warning[Supported Operations]
 Spice supports `INSERT` for write-capable connectors and `MERGE INTO` for [Spice Cayenne](../../components/data-accelerators/cayenne) catalog tables. `UPDATE` and `DELETE` statements are not yet supported as standalone operations. For data modifications, use `MERGE INTO` or the source database directly.
+:::
 
 :::info
 Spice is built on [Apache DataFusion](https://datafusion.apache.org/) and uses the PostgreSQL dialect, even when querying datasources with different SQL dialects.