Fix blocking and non-blocking issues

Author: dominicbetts

articles/iot-operations/develop-edge-apps/howto-build-akri-connectors-vscode.md

@@ -65,7 +65,7 @@ To deploy and use your connector with an Azure IoT Operations instance, you also
 
 - An instance of [Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md).
 - Access to a container registry, such as Azure Container Registry, to publish your connector images.
-- An container registry endpoint configured in your Azure IoT Operations instance to pull your connector images. For more information, see [Configure registry endpoints](howto-configure-registry-endpoint.md).
+- A container registry endpoint configured in your Azure IoT Operations instance to pull your connector images. For more information, see [Configure registry endpoints](howto-configure-registry-endpoint.md).
 
 ## Author and validate an Akri connector
 

articles/iot-operations/develop-edge-apps/howto-build-wasm-modules-vscode.md

@@ -307,7 +307,7 @@ This example shows how to use the state store with WASM operators. The state sto
 
 ### Open the state store sample workspace
 
-Clone the [Explore IoT Operations](https://github.com/Azure-Samples/azure-iot-operations) repository if you haven't already.
+Clone the [Explore IoT Operations](https://github.com/Azure-Samples/explore-iot-operations) repository if you haven't already.
 
 Open the `samples/wasm/statestore-scenario` folder in Visual Studio Code by selecting **File > Open Folder** and navigating to the `samples/wasm/statestore-scenario` folder. This folder contains the following resources:
 
@@ -416,7 +416,7 @@ The following limitations apply to the local schema file (`tk_schema_config.json
 
 Currently, the following limitations apply in the local development runtime:
 - Only one schema config file is loaded. No multi-file include or directory scanning is supported.
-- `$ref` to external files or URLs isn't supported locally. Keep the schema self‑contained. You can use internal JSON pointer refs like `{"$ref":"#/components/..."}`.
+- `$ref` to external files or URLs isn't supported locally. Keep the schema self‑contained. You can use internal JSON pointer references like `{"$ref":"#/components/..."}`.
 - Commonly used draft-07 keywords like `type`, `properties`, `required`, `enum`, `minimum`, `maximum`, `allOf`, `anyOf`, `oneOf`, `not`, and `items` all work. The underlying validator might ignore less common or advanced features like `contentEncoding` and `contentMediaType`.
 - Keep the size of your schemas to less than ~1 MB for fast cold starts.
 - Versioning and schema evolution policies aren't enforced locally. You're responsible for staying aligned with the cloud registry.

articles/iot-operations/develop-edge-apps/howto-deploy-wasm-graph-definitions.md

@@ -14,9 +14,6 @@ ai-usage: ai-assisted
 
 Azure IoT Operations data flow graphs support WebAssembly (WASM) modules for custom data processing at the edge. You can deploy custom business logic and data transformations as part of your data flow pipelines.
 
-> [!TIP]
-> Want to run AI in-band? See [Run ONNX inference in WebAssembly data flow graphs](../develop-edge-apps/howto-wasm-onnx-inference.md) to package and execute small ONNX models inside your WASM operators.
-
 > [!IMPORTANT]
 > Data flow graphs currently only support MQTT, Kafka, and OpenTelemetry endpoints. Other endpoint types like Data Lake, Microsoft Fabric OneLake, Azure Data Explorer, and Local Storage are not supported. For more information, see [Known issues](../troubleshoot/known-issues.md#data-flow-graphs-only-support-specific-endpoint-types).
 

articles/iot-operations/toc.yml

@@ -249,6 +249,9 @@ items:
               - name: Configure registry endpoints
                 href: develop-edge-apps/howto-configure-registry-endpoint.md
                 displayName: data flow, endpoint, northbound, registry, connectors
+              - name: Deploy graph definitions
+                href: develop-edge-apps/howto-deploy-wasm-graph-definitions.md
+                displayName: data flow, WASM, WebAssembly, graph definitions, deploy, container, registry
               - name: AI inference with ONNX
                 href: connect-to-cloud/howto-wasm-onnx-inference.md
                 displayName: data flow, WASM, WebAssembly, ONNX, inference, AI, wasi-nn