Merge pull request #3211 from madeline-underwood/device

Device

Author: jasonrandrews

content/learning-paths/embedded-and-microcontrollers/device-connect-d2d/_index.md

@@ -3,9 +3,6 @@ title: Device-to-Device communication with Device Connect
 
 minutes_to_complete: 25
 
-draft: true
-cascade:
-    draft: true
 
 who_is_this_for: This is an introductory topic for developers wiring up heterogeneous edge fleets, where devices need a shared way to find each other and a shared way to be controlled by agents. Device Connect provides this communication protocol between agents and devices, and standardizes how devices from different vendors advertise themselves and exchange structured messages, so both peer devices and AI agents can discover and invoke them through the same driver model. You'll use it to stand up peer-to-peer communication between two devices, with no broker or cloud service in between.
 

content/learning-paths/embedded-and-microcontrollers/device-connect-strands/_index.md

@@ -1,14 +1,11 @@
 ---
 title: Connect AI agents to edge devices using Device Connect and Strands
-
-draft: true
-cascade:
-    draft: true
-
+description: Learn how to connect AI agents to Arm-based edge devices using Device Connect for structured device access and Strands for agent orchestration, with examples for both simulated and physical robots.
 minutes_to_complete: 30
 
 who_is_this_for: This is an introductory topic for software developers who want to connect AI agents to edge devices. You'll use Device Connect, Arm's platform for structured device access, and Strands, AWS's open-source agent SDK. The examples cover both physical and simulated devices.
 
+
 learning_objectives:
     - Understand how Device Connect and Strands work together to give AI agents structured access to Arm-based edge devices
     - Set up a Python environment with the Device Connect SDK and agent tools installed from source

content/learning-paths/embedded-and-microcontrollers/device-connect-strands/run-example.md

@@ -1,14 +1,14 @@
 ---
-title: Run the example end to end
+title: Run device discovery and agent control examples
 weight: 4
 
 # FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
 
-## Overview
+## Run device-to-device discovery and control
 
-This section runs Device Connect's device-to-device discovery. There are two ways to walk through this setup. Optionally, you can connect an external device. 
+This section demonstrates Device Connect's device-to-device discovery. There are two ways to walk through this setup. Optionally, you can connect an external device. 
 
 ### Option 1: run on a single machine
 
@@ -64,7 +64,7 @@ Two things happen when this script runs.
 
 ![Sequence diagram showing the call flow when r.run() executes: the script calls Robot() and DeviceRuntime, which announces presence to the Zenoh mesh, subscribes to the command topic, registers RPC handlers, and starts emitting stateUpdate events at 10 Hz#center](./images/visual2.png "Call flow inside r.run(): device registration and event publishing over Zenoh")
 
-You should see INFO-level log output similar to:
+The output is similar to:
 
 ```output
 device_connect_sdk.device.so100-abc123 - INFO - Using ZENOH messaging backend

content/learning-paths/embedded-and-microcontrollers/device-connect-strands/run-infra-example.md

@@ -108,7 +108,9 @@ r.run()
 PY
 ```
 
-Because `ZENOH_CONNECT` points at your host, the SDK routes traffic through the Device Connect router instead of using local network discovery. The robot registers with the persistent registry and you should see output similar to:
+Because `ZENOH_CONNECT` points at your host, the SDK routes traffic through the Device Connect router instead of using local network discovery. The robot registers with the persistent registry.
+
+The output is similar to:
 
 ```output
 INFO:strands_robots.mesh:Zenoh session started

content/learning-paths/embedded-and-microcontrollers/device-connect-strands/setup.md

@@ -1,5 +1,5 @@
 ---
-title: Set up the developer environment
+title: Set up the Device Connect and Strands developer environment
 weight: 3
 
 # FIXED, DO NOT MODIFY
@@ -38,7 +38,7 @@ source .venv/bin/activate
 
 The `strands-robots` SDK uses Device Connect's built-in device-to-device discovery: every `Robot()` instance announces itself on the local network at startup, and any process running `discover_devices()` or `robot_mesh(action='peers')` on the same network segment will find it automatically.
 
-This means discovery works as long as the device process and the agent process are on the same LAN or on the same machine. Discovery is typically available on home and office networks. If you are behind a firewall or VPN that blocks local network traffic, devices will not discover each other - that scenario requires the infrastructure-backed setup with a Zenoh router, which is covered later in this Learning Path.
+This means discovery works as long as the device process and the agent process are on the same LAN or on the same machine. Discovery is typically available on home and office networks. If you're behind a firewall or VPN that blocks local network traffic, devices won't discover each other - that scenario requires the infrastructure-backed setup with a Zenoh router, which is covered later in this Learning Path.
 
 ## What you've set up and what's next