reviewer requests

Author: asergaz

articles/iot/index.yml

@@ -58,12 +58,12 @@ productDirectory:
       url: ../iot-operations/index.yml
     # Card
     - title: Azure IoT Hub
-      summary: Use Azure IoT Hub to build a cloud-based IoT solution. IoT Hub does not follow the adaptive cloud approach
+      summary: Use Azure IoT Hub to build a cloud-based IoT solution. IoT Hub doesn't follow the adaptive cloud approach
       imageSrc: ../media/index/iot-hub.svg
       url: ../iot-hub/index.yml
     # Card
     - title: Azure IoT Central
-      summary: Use Azure IoT Central to build a cloud-based IoT solution. IoT Central does not follow the adaptive cloud approach
+      summary: Use Azure IoT Central to build a cloud-based IoT solution. IoT Central doesn't follow the adaptive cloud approach
       imageSrc: ../media/index/iot-central.svg
       url: ../iot-central/index.yml
     # Card
@@ -78,12 +78,12 @@ productDirectory:
       url: ../iot-edge/index.yml
     # Card
     - title: Azure Event Grid
-      summary: Currently, Azure Event Grid is typically part of a hybrid IoT solution that use Azure IoT Operations, IoT Hub, or IoT Central
+      summary: Currently, Azure Event Grid is typically part of a hybrid IoT solution that uses Azure IoT Operations, IoT Hub, or IoT Central
       imageSrc: ../media/index/event-grid-domains.svg
       url: ../event-grid/index.yml
     # Card
     - title: Microsoft Defender for IoT
-      summary: Microsoft Defender for IoT is a unified security solution that helps you secure cloud-based, edge-based and hybrid IoT solutions
+      summary: Microsoft Defender for IoT is a unified security solution that helps you secure cloud-based, edge-based, and hybrid IoT solutions
       imageSrc: ../media/index/defender-iot.svg
       url: ../defender-for-iot/index.yml
     # Card

articles/iot/iot-overview-device-development.md

@@ -52,7 +52,7 @@ In Azure IoT, a device developer writes the code to run on the devices in the so
 
 ## Asset and device types
 
-An IoT solution can contain many types of [assets](iot-glossary.md#asset) and [devices](iot-glossary.md#device). You typically find devices in cloud-based solutions and assets in edge-based solutions. It's also possible to have a hybrid solution that contain both devices and assets.
+An IoT solution can contain many types of [assets](iot-glossary.md#asset) and [devices](iot-glossary.md#device). You typically find devices in cloud-based solutions and assets in edge-based solutions. It's also possible to have a hybrid solution that contains both devices and assets.
 
 # [Edge-based solution](#tab/edge)
 
@@ -82,7 +82,7 @@ These devices are typically built using microcontrollers (MCUs) or microprocesso
 
 - MCUs are less expensive and simpler to operate than MPUs.
 - An MCU contains many of the functions, such as memory, interfaces, and I/O on the chip itself. An MPU accesses this functionality from components in supporting chips.
-- An MCU often uses a real-time OS (RTOS) or runs bare-metal (no OS) and provides real-time responses and highly deterministic reactions to external events. MPUs generally run a general purpose OS, such as Windows, Linux, or macOS that provides a nondeterministic real-time response. There's typically no guarantee as to when a task will complete.
+- An MCU often uses a real-time OS (RTOS) or runs bare-metal (no OS) and provides real-time responses and highly deterministic reactions to external events. MPUs generally run a general purpose OS, such as Windows, Linux, or macOS that provides a nondeterministic real-time response. There's typically no guarantee as to when a task completes.
 
 Examples of specialized hardware and operating systems include:
 
@@ -150,11 +150,11 @@ Device and asset models define the data that devices and assets exchange with th
 
 # [Edge-based solution](#tab/edge)
 
-In an edge-based solution, an operator configures connectors to connect to assets. This configuration includes a mapping between the asset's data and a cloud schema. For example, the OPC UA connector lets the operator map OPC UA node Ids to tags and events in a JSON message exchanged with the MQTT broker. The following screenshot shows an example in the digital operations experience web UI that defines two such mappings for an asset:
+In an edge-based solution, an operator configures connectors to connect to assets. This configuration includes a mapping between the asset's data and a cloud schema. For example, the OPC UA connector lets the operator map OPC UA node IDs to tags and events in a JSON message exchanged with the MQTT broker. The following screenshot shows an example in the digital operations experience web UI that defines two such mappings for an asset:
 
 :::image type="content" source="media/iot-overview-device-development/add-tag.png" alt-text="Screenshot that shows an example asset definition.":::
 
-Elsewhere in the solution, an operator can refer directly to the **Temperature** and **Tag 10** tags without needing to know the details of the OPC UA node Ids.
+Elsewhere in the solution, an operator can refer directly to the **Temperature** and **Tag 10** tags without needing to know the details of the OPC UA node IDs.
 
 # [Cloud-based solution](#tab/cloud)
 

articles/iot/iot-overview-security.md

@@ -190,7 +190,7 @@ Microsoft Defender for IoT can automatically monitor some of the recommendations
 
 ---
 
-## Related Content
+## Related content
 
 - [Azure security baseline for Azure Arc enabled Kubernetes](/security/benchmark/azure/baselines/azure-arc-enabled-kubernetes-security-baseline?toc=/azure/azure-arc/kubernetes/toc.json)
 - [Concepts for keeping your cloud-native workload secure](https://kubernetes.io/docs/concepts/security/)

articles/iot/iot-services-and-technologies.md

@@ -59,7 +59,7 @@ To learn more, see [What is Azure IoT Operations?](../iot-operations/overview-io
 
 ### Azure Device Registry
 
-> Currently, Azure Device Registry is typically part of an **edge-based IoT solution** that use Azure IoT Operations and follows the adaptive cloud approach.
+> Currently, Azure Device Registry is typically part of an **edge-based IoT solution** that uses Azure IoT Operations and follows the adaptive cloud approach.
 
 Azure Device Registry is a backend service that enables the management of assets and devices in your solution using Azure Resource Manager. Azure Device Registry:
 
@@ -72,7 +72,7 @@ To learn more, see [What is asset management in Azure IoT Operations](../iot-ope
 
 ### Azure IoT Operations SDKs (preview)
 
-> The Azure IoT Operations SDKs enable you to build a custom **edge-based IoT solution** that use Azure IoT Operations.
+> The Azure IoT Operations SDKs enable you to build a custom **edge-based IoT solution** that uses Azure IoT Operations.
 
 The Azure IoT Operations SDKs are a suite of tools and libraries across multiple languages designed to aid the development of applications for Azure IoT Operations. The SDKs can be used to build secure, highly available applications at the edge, that interact with Azure IoT Operations to perform operations such as asset discovery, protocol translation and data transformation.
 
@@ -88,31 +88,31 @@ To learn more, see [What is Azure IoT Hub?](../iot-hub/iot-concepts-and-iot-hub.
 
 ### Azure IoT Hub Device Provisioning Service (DPS)
 
-> DPS is typically part of a **cloud-based IoT solution** that use IoT Hub or IoT Central.
+> DPS is typically part of a **cloud-based IoT solution** that uses IoT Hub or IoT Central.
 
 DPS is a helper service for IoT Hub that enables zero-touch, just-in-time provisioning of IoT devices to an IoT hub without requiring human intervention. Many of the manual steps traditionally involved in provisioning are automated with DPS to reduce the time to deploy IoT devices and lower the risk of manual error. DPS can provision devices that use X.509 certificates and trusted platform modules. IoT Central applications use an internal DPS instance to manage device connections.
 
 To learn more, see [What is Azure IoT Hub Device Provisioning Service?](../iot-dps/about-iot-dps.md).
 
 ### Azure Device Update for IoT Hub
 
-> Device Update for IoT Hub is typically part of a **cloud-based IoT solution** that use IoT Hub.
+> Device Update for IoT Hub is typically part of a **cloud-based IoT solution** that uses IoT Hub.
 
 Azure Device Update for IoT Hub is a service that enables you to deploy over-the-air updates for your IoT devices, including Azure IoT Edge devices. Device Update offers optimized update deployment and streamlined operations through integration with Azure IoT Hub, making it easy to adopt on any existing IoT Hub-based solution.
 
 To learn more, see [What is Device Update for IoT Hub?](../iot-hub-device-update/understand-device-update.md).
 
 ### Azure IoT Edge
 
-> IoT Edge is typically part of a **hybrid IoT solution** that use IoT Hub or IoT Central.
+> IoT Edge is typically part of a **hybrid IoT solution** that uses IoT Hub or IoT Central.
 
 Azure IoT Edge is a device-focused runtime that enables you to deploy, run, and monitor containerized Linux workloads at the edge, bringing analytics closer to your devices for faster insights and offline decision-making. IoT Edge can also act as a gateway for devices with no internet connectivity and protocol translation. IoT Edge is a feature of Azure IoT Hub and also integrates with Azure IoT Central.
 
 To learn more, see [What is Azure IoT Edge](../iot-edge/about-iot-edge.md).
 
 ## Azure Digital Twins
 
-> The Azure Digital Twins service is typically part of a **cloud-based IoT solution** that use IoT Hub.
+> The Azure Digital Twins service is typically part of a **cloud-based IoT solution** that uses IoT Hub.
 
 Azure Digital Twins is a platform as a service (PaaS) offering that enables the creation of twin graphs based on digital models of entire environments, which could be buildings, factories, farms, energy networks, railways, stadiums, and more—even entire cities. Azure Digital Twins can be used to design a digital twin architecture that represents actual IoT devices in a wider cloud solution, and which connects to IoT Hub device twins to send and receive live data.
 
@@ -128,7 +128,7 @@ To learn more, see [What is Azure IoT Central?](../iot-central/core/overview-iot
 
 ## Azure Event Grid
 
-> Currently, Azure Event Grid is typically part of a **hybrid IoT solution** that use Azure IoT Operations, IoT Hub, or IoT Central.
+> Currently, Azure Event Grid is typically part of a **hybrid IoT solution** that uses Azure IoT Operations, IoT Hub, or IoT Central.
 
 Azure Event Grid is a highly scalable, fully managed Pub Sub message distribution service that offers flexible message consumption patterns using the MQTT and HTTP protocols. With Azure Event Grid, you can build data pipelines with device data, integrate applications, and build event-driven serverless architectures. Event Grid enables clients to publish and subscribe to messages over the MQTT v3.1.1 and v5.0 protocols to support IoT solutions. Through HTTP, Event Grid enables you to build event-driven solutions where a publisher service announces its system state changes (events) to subscriber applications.
 
@@ -140,7 +140,7 @@ To learn more, see [What is Azure Event Grid?](../event-grid/overview.md)
 
 ## Azure IoT device and service SDKs
 
-> The Azure IoT device and service SDKs enables you to build a custom **cloud-based IoT solution** that use IoT Hub or IoT Central.
+> The Azure IoT device and service SDKs enables you to build a custom **cloud-based IoT solution** that uses IoT Hub or IoT Central.
 
 - The [Azure IoT device SDKs](iot-sdks.md#device-sdks) help you address the challenges of connecting devices securely and reliably to your IoT Hub or IoT Central using protocols such as MQTT and AMQP.
 - The [Azure IoT service SDKs](iot-sdks.md#iot-hub-service-sdks) contain code to facilitate building applications that interact directly with IoT Hub to manage devices and security.
@@ -153,7 +153,7 @@ To learn more, see [Azure IoT device and service SDKs](iot-sdks.md).
 
 ## Azure IoT Plug and Play
 
-> Azure IoT Plug and Play is a programming model that enables you to build a **cloud-based IoT solution** that use IoT Hub or IoT Central.
+> Azure IoT Plug and Play is a programming model that enables you to build a **cloud-based IoT solution** that uses IoT Hub or IoT Central.
 
 IoT Plug and Play enables solution builders to integrate IoT devices with their solutions without any manual configuration. At the core of IoT Plug and Play, is a device _model_ that a device uses to advertise its capabilities to an IoT Plug and Play-enabled service such as IoT Central or Azure Digital Twins. You define IoT Plug and Play models and interfaces using the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/README.md).