Cleanup

Author: PatAltimore

articles/iot-operations/connect-to-cloud/howto-configure-dataflow-endpoint.md

@@ -64,7 +64,7 @@ spec:
 
 ---
 
-Similarly, you can create multiple dataflows that use the same MQTT endpoint for other endpoints and topics. For example, you can use the same MQTT endpoint for a dataflow that sends data to sends data to Kafka.
+Similarly, you can create multiple dataflows that use the same MQTT endpoint for other endpoints and topics. For example, you can use the same MQTT endpoint for a dataflow that sends data to a Kafka endpoint.
 
 # [Portal](#tab/portal)
 

articles/iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md

@@ -77,7 +77,7 @@ This configuration creates a connection to the default MQTT broker with the foll
 
 # [Bicep](#tab/bicep)
 
-This Bicep template file from [Bicep File for MQTT-bridge dataflow Tutorial](https://gist.github.com/david-emakenemi/7a72df52c2e7a51d2424f36143b7da85) deploys the necessary dataflow and dataflow enpoints for MQTT broker and Azure Event Grid.
+This Bicep template file from [Bicep File for MQTT-bridge dataflow Tutorial](https://gist.github.com/david-emakenemi/7a72df52c2e7a51d2424f36143b7da85) deploys the necessary dataflow and dataflow endpoints for MQTT broker and Azure Event Grid.
 
 Download the file to your local, and make sure to replace the values for `customLocationName`, `aioInstanceName`, `eventGridHostName`.
 

articles/iot-operations/connect-to-cloud/howto-create-dataflow.md

@@ -232,7 +232,7 @@ Key names in the distributed state store correspond to a dataset in the dataflow
 
 # [Portal](#tab/portal)
 
-Currently, the enrich operation is not available in the operations experience portal.
+Currently, the enrich operation isn't available in the operations experience portal.
 
 # [Kubernetes](#tab/kubernetes)
 

articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md

@@ -148,7 +148,7 @@ example.region-1.ts.eventgrid.azure.net
 
 # [Bicep](#tab/bicep)
 
-The dataflow and dataflow endpoints for MQTT broker and Azure Event Grid can be deployed as standard Azure resources since they have Azure Resource Provider (RPs) implementations. This Bicep template file from [Bicep File for MQTT-bridge dataflow Tutorial](https://gist.github.com/david-emakenemi/7a72df52c2e7a51d2424f36143b7da85) deploys the necessary dataflow and dataflow enpoints.
+The dataflow and dataflow endpoints for MQTT broker and Azure Event Grid can be deployed as standard Azure resources since they have Azure Resource Provider (RPs) implementations. This Bicep template file from [Bicep File for MQTT-bridge dataflow Tutorial](https://gist.github.com/david-emakenemi/7a72df52c2e7a51d2424f36143b7da85) deploys the necessary dataflow and dataflow endpoints.
 
 Download the file to your local, and make sure to replace the values for `customLocationName`, `aioInstanceName`, `eventGridHostName` with yours.
 
@@ -212,7 +212,7 @@ This is the default configuration for the Azure IoT Operations MQTT broker endpo
 
 # [Bicep](#tab/bicep)
 
-Since you already deployed the resources in the previous section, there's no additional deployment needed. However, this endpoint is the destination for the dataflow that sends messages to Azure Event Grid. Replace `<EVENT-GRID-HOSTNAME>` with the hostname you got from the previous step, include the port number `8883`.
+Since you already deployed the resources in the previous section, there's no additional deployment needed. However, this endpoint is the destination for the dataflow that sends messages to Azure Event Grid. Replace `<EVENT-GRID-HOSTNAME>` with the hostname you got from the previous step. Include the port number `8883`.
 
 ```bicep
 resource remoteMqttBrokerDataflowEndpoint 'Microsoft.IoTOperations/instances/dataflowEndpoints@2024-08-15-preview' = {
@@ -240,7 +240,7 @@ resource remoteMqttBrokerDataflowEndpoint 'Microsoft.IoTOperations/instances/dat
 
 # [Kubernetes](#tab/kubernetes)
 
-Create dataflow endpoint for the Azure Event Grid. This endpoint is the destination for the dataflow that sends messages to Azure Event Grid. Replace `<EVENT-GRID-HOSTNAME>` with the hostname you got from the previous step, include the port number `8883`.
+Create dataflow endpoint for the Azure Event Grid. This endpoint is the destination for the dataflow that sends messages to Azure Event Grid. Replace `<EVENT-GRID-HOSTNAME>` with the hostname you got from the previous step. Include the port number `8883`.
 
 ```yaml
 apiVersion: connectivity.iotoperations.azure.com/v1beta1
@@ -395,7 +395,7 @@ To verify the MQTT bridge is working, deploy an MQTT client to the same namespac
 
 # [Bicep](#tab/bicep)
 
-Currently, bicep does not apply to deploy MQTT client.
+Currently, bicep doesn't apply to deploy MQTT client.
 
 # [Kubernetes](#tab/kubernetes)