review what is aio

Author: asergaz

articles/iot-operations/develop-edge-apps/overview-iot-operations-sdks.md

@@ -4,7 +4,7 @@ description: Learn about Azure IoT Operations SDKs and how to use it to develop
 author: asergaz
 ms.author: sergaz
 ms.topic: concept-article
-ms.date: 05/07/2025
+ms.date: 05/27/2025
 
 #CustomerIntent: As a developer, I want to know why use Azure IoT Operations SDKs to develop highly available edge applications.
 ---
@@ -21,7 +21,7 @@ The Azure IoT Operations SDKs are a suite of tools and libraries across multiple
 | **Zero data loss** | Builds on MQTT broker to remove data loss due to application failure. |
 | **Low latency** | Optimized layering and tight MQTT client coupling minimized overheads. |
 | **Integration with Azure IoT Operations services** | Libraries provide access to services such as state store. |
-| **Simplify complex messaging** | Provide support for communication between applications via MQTT5 using a remote procedure call (RPC) implementation. |
+| **Simplify complex messaging** | Provide support for communication between applications via MQTT v5 using a remote procedure call (RPC) implementation. |
 | **Support** | The SDKs are maintained and supported by a dedicated team at Microsoft. |
 
 The SDKs are open source and available on GitHub:
@@ -34,23 +34,23 @@ The SDKs are open source and available on GitHub:
 > Azure IoT Operations SDKs is currently in PREVIEW.
 > The assets in the [Azure IoT Operations SDKs GitHub repository](https://github.com/Azure/iot-operations-sdks) have been made available for early access and feedback purposes.
 
-## Goals of the SDKs
+## Goal of the SDKs
 
-The goal of the SDKs is to provide an application framework to abstract the MQTT concepts, with a clean API, that can also be consumed using the Protocol Compiler (Codegen) from [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/README.md) models.
+The goal of the SDKs is to provide an application framework to abstract the MQTT concepts, with a clean API that let you use the *Protocol Compiler (codegen)*, to generate code from [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/README.md) models in the supported programming languages.
 
 The SDKs can be used to build highly available applications at the edge, that interact with Azure IoT Operations to perform operations such as **asset discovery**, **protocol translation** and **data transformation**.
 
 ## Benefits of using the SDKs
 
-The SDKs provide a number of benefits compared to utilizing the MQTT client directly:
+The SDKs provide a number of benefits compared to using the MQTT client directly:
 
 | Feature | Benefit |
 |-|-|
 | **Connectivity** | Maintain a secure connection to the MQTT Broker, including rotating server certificates and authentication keys. |
 | **Security** | Support SAT or X.509 certificate authentication with credential rotation. |
 | **Configuration** | Configure the MQTT Broker connection through the file system, environment or connection string. |
 | **Services** | Provides client libraries to Azure IoT Operations services for simplified development. |
-| **Codegen** | Provides contract guarantees between client and servers via RPC and telemetry. |
+| **Protocol Compiler (codegen)** | Provides contract guarantees between client and servers via RPC and telemetry. |
 | **High availability** | Building blocks for building highly available apps via state store, lease lock and leader election clients. |
 | **Payload formats** | Supports multiple serialization formats, built in. |
 
@@ -64,7 +64,7 @@ The SDKs provide a number of components available for simplicity and ease of use
 
 * A set of clients providing integration with Azure IoT Operations services such as **state store**, **leader election**, **lease lock**, and **schema registry**.
 
-* The **Protocol Compiler (Codegen)** allows clients and servers to communicate via a schema contract. First describe the communication (using **Telemetry** and **Commands**) with DTDL, then generate a set of client libraries and server library stubs across the supported programming languages.
+* The **Protocol Compiler (codegen)** allows clients and servers to communicate via a schema contract. First describe the communication (using **Telemetry** and **Commands**) with DTDL, then generate a set of client libraries and server library stubs across the supported programming languages.
 
 Read further about the underlying terminology and different components of the SDKs:
 
@@ -79,22 +79,20 @@ The SDKs supports the following application types:
 
 | Application type | Description |
 |-|-|
-| [Edge application](https://github.com/Azure/iot-operations-sdks/blob/main/doc/edge_application/README.md) | A generic edge application that needs to interface with various Azure IoT Operations services such as the MQTT broker and state store. The SDKs provides convenient clients to simplify the development experience. </br>*An Edge Application is a customer managed artifact, including deployment to the cluster and monitoring execution.* |
-| [Akri connector](https://github.com/Azure/iot-operations-sdks/blob/main/doc/akri_connector/README.md)</br>*(in development)*| A specialized edge application deployed by the Akri Operator and designed to interface with on-premises asset endpoints. The Akri connector is responsible for discovering assets available via the endpoint, and relaying information to and from those assets.</br>*The Akri Connector's deployment is managed automatically by the Akri Operator.* |
+| [Edge application](https://github.com/Azure/iot-operations-sdks/blob/main/doc/edge_application/README.md) | A generic edge application that needs to interface with various Azure IoT Operations services such as the MQTT broker and state store. The SDKs provides convenient clients to simplify the development experience. </br></br>*An Edge Application is a customer managed artifact, including deployment to the cluster and monitoring execution.* |
+| [Akri connector](https://github.com/Azure/iot-operations-sdks/blob/main/doc/akri_connector/README.md)</br>*(in development)*| A specialized edge application deployed by the Akri Operator and designed to interface with on-premises asset endpoints. The Akri connector is responsible for discovering assets available via the endpoint, and relaying information to and from those assets.</br></br>*The Akri connector's deployment is managed automatically by the Akri Operator.* |
 
 > [!NOTE]
 > The Akri connector is part of the Akri services (preview), which is under active development and will be available in the near future.
 
-## Samples and tutorials
+## Samples
 
 Review the [samples](https://github.com/Azure/iot-operations-sdks/tree/main/samples) directory for samples about creating applications for Azure IoT Operation on the supported languages.
 
-To deploy a fully functional application to a cluster and see the SDKs in action, follow the [Tutorial: Develop an edge app with Azure IoT Operations SDKs for efficient data handling](tutorial-develop-edge-app.md).
-
 ## SDKs reference documentation
 
-For documentation related to the implementation of the SDKs, it's fundamentals primitives and protocols as well as the underlying topic and payload structure used for communication over MQTT, see [SDKs reference documentation](https://github.com/Azure/iot-operations-sdks/blob/main/doc/reference/README.md).
+For documentation related to the implementation of the SDKs, it's fundamentals primitives and protocols as well as the underlying topic and payload structure used for communication over MQTT, see [Azure IoT Operatios SDKs reference documentation](https://github.com/Azure/iot-operations-sdks/blob/main/doc/reference/README.md).
 
 ## Next step
 
-Try the [Quickstart: Start developing with the Azure IoT Operations SDKs](develop-edge-apps/quickstart-get-started-sdks.md).
+To deploy a fully functional application to a cluster and see the SDKs in action, follow the [Tutorial: Develop an edge app with Azure IoT Operations SDKs for efficient data handling](tutorial-develop-edge-app.md).

articles/iot-operations/develop-edge-apps/reference-state-store-protocol.md

@@ -13,7 +13,7 @@ ms.date: 05/07/2025
 
 # State store protocol
 
-The state store is a distributed storage system within the Azure IoT Operations cluster. The state store offers the same high availability guarantees as MQTT messages in MQTT broker. According to the MQTT5/RPC protocol guidelines, clients should use MQTT5 to interact with the state store. This article provides protocol guidance for developers who need to implement their own state store clients. 
+The state store is a distributed storage system within the Azure IoT Operations cluster. The state store offers the same high availability guarantees as MQTT messages in MQTT broker. According to the MQTT5/RPC protocol guidelines, clients should use MQTT v5 to interact with the state store. This article provides protocol guidance for developers who need to implement their own state store clients. 
 
 ## Overview
 
@@ -40,12 +40,12 @@ sequenceDiagram
 
 :::image type="content" source="media/concept-about-state-store-protocol/state-store-request-response-basic.svg" alt-text="Diagram of state store basic request and response process." border="false":::
 
-## State store system topic, QoS, and required MQTT5 properties
+## State store system topic, QoS, and required MQTT v5 properties
 
 To communicate with the state store, clients must meet the following requirements:
 
-- Use MQTT5. For more information, see the [MQTT 5 specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html).
-- Use QoS 1 (Quality of Service level 1). QoS 1 is described in the [MQTT 5 specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901236).
+- Use MQTT v5. For more information, see the [MQTT v5 specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html).
+- Use QoS 1 (Quality of Service level 1). QoS 1 is described in the [MQTT v5 specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901236).
 - Have a clock that is within one minute of the MQTT broker's clock.
 
 To communicate with the state store, clients must `PUBLISH` requests to the system topic `statestore/v1/FA9AE35F-2F64-47CD-9BFF-08E2B32A0FE8/command/invoke`. Because the state store is part of Azure IoT Operations, it does an implicit `SUBSCRIBE` to this topic on startup.
@@ -362,7 +362,7 @@ Clients can register with the state store to receive notifications of keys being
 
 ### KEYNOTIFY request messages
 
-State store clients request the state store monitor a given `keyName` for changes by sending a `KEYNOTIFY` message. Just like all state store requests, clients PUBLISH a QoS1 message with this message via MQTT5 to the state store system topic `statestore/v1/FA9AE35F-2F64-47CD-9BFF-08E2B32A0FE8/command/invoke`.
+State store clients request the state store monitor a given `keyName` for changes by sending a `KEYNOTIFY` message. Just like all state store requests, clients PUBLISH a QoS1 message with this message via MQTT v5 to the state store system topic `statestore/v1/FA9AE35F-2F64-47CD-9BFF-08E2B32A0FE8/command/invoke`.
 
 The request payload has the following form: