Clarifications for NXP board LP

Author: annietllnd

content/learning-paths/embedded-and-microcontrollers/linux-nxp-board/1-overview.md

@@ -22,13 +22,6 @@ The following image highlights the i.MX 93 SoC and the NPU location on the board
 
 ![NXP FRDM i.MX 93 Board SoC Highlighted alt-text#center](./nxp-frdm-imx93-board-soc-highlighted.png "Arm Ethos-U65 NPU location")
 
-If you connect the board to a display, you can see ML demos and application output directly on the device. This is useful when you want quick visual confirmation that your model runs on the target hardware.
-
-## Unbox and power the board
-
-To set up the hardware, follow NXP’s getting started guide: [Getting Started with FRDM-IMX93](https://www.nxp.com/document/guide/getting-started-with-frdm-imx93:GS-FRDM-IMX93).
-
-Stop when you complete section "1.6 Connect Power Supply".
 
 ## Connect to the serial console and log in
 
@@ -46,7 +39,6 @@ sudo apt install -y picocom
 
 
 {{% notice macOS %}}
-
 On macOS, you might need an extra USB-to-UART driver depending on which USB serial bridge the board exposes. You can get the drivers from Silicon Labs [Downloads page](https://www.silabs.com/developer-tools/usb-to-uart-bridge-vcp-drivers?tab=downloads).
 {{% /notice %}}
 
@@ -100,7 +92,11 @@ Type `root` to log in as root (no password is needed).
 
 ## (Optional) Run the built-in NXP demos
 
+If you connect the board to a display, you can see ML demos and application output directly on the device. This is useful when you want quick visual confirmation that your model runs on the target hardware. As per the setup instructions in [NXP’s getting started guide](https://www.nxp.com/document/guide/getting-started-with-frdm-imx93:GS-FRDM-IMX93):
+
 - Connect the board to a monitor via HDMI.
 - Connect a mouse to the board’s USB-A port.
 
+The demos will then show up automatically.
+
 ![NXP board built-in ML demos alt-text#center](./nxp-board-built-in-ml-demos.png "NXP board built-in ML demos")

content/learning-paths/embedded-and-microcontrollers/linux-nxp-board/4-enable-wifi.md

@@ -8,8 +8,6 @@ weight: 4 # 1 is first, 2 is second, etc.
 layout: "learningpathall"
 ---
 
-Proceed with the remainder of this Learning Path logged in as `root`. 
-
 Once the board is on your network, copying files over SSH is usually the fastest workflow. If you can’t use WiFi, you can still move files with a USB drive. Create a test file to transfer.
 
 ```bash
@@ -26,7 +24,7 @@ ifconfig | grep RUNNING -A 1
 
 Look for the WiFi interface (often `mlan0`) and note the `inet` address.
 
-On your development machine, copy a file to the board with `scp` by updating the IP address in the following command:
+On your host machine, copy a file to the board with `scp` by updating the IP address in the following command:
 
 ```bash
 scp test.txt root@<ip-address>:/root/test.txt
@@ -68,8 +66,8 @@ umount /mnt
 You should now see the file in the `root` directory:
 
 ```output
-root@imx93evk:~# ls /root
+:~# ls /root
 test.txt
 ```
 
-Proceed to the final section to automate reconnecting to wifi.
+Proceed to the final section to automate reconnecting to WiFi.

content/learning-paths/embedded-and-microcontrollers/linux-nxp-board/7-enable-persistent-wifi.md

@@ -8,7 +8,7 @@ weight: 5 # 1 is first, 2 is second, etc.
 layout: "learningpathall"
 ---
 
-ConnMan usually persists your WiFi network configuration across reboots. On this Linux image, the missing piece is often that the WiFi driver module isn’t loaded automatically at boot.
+ConnMan persists your WiFi network configuration across reboots. On this Linux image, the missing piece is often that the WiFi driver module isn’t loaded automatically at boot.
 
 In this section, you’ll run one command at boot to load the WiFi driver. After that, ConnMan should reconnect to the saved network automatically.