Merge pull request #276278 from dominicbetts/aio-qs-fixes

AIO: Fix example output in quickstart

Author: prmerger-automator[bot]

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

@@ -235,8 +235,7 @@ kubectl get pods -n azure-iot-operations |  Select-String -Pattern "akri"
 
 The output from the previous command looks like the following example:
 
-```console
-akri-opcua-asset-discovery-daemonset-h47zk     1/1     Running   3 (4h15m ago)    2d23h
+```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
 ```
@@ -261,16 +260,16 @@ It might take a few minutes for the instance to show up.
 
 The output from the previous command looks like the following example.
 
-```console
-NAMESPACE              NAME                      CONFIG             SHARED   NODES            AGE
-azure-iot-operations   akri-opcua-asset-dbdef0   akri-opcua-asset   true     ["dom-aio-vm"]   35m
+```output
+NAME                      CONFIG             SHARED   NODES                          AGE
+akri-opcua-asset-dbdef0   akri-opcua-asset   true     ["k3d-k3s-default-server-0"]   45s
 ```
 
 Now you can use these resources in the local cluster namespace.
 
 To confirm that Akri connected to the OPC UA Broker, copy and paste the name of the Akri instance from the previous step into the following command:
 
-```bash
+```console
 kubectl get akrii <AKRI_INSTANCE_NAME> -n azure-iot-operations -o json
 ```