acrolinx edits

Signed-off-by: Ryan Winter <[email protected]>

Author: ryanwinter

articles/iot-operations/create-edge-apps/howto-deploy-dapr.md

@@ -20,7 +20,7 @@ Azure IoT Operations supports two of these building blocks, powered by [MQTT bro
 - Publish and subscribe
 - State management
 
-To use the Dapr pluggable components, define the component spec for each of the APIs and then [register this to the cluster](https://docs.dapr.io/operations/components/pluggable-components-registration/). The Dapr components listen to a Unix domain socket placed on the shared volume. The Dapr runtime connects with each socket and discovers all services from a given building block API that the component implements.
+To use the Dapr pluggable components, define the component spec for each of the APIs and then [register with the cluster](https://docs.dapr.io/operations/components/pluggable-components-registration/). The Dapr components listen to a Unix domain socket placed on the shared volume. The Dapr runtime connects with each socket and discovers all services from a given building block API that the component implements.
 
 ## Install Dapr runtime
 
@@ -47,7 +47,7 @@ To create the yaml file, use the following component definitions:
 > | `metadata:name` | The component name is important and is how a Dapr application references the component. |
 > | `metadata:annotations:dapr.io/component-container` | Component annotations used by Dapr sidecar injector, defining the image location, volume mounts and logging configuration |
 > | `spec:type` | [The type of the component](https://docs.dapr.io/operations/components/pluggable-components-registration/#define-the-component), which needs to be declared exactly as shown |
-> | `spec:metadata:keyPrefix` | Defines the key prefix used when communicating to the statestore backend. See the [Dapr documentation](https://docs.dapr.io/developing-applications/building-blocks/state-management/howto-share-state) for more information |
+> | `spec:metadata:keyPrefix` | Defines the key prefix used when communicating to the statestore backend. See more information, see [Dapr documentation](https://docs.dapr.io/developing-applications/building-blocks/state-management/howto-share-state) for more information |
 > | `spec:metadata:hostname` | The MQTT broker hostname. Default is `aio-mq-dmqtt-frontend` |
 > | `spec:metadata:tcpPort` | The MQTT broker port number. Default is `8883` |
 > | `spec:metadata:useTls` |  Define if TLS is used by the MQTT broker. Default is `true` |
@@ -167,4 +167,4 @@ To configure authorization policies to MQTT broker, first you create a [BrokerAu
 
 ## Next steps
 
-Now that you have deployed the Dapr components, you can [Use Dapr to develop distributed applications](howto-develop-dapr-apps.md).
+Now that the Dapr components are deployed to the cluster, you can [Use Dapr to develop distributed applications](howto-develop-dapr-apps.md).

articles/iot-operations/create-edge-apps/howto-develop-dapr-apps.md

@@ -36,7 +36,7 @@ The first step is to write an application that uses a Dapr SDK to publish/subscr
 
 After you finish writing the Dapr application, build the container:
 
-1. To package the application into a container, run the following command:
+1. Package the application into a container with the following command:
 
     ```bash
     docker build . -t my-dapr-app
@@ -50,9 +50,9 @@ After you finish writing the Dapr application, build the container:
 
 ## Deploy a Dapr application
 
-The following [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) definition contains volumes for SAT authentication and TLS certificate chain, as well as utilizing Dapr sidecar injection to automatically add the pluggable components to the Pod.
+The following [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) definition contains volumes for SAT authentication and TLS certificate chain, and utilizes Dapr sidecar injection to automatically add the pluggable components to the Pod.
 
-The following definition components will typically require customization to your specific application:
+The following definition components might require customization to your specific application:
 
 > | Component | Description |
 > |-|-|
@@ -126,7 +126,7 @@ The following definition components will typically require customization to your
     kubectl get pods -w
     ```
 
-    The pod should report 3 containers running after a short interval, as shown in the following example output:
+    The pod should report three containers running after a short interval, as shown in the following example output:
 
     ```output
     NAME                          READY   STATUS              RESTARTS   AGE
@@ -136,7 +136,7 @@ The following definition components will typically require customization to your
 
 ## Troubleshooting
 
-If the application doesn't start or you see the containers in `CrashLoopBackoff`, the logs for the `daprd` container often contains useful information.
+If the application doesn't start or you see the containers in `CrashLoopBackoff` state, the log for the `daprd` container often contains useful information.
 
 Run the following command to view the logs for the daprd component:
 

articles/iot-operations/create-edge-apps/howto-develop-mqttnet-apps.md

@@ -16,52 +16,49 @@ ms.date: 07/02/2024
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-[MQTTnet](https://dotnet.github.io/MQTTnet/) is an open-source, high performance .NET library for MQTT based communication. This article uses a Kubernetes service account token and MQTTnet to connect to MQTT broker. You should use service account tokens to connect to in-cluster clients.
+[MQTTnet](https://dotnet.github.io/MQTTnet/) is an open-source, high performance .NET library for MQTT based communication. This article uses a Kubernetes service account token and MQTTnet to connect to MQTT broker. You should use service account tokens to connect in-cluster applications.
 
 ## Sample code
 
 The [sample code](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/mqtt-client-dotnet/Program.cs) performs the following steps:
 
-1. Creates an MQTT client using the `MQTTFactory` class:
+1. Creates an MQTT client using the `MqttFactory` class:
 
     ```csharp
     var mqttFactory = new MqttFactory();
     var mqttClient = mqttFactory.CreateMqttClient();
     ```
 
-1. The following Kubernetes pod specification mounts the service account token to the specified path on the container file system. The mounted token is used as the password with well-known username `K8S-SAT`:
+1. The [Kubernetes pod specification](#pod-specification) mounts the service account on the container file system. The contents of the file are read:
+##3. The mounted token is used as the password with well-known username `K8S-SAT`:
 
     ```csharp
-    string token_path = "/var/run/secrets/tokens/mqtt-client-token";
+    static string token_path = "/var/run/secrets/tokens/mqtt-client-token";
     ...
 
-    static async Task<int> MainAsync()
-    {
-        ...
-
-        // Read SAT Token
-        var satToken = File.ReadAllText(token_path);
+    // Read SAT Token
+    var satToken = File.ReadAllText(token_path);
     ```
 
-1. All options for the MQTT client are bundled in the class named `MqttClientOptions`. It's possible to fill options manually in code via the properties but you should use the `MqttClientOptionsBuilder` as advised in the [client](https://github.com/dotnet/MQTTnet/wiki/Client) documentation. The following code shows how to use the builder with the following options:
+1. The MQTT client options are configured using the `MqttClientOptions` class. Using the `MqttClientOptionsBuilder` as advised in the [client](https://github.com/dotnet/MQTTnet/wiki/Client) documentation is the advised way of setting the options:
 
     ```csharp
-    # Create TCP based options using the builder amd connect to broker
+    // Create TCP based options using the builder amd connect to broker
     var mqttClientOptions = new MqttClientOptionsBuilder()
         .WithTcpServer(broker, 1883)
-        .WithProtocolVersion(MqttProtocolVersion.V500)
-        .WithClientId("sampleid")
-        .WithCredentials("K8S-SAT", satToken)
+        .WithProtocolVersion(MqttProtocolVersion.V311)
+        .WithClientId("mqtt-client-dotnet")
+        .WithCredentials("K8S-SAT", satToken);        
         .Build();
     ```
 
-1. After setting up the MQTT client options, a connection can be established. The following code shows how to connect with a server. You can replace the *CancellationToken.None* with a valid *CancellationToken*, if needed.
+5. After setting up the MQTT client options, a connection can be established. The following code shows how to connect with a server. You can replace the *CancellationToken.None* with a valid *CancellationToken*, if needed.
 
     ```csharp
     var response = await mqttClient.ConnectAsync(mqttClientOptions, CancellationToken.None);
     ```
 
-1. MQTT messages can be created using the properties directly or via using `MqttApplicationMessageBuilder`. This class has some useful overloads that allow dealing with different payload formats. The API of the builder is a fluent API. The following code shows how to compose an application message and publish them to a topic called *sampletopic*:
+6. MQTT messages can be created using the properties directly or via using `MqttApplicationMessageBuilder`. This class has some useful overloads that allow dealing with different payload formats. The API of the builder is a fluent API. The following code shows how to compose an application message and publish them to an article called *sampletopic*:
 
     ```csharp
     var applicationMessage = new MqttApplicationMessageBuilder()
@@ -126,5 +123,5 @@ To run the sample, follow the instructions in its [README](https://github.com/Az
 
 ## Related content
 
-- [MQTT broker overview](../manage-mqtt-broker/overview-iot-mq.md)
-- [Develop with MQTT broker](edge-apps-overview.md)
+- [Publish and subscribe MQTT messages using MQTT broker](../manage-mqtt-broker/overview-iot-mq.md)
+- [Develop highly available distributed applications](edge-apps-overview.md)

articles/iot-operations/create-edge-apps/tutorial-event-driven-with-dapr.md

@@ -19,10 +19,10 @@ In this walkthrough, you deploy a Dapr application to the cluster. The Dapr appl
 The Dapr application performs the following steps:
 
 1. Subscribes to the `sensor/data` topic for sensor data.
-1. When data is receiving on the topic, it's forwarded to the MQTT broker state store.
-1. Every **10 seconds**, it fetches the data from the state store and calculates the *min*, *max*, *mean*, *median*, and *75th percentile* values on any sensor data timestamped in the last **30 seconds**.
-1. Data older than **30 seconds** is expired from the state store.
-1. The result is published to the `sensor/window_data` topic in JSON format.
+1. When data is receiving on the topic, it's published to the MQTT broker state store.
+2. Every **10 seconds**, it fetches the data from the state store and calculates the *min*, *max*, *mean*, *median*, and *75th percentile* values on any sensor data timestamped in the last **30 seconds**.
+3. Data older than **30 seconds** is expired from the state store.
+4. The result is published to the `sensor/window_data` topic in JSON format.
 
 > [!NOTE]
 > This tutorial [disables Dapr CloudEvents](https://docs.dapr.io/developing-applications/building-blocks/pubsub/pubsub-raw/) which enables it to publish and subscribe using raw MQTT.
@@ -120,7 +120,7 @@ To start, create a yaml file that uses the following definitions:
 
 Simulate test data by deploying a Kubernetes workload. It simulates a sensor by sending sample temperature, vibration, and pressure readings periodically to the MQTT broker using an MQTT client on the `sensor/data` topic.
 
-1. Deploy the simulator from the Explore IoT Operations repository:
+1. Deploy the simulator from the *Explore IoT Operations* repository:
 
     ```bash
     kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/tutorials/mq-event-driven-dapr/simulate-data.yaml    
@@ -205,7 +205,7 @@ To verify the MQTT bridge is working, deploy an MQTT client to the cluster.
 
 ## Verify the Dapr application output
 
-1. Open a shell to the mosquitto client pod:
+1. Open a shell to the Mosquitto client pod:
 
     ```bash
     kubectl exec --stdin --tty mqtt-client -n azure-iot-operations -- sh
@@ -252,7 +252,7 @@ To verify the MQTT bridge is working, deploy an MQTT client to the cluster.
 
 ## Optional - Create the Dapr application
 
-The above tutorial uses a prebuilt container of the Dapr application. If you would like to modify and build the code yourself, follow these steps:
+ThIs tutorial uses a prebuilt container of the Dapr application. If you would like to modify and build the code yourself, follow these steps:
 
 ### Prerequisites
 
@@ -290,7 +290,7 @@ The above tutorial uses a prebuilt container of the Dapr application. If you wou
 
 ## Troubleshooting
 
-If the application doesn't start or you see the containers in `CrashLoopBackoff`, the logs for the `daprd` container often contains useful information.
+If the application doesn't start or you see the containers in `CrashLoopBackoff`, the `daprd` container log often contains useful information.
 
 Run the following command to view the logs for the daprd component: