incorporating feedback

Author: ShawnJackson

articles/iot-operations/discover-manage-assets/concept-assets-devices.md

@@ -21,6 +21,25 @@ The following diagram shows the relationships between assets, devices, and conne
 
 :::image type="content" source="media/concept-assets-devices/assets-devices.svg" alt-text="Diagram that shows the relationships between asset and device configuration resources." border="false":::
 
+<!--
+```mermaid
+graph LR
+    CT["`Connector templates
+       such as OPC UA, ONVIF, Media.`"]
+
+    subgraph Device
+        IE1["`Inbound endpoint(s)<br/>- *Address*<br/>- *Connector type*<br/>- *Authentication data*`"]
+    end
+
+
+    A["`Asset<br/>- *Name*<br/>- *Data points/Streams/<br/>Events*`"]
+
+
+    CT -- Used by connector type --&gt; IE1
+    A -- "`References an inbound endpoint`" --&gt; IE1>
+```
+--->
+
 ## Devices
 
 Before you create an asset, define a device. A device is a configuration resource that describes [southbound](overview-manage-assets.md#southbound-and-northbound-connectivity) edge connectivity information for one or more assets.

articles/iot-operations/discover-manage-assets/overview-manage-assets.md

@@ -25,6 +25,8 @@ In the context of Azure IoT Operations, the terms *asset* and *device* can refer
 
 This diagram shows the key components of asset management in Azure IoT Operations.
 
+<!-- Art Library Source# ConceptArt-0-000-92 -->
+
 :::image type="content" source="media/overview-manage-assets/azure-iot-operations-architecture.svg" alt-text="Diagram that shows services for managing assets." lightbox="media/overview-manage-assets/azure-iot-operations-architecture.png" border="false":::
 
 In the preceding diagram:
@@ -39,6 +41,30 @@ This diagram shows how physical devices connect to Azure IoT Operations.
 
 :::image type="content" source="media/overview-manage-assets/physical-assets-devices.svg" alt-text="Diagram that shows how physical assets and devices connect." border="false":::
 
+<!--
+```mermaid
+graph LR
+    subgraph Physical devices and assets
+        D2[Device connects directly to<br>the edge-based MQTT broker]
+        D3[Physical device such as an<br>ONVIF compliant camera]
+        D4[OPC UA server]
+        D5[Physical asset<br>such as an oven]
+    end
+
+    subgraph IoT Operations edge cluster
+        B2[MQTT broker]
+        B3[Connectors such as<br>OPC UA or ONVIF]
+    end
+
+    D2 -- Publish --&gt; B2
+
+    B3 -- Publish --&gt; B2
+    D3 -- Communicates using ONVIF protocol --&gt; B3
+    D4 -- Communicates using OPC UA protocol --&gt; B3
+    D5 --&gt; D4
+```
+-->
+
 ## Configuration resources
 
 [!INCLUDE [assets-devices-logical-entities](../includes/assets-devices-logical-entities.md)]

articles/iot-operations/overview-iot-operations.md

@@ -55,6 +55,8 @@ With Azure IoT Operations, you can use data collected from assets and equipment
 
 ## Architecture overview
 
+<!-- Art Library Source# ConceptArt-0-000-92 -->
+
 :::image type="content" source="media/overview-iot-operations/azure-iot-operations-architecture.svg" alt-text="Diagram of the high-level architecture of Azure IoT Operations, showing its core components and data flow." lightbox="media/overview-iot-operations/azure-iot-operations-architecture.png" border="false":::
 
 The Azure IoT Operations architecture has these core elements: