M3 tutorial updates

Author: dominicbetts

articles/iot-operations/end-to-end-tutorials/media/tutorial-add-assets/site-list.png

@@ -63,7 +63,7 @@ Browse to the [operations experience](https://iotoperations.azure.com) in your b
 
 ## Select your site
 
-A _site_ is a collection of Azure IoT Operations instances. Sites typically group instances by physical location and make it easier for OT users to locate and manage assets. Your IT administrator creates [sites and assigns Azure IoT Operations instances to them](/azure/azure-arc/site-manager/overview). Because you're working with a new deployment, there are no sites yet. You can find the cluster you created in the previous tutorial by selecting **Unassigned instances**. In the operations experience, an instance represents a cluster where you deployed Azure IoT Operations.
+A _site_ is a collection of Azure IoT Operations instances. Sites typically group instances by physical location and make it easier for OT users to locate and manage assets. Your IT administrator creates [sites and assigns Azure IoT Operations instances to them](/azure/azure-arc/site-manager/overview). Because you're working with a new deployment, there are no sites yet. You can find the cluster you created in the previously by selecting **View unassigned instances**. In the operations experience, an instance represents a cluster where you deployed Azure IoT Operations.
 
 :::image type="content" source="media/tutorial-add-assets/site-list.png" alt-text="Screenshot that shows the unassigned instances node in the operations experience.":::
 

articles/iot-operations/end-to-end-tutorials/media/tutorial-upload-telemetry-to-cloud/event-hubs-data-viewer.png

@@ -95,7 +95,7 @@ In this section, you create a KQL database in your Microsoft Fabric workspace to
 1. Run the following KQL query to create a data mapping for your table. The data mapping will be called *opcua_mapping*.
 
     ```kql
-    .create table ['OPCUA'] ingestion json mapping 'opcua_mapping' '[{"column":"AssetId", "Properties":{"Path":"$[\'AssetId\']"}},{"column":"Temperature", "Properties":{"Path":"$.Temperature.Value"}},{"column":"Humidity", "Properties":{"Path":"$.Humidity.Value"}},{"column":"Timestamp", "Properties":{"Path":"$[\'EventProcessedUtcTime\']"}}]'
+    .create table ['OPCUA'] ingestion json mapping 'opcua_mapping' '[{"column":"AssetId", "Properties":{"Path":"$[\'AssetId\']"}},{"column":"Temperature", "Properties":{"Path":"$[\'ThermostatTemperature\']"}},{"column":"Humidity", "Properties":{"Path":"$[\'ThermostatHumidity\']"}},{"column":"Timestamp", "Properties":{"Path":"$[\'EventProcessedUtcTime\']"}}]'
     ```
 
 ### Add data table as a destination

articles/iot-operations/end-to-end-tutorials/media/tutorial-upload-telemetry-to-cloud/rename-transform.png

@@ -125,20 +125,20 @@ To create the dataflow:
 
 1. In the dataflow editor, select **Select source**. Then select the thermostat asset you created previously and select **Apply**.
 
-1. In the dataflow editor, select **Select dataflow endpoint**. Then select the **event-hubs-target**** endpoint you created previously and select **Apply**.
+1. In the dataflow editor, select **Select dataflow endpoint**. Then select the **event-hubs-target** endpoint you created previously and select **Apply**.
 
 1. On the next page, enter *destinationeh* as the topic. The topic refers to the hub you created in the Event Hubs namespace. Select **Apply**. Your dataflow now has the thermostat asset as its source and a hub in your Event Hubs namespace as its destination.
 
 1. To add a transformation, select **Add transform (optional)**.
 
 1. To rename the `Tag 10` and `temperature` fields in the incoming message, select **+ Add** in the **Rename** tile.
 
-1. Add the following two transforms:
+1. Add the following two rename transforms:
 
     | Datapoint | New datapoint name |
     |-----------|--------------------|
-    | "Tag 10"    | Humidity          |
-    | temperature | Temperature       |
+    | Tag 10.Value    | ThermostatHumidity          |
+    | temperature.Value | ThermostatTemperature       |
 
     The rename transformation looks like the following screenshot: