Skip to content

Commit c14a6ed

Browse files
committed
Fixes to WASM article
1 parent 7570c39 commit c14a6ed

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/iot-operations/connect-to-cloud/howto-dataflow-graph-wasm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -963,7 +963,7 @@ For storage destinations like Azure Data Lake or Fabric OneLake, you can specify
963963

964964
### Node connections
965965

966-
Node connections define the data flow path between nodes. Each connection specifies a source node and destination node, creating the processing pipeline. Connections can optionally include schema to have the schema be provided to the module at initialization, allowing for schema validation like in [this example](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/schema-registry-scenario/operators/filter/src/lib.rs).
966+
Node connections define the data flow path between nodes. Each connection specifies a source node and destination node, creating the processing pipeline. Connections can optionally include a schema, which is provided to the module at initialization, allowing for schema validation [as in this example](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/schema-registry-scenario/operators/filter/src/lib.rs).
967967

968968
# [Operations experience](#tab/portal)
969969

0 commit comments

Comments
 (0)