edit pass: azure-iot-operations-articles

Author: ShawnJackson

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

@@ -23,7 +23,7 @@ The following diagram shows the relationships between assets, devices, and conne
 
 ## 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.
+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.
 
 ### Inbound endpoints
 
@@ -48,7 +48,7 @@ An IT user adds connector templates in the Azure portal. After the IT user adds
 
 ## Assets
 
-An *asset* is a configuration resource that represents a physical device or asset as:
+An asset is a configuration resource that represents a physical device or asset as:
 
 - An Azure Resource Manager resource in the cloud.
 - A Kubernetes custom resource at the edge.

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

@@ -109,7 +109,7 @@ Akri services simplify the creation of assets by automatically onboarding assets
 
 #### Monitoring
 
-Akri services provide monitoring capabilities for physical devices and assets. These capabilities include tracking the status and health of devices. The monitoring framework works seamlessly with the connectors and Device Registry, so you can gain insights into your edge environment.
+Akri services provide monitoring capabilities for physical devices and assets. These capabilities include tracking the status and health of devices. The monitoring framework works seamlessly with the connectors and Device Registry to help you gain insights into your edge environment.
 
 ### Operations experience
 

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

@@ -60,7 +60,7 @@ With Azure IoT Operations, you can use data collected from assets and equipment
 The Azure IoT Operations architecture has these core elements:
 
 * Data services that run on Azure Arc-enabled edge Kubernetes clusters:
-  * *MQTT broker* to power event-driven architectures as an edge-native MQTT broker.
+  * An edge-native *MQTT broker* to power event-driven architectures.
   * *Akri connectors*, like the connector for OPC UA, to simplify communication with servers and leaf devices.
   * *Data flows* to transform and contextualize data. You can route messages to various locations, including cloud endpoints.
 * The *operations experience*. OT users use this web UI to manage assets and data flows in an Azure IoT Operations deployment.