Akri clarifications

Author: dominicbetts

articles/iot-operations/get-started/quickstart-add-assets.md

@@ -180,6 +180,9 @@ To verify that the thermostat asset you added is publishing data, view the telem
 
 :::image type="content" source="media/quickstart-add-assets/mqttui-output.png" alt-text="Screenshot of the mqttui topic display showing the temperature telemetry." lightbox="media/quickstart-add-assets/mqttui-output.png":::
 
+> [!TIP]
+> Data from an asset with a name that starts with _boiler-_ is from an asset that was automatically discovered. This is not the same asset as the thermostat asset you created.
+
 If there's no data flowing, restart the `aio-opc-opc.tcp-1` pod:
 
 1. Find the name of your `aio-opc-opc.tcp-1` pod by using the following command:
@@ -223,39 +226,38 @@ In the previous section, you saw how to add assets manually. You can also use Az
 
 When you deploy Azure IoT Operations, the deployment includes the Akri discovery handler pods. To verify these pods are running, run the following command:
 
-```bash
+```console
 kubectl get pods -n azure-iot-operations | grep akri
 ```
 
-```powershell
-kubectl get pods -n azure-iot-operations |  Select-String -Pattern "akri"
-```
-
 The output from the previous command looks like the following example:
 
 ```output
 aio-akri-otel-collector-5c775f745b-g97qv       1/1     Running   3 (4h15m ago)    2d23h
 aio-akri-agent-daemonset-mp6v7                 1/1     Running   3 (4h15m ago)    2d23h
 ```
 
-In your Codespaces terminal, run the following command to apply a new configuration for the discovery handler:
+Use the following command to verify that the discovery pod is running:
 
 ```console
-kubectl apply -f /workspaces/explore-iot-operations/samples/quickstarts/akri-opcua-asset.yaml
+kubectl get pods -n azure-iot-operations | grep discovery
 ```
 
-The following snippet shows the YAML file that you applied:
+The output from the previous command looks like the following example:
 
-:::code language="yaml" source="~/azure-iot-operations-samples/samples/quickstarts/akri-opcua-asset.yaml":::
+```output
+aio-opc-asset-discovery-wzlnj                   1/1     Running     0              19m
+```
+
+> [!TIP]
+> There's currently a known issue where the Akri discovery handler pod might not start. If you encounter this issue, see [Troubleshoot Azure IoT Akri Preview](../troubleshoot/known-issues.md#azure-iot-akri-preview).
 
 To verify the configuration, run the following command to view the Akri instances that represent the OPC UA data sources discovered by Akri:
 
 ```console
 kubectl get akrii -n azure-iot-operations
 ```
 
-It might take a few minutes for the instance to show up.
-
 The output from the previous command looks like the following example.
 
 ```output