Merge pull request #309232 from jlian/main

Fix links

Author: prmerger-automator[bot]

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

@@ -75,7 +75,7 @@ moduleRequirements:
 
 ## Example 1: Simple graph definition
 
-The [simple graph definition](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/rust/graph-simple.yaml) demonstrates a basic three-stage pipeline that converts temperature data from Fahrenheit to Celsius:
+The [simple graph definition](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/graph-simple.yaml) demonstrates a basic three-stage pipeline that converts temperature data from Fahrenheit to Celsius:
 
 :::code language="yaml" source="~/azure-iot-operations-samples/samples/wasm/graph-simple.yaml":::
 
@@ -89,7 +89,7 @@ This graph creates a straightforward data processing pipeline:
 2. **Map operation**: Processes data with the temperature WASM module (`temperature:1.0.0`)
 3. **Sink operation**: Sends converted data to the data flow's destination endpoint
 
-The [temperature module](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/rust/examples/temperature/src/lib.rs) converts Fahrenheit to Celsius using the standard formula `(F - 32) × 5/9 = C`.
+The [temperature module](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/operators/temperature/src/lib.rs) converts Fahrenheit to Celsius using the standard formula `(F - 32) × 5/9 = C`.
 
 **Input format:**
 ```json
@@ -103,7 +103,7 @@ The [temperature module](https://github.com/Azure-Samples/explore-iot-operations
 
 ## Example 2: Complex graph definition
 
-The [complex graph definition](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/rust/graph-complex.yaml) demonstrates a sophisticated multi-sensor processing workflow that handles temperature, humidity, and image data with advanced analytics:
+The [complex graph definition](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/graph-complex.yaml) demonstrates a sophisticated multi-sensor processing workflow that handles temperature, humidity, and image data with advanced analytics:
 
 :::code language="yaml" source="~/azure-iot-operations-samples/samples/wasm/graph-complex.yaml":::
 
@@ -170,7 +170,7 @@ As shown in the diagram, data flows from a single source through multiple proces
    - Aggregates multi-sensor results
    - Adds metadata and overtemperature alerts
 
-The graph uses specialized modules from the [Rust examples](https://github.com/Azure-Samples/explore-iot-operations/tree/wasm/samples/wasm/rust/examples):
+The graph uses specialized modules from the [Rust examples](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/operators):
 
 - Window module for time-based processing delays
 - Temperature modules for conversion, filtering, and statistical analysis
@@ -269,7 +269,7 @@ moduleConfigurations:
 
 These parameters are passed to your WASM operator's `init` function at runtime, enabling dynamic configuration without rebuilding modules. For detailed examples of how to access and use these parameters in your Rust and Python code, see [Module configuration parameters](howto-develop-wasm-modules.md#module-configuration-parameters).
 
-For a complete implementation example, see the [branch module](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/python/examples/branch), which demonstrates parameter usage for conditional routing logic.
+For a complete implementation example, see the [branch module](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python/operators/branch), which demonstrates parameter usage for conditional routing logic.
 
 ## Next steps
 

articles/iot-operations/connect-to-cloud/howto-develop-wasm-modules.md

@@ -159,7 +159,7 @@ source ~/.bashrc
 
 Python development uses componentize-py with WebAssembly Interface Types (WIT) for code generation. The WIT schemas define the interfaces between your Python code and the WASM runtime.
 
-**Get the WIT schemas**: The required schemas are available in the [Azure IoT Operations samples repository](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/python/schema). Clone or download these schemas to your development environment:
+**Get the WIT schemas**: The required schemas are available in the [Azure IoT Operations samples repository](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python/schema). Clone or download these schemas to your development environment:
 
 ```bash
 # Clone the repository to access WIT schemas
@@ -391,7 +391,7 @@ docker run --rm -v "$(pwd):/workspace" ghcr.io/azure-samples/explore-iot-operati
 
 # [Python](#tab/python)
 
-The Python Docker builder is maintained in the Azure IoT Operations samples repository and includes all necessary dependencies and schemas. For detailed documentation, see [Python Docker builder usage](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/python#using-the-streamlined-docker-builder).
+The Python Docker builder is maintained in the Azure IoT Operations samples repository and includes all necessary dependencies and schemas. For detailed documentation, see [Python Docker builder usage](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python#using-the-streamlined-docker-builder).
 
 ```bash
 # Build release version (optimized for production)
@@ -424,7 +424,7 @@ The examples demonstrate working implementations that show the complete structur
 
 # [Python](#tab/python)
 
-For comprehensive examples, see the [Python examples](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/python/examples) in the samples repository. Complete implementations include:
+For comprehensive examples, see the [Python examples](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python/operators) in the samples repository. Complete implementations include:
 
 - **Map operators**: Data transformation and conversion logic
 - **Filter operators**: Conditional data processing and validation
@@ -533,7 +533,7 @@ metrics::record_to_histogram("processing_duration", duration_ms, Some(labels))?;
 
 # [Python](#tab/python)
 
-Python WASM development doesn't use a traditional SDK. Instead, you use generated bindings from WebAssembly Interface Types (WIT). The WIT schemas are available from the [Azure IoT Operations samples repository](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/python/schema).
+Python WASM development doesn't use a traditional SDK. Instead, you use generated bindings from WebAssembly Interface Types (WIT). The WIT schemas are available from the [Azure IoT Operations samples repository](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python/schema).
 
 These bindings give you:
 
@@ -587,7 +587,7 @@ To embed and run small ONNX models inside your modules for in-band inference, se
 
 All operators implement standardized interfaces defined using [WebAssembly Interface Types (WIT)](https://github.com/WebAssembly/component-model/blob/main/design/mvp/WIT.md). WIT provides language-agnostic interface definitions that ensure compatibility between WASM modules and the host runtime.
 
-The complete WIT schemas for Azure IoT Operations are available in the [samples repository](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/python/schema). These schemas define all the interfaces, types, and data structures you'll work with when developing WASM modules.
+The complete WIT schemas for Azure IoT Operations are available in the [samples repository](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python/schema). These schemas define all the interfaces, types, and data structures you'll work with when developing WASM modules.
 
 ### Data model and interfaces
 

articles/iot-operations/connect-to-cloud/howto-wasm-onnx-inference.md

@@ -249,7 +249,7 @@ fn init_model() -> Result<(), anyhow::Error> {
 
 ### Performance optimization
 
-To avoid recreating the ONNX graph and execution context for every message, initialize it once and reuse it. The [public sample](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/rust/examples/snapshot/src/lib.rs) uses a static `LazyLock`:
+To avoid recreating the ONNX graph and execution context for every message, initialize it once and reuse it. The [public sample](https://github.com/Azure-Samples/explore-iot-operations/blob/main/samples/wasm/operators/snapshot/src/lib.rs) uses a static `LazyLock`:
 
 ```rust
 use std::sync::LazyLock;