Edits for accuracy

Author: jlian

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

@@ -411,7 +411,6 @@ In the operations experience, select the **Advanced** tab for the dataflow endpo
 
 ```bicep
 dataLakeStorageSettings: {
-  ...
   batching: {
     latencySeconds: 100
     maxMessages: 1000
@@ -422,7 +421,7 @@ dataLakeStorageSettings: {
 # [Kubernetes](#tab/kubernetes)
 
 ```yaml
-fabricOneLakeSettings:
+dataLakeStorageSettings:
   batching:
     latencySeconds: 100
     maxMessages: 1000

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

@@ -138,6 +138,31 @@ kubectl apply -f <FILE>.yaml
 
 ---
 
+## OneLake path type
+
+The `oneLakePathType` setting determines the type of path to use in the OneLake path. The default value is `Tables`, which is the recommended path type for the most common use cases. The `Tables` path type is a table in the OneLake lakehouse that is used to store the data. It can also be set as `Files`, which is a file in the OneLake lakehouse that is used to store the data. The `Files` path type is useful when you want to store the data in a file format that isn't supported by the `Tables` path type.
+
+# [Portal](#tab/portal)
+
+The OneLake path type is set in the **Basic** tab for the dataflow endpoint.
+
+# [Bicep](#tab/bicep)
+
+```bicep
+fabricOneLakeSettings: {
+  oneLakePathType: 'Tables' // Or 'Files'
+}
+```
+
+# [Kubernetes](#tab/kubernetes)
+
+```yaml
+fabricOneLakeSettings:
+  oneLakePathType: Tables # Or Files
+```
+
+---
+
 ## Available authentication methods
 
 The following authentication methods are available for Microsoft Fabric OneLake dataflow endpoints. For more information about enabling secure settings by configuring an Azure Key Vault and enabling workload identities, see [Enable secure settings in Azure IoT Operations Preview deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
@@ -257,35 +282,12 @@ fabricOneLakeSettings:
 
 ---
 
+Here, the scope is optional and defaults to `https://storage.azure.com/.default`. If you need to override the default scope, specify the `scope` setting using Bicep or Kubernetes.
+
 ## Advanced settings
 
 You can set advanced settings for the Fabric OneLake endpoint, such as the batching latency and message count. You can set these settings in the dataflow endpoint **Advanced** portal tab or within the dataflow endpoint custom resource.
 
-### OneLake path type
-
-The `oneLakePathType` setting determines the type of path to use in the OneLake path. The default value is `Tables`, which is the recommended path type for the most common use cases. The `Tables` path type is a table in the OneLake lakehouse that is used to store the data. It can also be set as `Files`, which is a file in the OneLake lakehouse that is used to store the data. The `Files` path type is useful when you want to store the data in a file format that isn't supported by the `Tables` path type.
-
-# [Portal](#tab/portal)
-
-The OneLake path type is set in the **Basic** tab for the dataflow endpoint.
-
-# [Bicep](#tab/bicep)
-
-```bicep
-fabricOneLakeSettings: {
-  oneLakePathType: 'Tables' // Or 'Files'
-}
-```
-
-# [Kubernetes](#tab/kubernetes)
-
-```yaml
-fabricOneLakeSettings:
-  oneLakePathType: Tables # Or Files
-```
-
----
-
 ### Batching
 
 Use the `batching` settings to configure the maximum number of messages and the maximum latency before the messages are sent to the destination. This setting is useful when you want to optimize for network bandwidth and reduce the number of requests to the destination.

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

@@ -29,7 +29,9 @@ To set up bi-directional communication between Azure IoT Operations Preview and
 
 ### Create an Azure Event Hubs namespace and event hub in it
 
-First, [create a Kafka-enabled Azure Event Hubs namespace](../../event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md) and a event hub for each Kafka topic. 
+First, [create a Kafka-enabled Azure Event Hubs namespace](../../event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md)
+
+Next, [create an event hub in the namespace](../../event-hubs/event-hubs-create.md#create-an-event-hub). Each individual event hub corresponds to a Kafka topic. You can create multiple event hubs in the same namespace to represent multiple Kafka topics. 
 
 ### Assign the managed identity to the Event Hubs namespace
 
@@ -52,10 +54,7 @@ Finally, create the *DataflowEndpoint* resource. Use your own values to replace
     | -------------------- | ------------------------------------------------------------------------------------------------- |
     | Name                 | The name of the dataflow endpoint.                                     |
     | Host                 | The hostname of the Kafka broker in the format `<NAMEPSACE>.servicebus.windows.net:9093`. Include port number `9093` in the host setting for Event Hubs. |
-    | Authentication method| The method used for authentication. Choose *System assigned managed identity*, *User assigned managed identity*, or *SASL*. |
-    | SASL type            | The type of SASL authentication. Choose *Plain*, *ScramSha256*, or *ScramSha512*. Required if using *SASL*. |
-    | Synced secret name   | The name of the secret. Required if using *SASL* or *X509*. |
-    | Username reference of token secret | The reference to the username in the SASL token secret. Required if using *SASL*. |
+    | Authentication method| The method used for authentication. Choose *System assigned managed identity* |
 
 1. Select **Apply** to provision the endpoint.
 

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

@@ -183,11 +183,11 @@ resource remoteMqttBrokerDataflowEndpoint 'Microsoft.IoTOperations/instances/dat
   properties: {
     endpointType: 'Mqtt'
     mqttSettings: {
+      host: eventGridHostName
       authentication: {
         method: 'SystemAssignedManagedIdentity'
         systemAssignedManagedIdentitySettings: {}
       }
-      host: eventGridHostName
       tls: {
         mode: 'Enabled'
       }
@@ -274,9 +274,6 @@ resource dataflow_1 'Microsoft.IoTOperations/instances/dataflowProfiles/dataflow
     ]
   }
 } 
-```
-
-```bicep
 resource dataflow_2 'Microsoft.IoTOperations/instances/dataflowProfiles/dataflows@2024-09-15-preview' = {
   parent: defaultDataflowProfile
   name: 'remote-to-local'