Update opc topic

Author: dominicbetts

articles/iot-operations/get-started/quickstart-process-telemetry.md

@@ -71,7 +71,7 @@ In the following steps, leave all values at their default unless otherwise speci
     | Name          | `input data`                    |
     | Broker        | `tls://aio-mq-dmqtt-frontend:8883` |
     | Authentication| `Service account token (SAT)`                  |
-    | Topic         | `azure-iot-operations/data/opc.tcp/opc.tcp-1/#`                    |
+    | Topic         | `azure-iot-operations/data/#`                    |
     | Data format   | `JSON`                              |
 
 1. Select **Transform** from **Pipeline Stages** as the second stage in this pipeline. Enter the following values and then select **Apply**:
@@ -189,7 +189,7 @@ Create a Data Processor pipeline to process and enrich your data before it sends
     | Display name  | `OPC UA data` |
     | Broker        | `tls://aio-mq-dmqtt-frontend:8883` |
     | Authentication| `Service account token (SAT)` |
-    | Topic         | `azure-iot-operations/data/opc.tcp/opc.tcp-1/thermostat` |
+    | Topic         | `azure-iot-operations/data/thermostat` |
     | Data Format   | `JSON` |
 
 1. To track the last known value (LKV) of the temperature, select **Stages**, and select **Last known values**. Use the information the following tables to configure the stage to track the LKVs of temperature for the messages that only have boiler status messages, then select **Apply**:

articles/iot-operations/process-data/howto-configure-datasource-mq.md

@@ -75,7 +75,7 @@ The following shows an example configuration for the stage:
 | Name | `input data` |
 | Broker | `tls://aio-mq-dmqtt-frontend:8883` |
 | Authentication | `Service Account Token (SAT)` |
-| Topic | `azure-iot-operations/data/opc.tcp/opc.tcp-1/#` |
+| Topic | `azure-iot-operations/data/#` |
 | Data format | `JSON` |
 
 This example shows the topic used in the [Quickstart: Use Data Processor pipelines to process data from your OPC UA assets](../get-started/quickstart-process-telemetry.md). This configuration then generates messages that look like the following example: