Tidy up

dominicbetts · dominicbetts · commit 048fbc4b7581 · 2024-09-19T14:44:59.000+01:00
diff --git a/articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md b/articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md
@@ -31,7 +31,7 @@ This article describes how to use the operations experience web UI and the Azure
 - Define the asset endpoints that connect assets to your Azure IoT Operations instance.
 - Add assets, and define their tags and events to enable dataflow from OPC UA servers to the MQTT broker.
 
-These assets, tags, and events map inbound data from OPC UA servers to friendly names that you can use in the MQTT broker and data processor pipelines.
+These assets, tags, and events map inbound data from OPC UA servers to friendly names that you can use in the MQTT broker and dataflows.
 
 ## Prerequisites
 
@@ -126,7 +126,7 @@ To learn more, see [az iot ops asset endpoint](/cli/azure/iot/ops/asset/endpoint
 
 This configuration deploys a new `assetendpointprofile` resource called `opc-ua-connector-0` to the cluster. After you define an asset, a connector for OPC UA pod discovers it. The pod uses the asset endpoint that you specify in the asset definition to connect to an OPC UA server.
 
-When the OPC PLC simulator is running, data flows from the simulator, to the connector for OPC UA, and then to the MQTT broker.
+When the OPC PLC simulator is running, dataflows from the simulator, to the connector for OPC UA, and then to the MQTT broker.
 
 ### Configure an asset endpoint to use a username and password
 
diff --git a/articles/iot-operations/discover-manage-assets/overview-manage-assets.md b/articles/iot-operations/discover-manage-assets/overview-manage-assets.md
@@ -36,7 +36,7 @@ The following diagram shows the high-level architecture of Azure IoT Operations.
 
 - The **operations experience** is a web UI that lets you create and configure assets in your solution. The web UI simplifies the task of managing assets and is the recommended service to manage assets.
 - **Azure Device Registry Preview** is a backend service that enables the cloud and edge management of assets. Device Registry projects assets defined in your edge environment as Azure resources in the cloud. It provides a single unified registry so that all apps and services that interact with your assets can connect to a single source. Device Registry also manages the synchronization between assets in the cloud and assets as custom resources in Kubernetes on the edge.
-- The schema registry is a service that lets you define and manage the schema for your assets. Data flows use schemas to deserialize and serialize messages.
+- The schema registry is a service that lets you define and manage the schema for your assets. Dataflows use schemas to deserialize and serialize messages.
 - The **connector for OPC UA** is a data ingress and protocol translation service that enables Azure IoT Operations to ingress data from your assets. The broker receives telemetry and events from your assets and publishes the data to topics in the MQTT broker. The broker is based on the widely used OPC UA standard.
 
 ## Create and manage assets remotely
diff --git a/articles/iot-operations/get-started-end-to-end-sample/quickstart-add-assets.md b/articles/iot-operations/get-started-end-to-end-sample/quickstart-add-assets.md
@@ -33,7 +33,7 @@ Unless otherwise noted, you can run the console commands in this quickstart in e
 
 ## What problem will we solve?
 
-The data that OPC UA servers expose can have a complex structure and can be difficult to understand. Azure IoT Operations provides a way to model OPC UA assets as tags, events, and properties. This modeling makes it easier to understand the data and to use it in downstream processes such as the MQTT broker and data processor pipelines.
+The data that OPC UA servers expose can have a complex structure and can be difficult to understand. Azure IoT Operations provides a way to model OPC UA assets as tags, events, and properties. This modeling makes it easier to understand the data and to use it in downstream processes such as the MQTT broker and dataflows.
 
 ## Deploy the OPC PLC simulator
 
diff --git a/articles/iot-operations/includes/add-cluster-secret.md b/articles/iot-operations/includes/add-cluster-secret.md
diff --git a/articles/iot-operations/manage-mqtt-broker/overview-iot-mq.md b/articles/iot-operations/manage-mqtt-broker/overview-iot-mq.md
@@ -1,6 +1,6 @@
 ---
 title: Publish and subscribe MQTT messages using MQTT broker
-description: Use MQTT broker to publish and subscribe to messages. Destinations include other MQTT brokers, Azure IoT Data Processor, and Azure cloud services.
+description: Use MQTT broker to publish and subscribe to messages. Destinations include other MQTT brokers, dataflows, and Azure cloud services.
 author: PatAltimore
 ms.author: patricka
 ms.subservice: azure-mqtt-broker
diff --git a/articles/iot-operations/overview-iot-operations.md b/articles/iot-operations/overview-iot-operations.md
@@ -35,7 +35,7 @@ There are two core elements in the Azure IoT Operations Preview architecture:
 * **Azure IoT Operations Preview**. The set of data services that run on Azure Arc-enabled edge Kubernetes clusters. It includes the following services:
   * The _MQTT broker_ is an edge-native MQTT broker that powers event-driven architectures.
   * The _connector for OPC UA_ handles the complexities of OPC UA communication with OPC UA servers and other leaf devices.
-* The _operations experience_ is a web UI that provides a unified experience for operational technologists to manage assets and data processor pipelines in an Azure IoT Operations deployment. An IT administrator can use [Azure Arc site manager (preview)](../azure-arc/site-manager/overview.md) to group Azure IoT Operations instances by physical location and make it easier for OT users to find instances.
+* The _operations experience_ is a web UI that provides a unified experience for operational technologists to manage assets and dataflows in an Azure IoT Operations deployment. An IT administrator can use [Azure Arc site manager (preview)](../azure-arc/site-manager/overview.md) to group Azure IoT Operations instances by physical location and make it easier for OT users to find instances.
 
 ## Deploy
 
@@ -66,7 +66,7 @@ The [MQTT broker](manage-mqtt-broker/overview-iot-mq.md) runs on the edge. It le
 Examples of how components in Azure IoT Operations use the MQTT broker include:
 
 * The connector for OPC UA publishes data from OPC UA servers and other leaf devices to MQTT topics.
-* Data processor pipelines subscribe to MQTT topics to retrieve messages for processing.
+* Dataflows subscribe to MQTT topics to retrieve messages for processing.
 * Northbound cloud connectors subscribe to MQTT topics to fetch messages for forwarding to cloud services.
 
 ## Connect to the cloud
@@ -81,7 +81,7 @@ The northbound cloud connectors let you connect the MQTT broker directly to clou
 
 ## Process data
 
-In Azure IoT operations v0.6.0, the data processor is replaced by [data flows](./connect-to-cloud/overview-dataflow.md). Data flows provide enhanced data transformation and data contextualization capabilities within Azure IoT Operations. Data flows can use schemas stored in the schema registry to deserialize and serialize messages.
+In Azure IoT operations v0.6.0, the data processor is replaced by [dataflows](./connect-to-cloud/overview-dataflow.md). Dataflows provide enhanced data transformation and data contextualization capabilities within Azure IoT Operations. Dataflows can use schemas stored in the schema registry to deserialize and serialize messages.
 
 > [!NOTE]
 > If you want to continue using the data processor, you must deploy Azure IoT Operations v0.5.1 with the additional flag to include data processor component. It's not possible to deploy the data processor with Azure IoT Operations v0.6.0. The Azure IoT operations CLI extension that includes the flag for deploying the data processor is version 0.5.1b1. This version requires Azure CLI v2.46.0 or greater. The data processor documentation is currently available on the previous versions site: [Azure IoT Operations data processor](/previous-versions/azure/iot-operations/process-data/overview-data-processor).
diff --git a/articles/iot-operations/reference/glossary.md b/articles/iot-operations/reference/glossary.md
@@ -27,9 +27,9 @@ A unified data plane for the edge. It's a collection of modular, scalable, and h
 
 On first mention in an article, use _Azure IoT Operations Preview - enabled by Azure Arc_. On subsequent mentions, you can use _Azure IoT Operations_. Never use an acronym.
 
-### Data processor
+### Dataflows
 
-This component lets you aggregate, enrich, normalize, and filter the data from your devices and assets. The data processor is a pipeline-based data processing engine that lets you process data at the edge before you send it to the other services either at the edge or in the cloud
+This component lets you aggregate, enrich, normalize, and filter the data from your devices and assets. The dataflows is a data processing engine that lets you process data at the edge before you send it to the other services either at the edge or in the cloud
 
 ### Azure IoT Layered Network Management Preview
 
@@ -47,7 +47,7 @@ This component manages the connection to OPC UA servers and other leaf devices.
 
 ### Operations experience
 
-This web UI provides a unified experience for operational technologists to manage assets and data processor pipelines in an Azure IoT Operations deployment.
+This web UI provides a unified experience for operational technologists to manage assets and dataflows in an Azure IoT Operations deployment.
 
 ### Azure Device Registry Preview
 
diff --git a/articles/iot-operations/troubleshoot/troubleshoot.md b/articles/iot-operations/troubleshoot/troubleshoot.md
@@ -19,59 +19,12 @@ This article contains troubleshooting tips for Azure IoT Operations Preview.
 
 For general deployment and configuration troubleshooting, you can use the Azure CLI IoT Operations *check* and *support* commands.
 
-[Azure CLI version 2.46.0 or higher](/cli/azure/install-azure-cli) is required and the [Azure IoT Operations extension](/cli/azure/iot/ops) installed.
+[Azure CLI version 2.52.0 or higher](/cli/azure/install-azure-cli) is required and the [Azure IoT Operations extension](/cli/azure/iot/ops) installed.
 
 - Use [az iot ops check](/cli/azure/iot/ops#az-iot-ops-check) to evaluate Azure IoT Operations service deployment for health, configuration, and usability. The *check* command can help you find problems in your deployment and configuration.
 
 - Use [az iot ops support create-bundle](/cli/azure/iot/ops/support#az-iot-ops-support-create-bundle) to collect logs and traces to help you diagnose problems. The *support create-bundle* command creates a standard support bundle zip archive you can review or provide to Microsoft Support.
 
-## Data processor pipeline deployment troubleshooting
-
-If your data processor pipeline deployment status is showing as **Failed**, use the following commands to find the pipeline error codes.
-
-To list the data processor pipeline deployments, run the following command:
-
-```bash
-kubectl get pipelines -A
-```
-
-The output from the pervious command looks like the following example:
-
-```text
-NAMESPACE                NAME                           AGE
-azure-iot-operations     passthrough-data-pipeline      2d20h
-azure-iot-operations     reference-data-pipeline        2d20h
-azure-iot-operations     contextualized-data-pipeline   2d20h
-```
-
-To view detailed information for a pipeline, run the following command:
-
-```bash
-kubectl describe pipelines passthrough-data-pipeline -n azure-iot-operations
-```
-
-The output from the previous command looks like the following example:
-
-```text
-...
-Status:
-  Provisioning Status:
-    Error
-      Code:  <ErrorCode>
-      Message: <ErrorMessage>
-    Status:        Failed
-Events:            <none>
-```
-
-If you see the following message when you try to access the **Pipelines** tab in the Azure IoT Operations (preview) portal:
-
-_Data Processor not found in the current deployment. Please re-deploy with the additional argument to include the data processor._
-
-You need to deploy Azure IoT Operations with the optional data processor component included. To do this, you need to add the `--include-dp` argument when you run the [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command. You must use the `--include-dp` argument to include the data processor component when you first deploy Azure IoT Operations. You can't add this optional component to an existing deployment.
-
-> [!TIP]
-> If you want to delete the Azure IoT Operations deployment but plan on reinstalling it on your cluster, use the [az iot ops delete](/cli/azure/iot/ops?az-iot-ops-delete) command.
-
 ## Azure IoT Layered Network Management Preview troubleshooting
 
 The troubleshooting guidance in this section is specific to Azure IoT Operations when using the Layered Network Management component. For more information, see [How does Azure IoT Operations Preview work in layered network?](../manage-layered-network/concept-iot-operations-in-layered-network.md).
