more alterations

Author: anupras-mohapatra-arm

content/learning-paths/embedded-and-microcontrollers/zephyr_shell/1_installation.md

@@ -24,7 +24,7 @@ Before working through this Learning Path, complete [Build Zephyr projects with
 
 The two examples in this Learning Path have additional requirements:
 
-- MQTT shell example: Docker Desktop, Docker Engine, or another Docker-compatible runtime on your host computer. The board communicates with a Mosquitto broker running in a container.
+- MQTT shell example: Docker Desktop, Docker Engine, or another Docker-compatible runtime on your host computer, if you're not installing Mosquitto on host. The board communicates with a Mosquitto broker running in a container.
 - UART shell example: A USB cable to connect the development board to your host computer. The board exposes a shell prompt over the USB serial interface.
 
 ## Hardware requirements

content/learning-paths/embedded-and-microcontrollers/zephyr_shell/2_overview.md

@@ -35,7 +35,7 @@ In this Learning Path, you'll work with two transports:
 
 ### MQTT backend
 
-Enable the MQTT backend with `CONFIG_SHELL_BACKEND_MQTT=y`. The MQTT backend routes shell commands and responses over MQTT topics. The board subscribes to `<device_id>/sh/rx` for inbound commands and publishes responses to `<device_id>/sh/tx`. The backend connects automatically once the board has an IPv4 address, and is IPv4-only.
+Enable the MQTT backend with `CONFIG_SHELL_BACKEND_MQTT=y`. The MQTT backend routes shell commands and responses over MQTT topics. The board subscribes to `<device_id>/sh/rx` for inbound commands and publishes responses to `<device_id>/sh/tx`. The backend connects automatically when the board has an IPv4 address. The backend is IPv4-only.
 
 ### UART backend 
 

content/learning-paths/embedded-and-microcontrollers/zephyr_shell/3_mqtt_shell.md

@@ -48,7 +48,7 @@ To create an application project in Workbench for Zephyr:
 
 ### Configure the application
 
-The `hello_world` sample provides a working `CMakeLists.txt`, `prj.conf`, and `src/main.c`. Leave `CMakeLists.txt` unchanged, and replace `prj.conf` and `src/main.c` with the following contents.
+The `hello_world` sample provides a working `CMakeLists.txt`, `prj.conf`, and `src/main.c`. Leave `CMakeLists.txt` unchanged, and replace `prj.conf` and `src/main.c`.
 
 Replace the contents of `prj.conf` with the following text:
 
@@ -80,7 +80,7 @@ CONFIG_NET_BUF_RX_COUNT=32
 
 Replace `192.168.1.233` with the IP address of the host running Mosquitto, as seen from the board's Ethernet network.
 
-The values under "Resource tuning" keep the shell footprint small on Cortex-M and allow the network stack and MQTT client to operate reliably.
+The values under `# Resource tuning` keep the shell footprint small on Cortex-M and allow the network stack and MQTT client to operate reliably.
 
 #### Use a static IPv4 address
 
@@ -90,7 +90,7 @@ DHCP is convenient, but it's not required. To use a static address, remove:
 CONFIG_NET_DHCPV4=y
 ```
 
-Then add values that match your network:
+Then, add values that match your network:
 
 ```text
 CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.168.1.50"
@@ -117,7 +117,7 @@ int main(void)
 
 In the **Workbench for Zephyr** panel, select your project and build configuration. Select **Build**, then select **Flash**.
 
-The FRDM-MCXN947 uses NXP LinkServer as the debug runner. If LinkServer isn't installed, follow the Workbench for Zephyr prompt to install or configure it.
+The FRDM-MCXN947 uses NXP LinkServer as the debug runner. If LinkServer isn't installed, follow the `Workbench for Zephyr` prompt to install or configure it.
 
 ## Create the Mosquitto Docker Compose project
 
@@ -372,7 +372,7 @@ Threads:
 	stack size 320, unused 256, usage 64 / 320 (20 %)
 ```
 
-The `*` next to `shell_mqtt` marks the running thread, which is the shell that just executed the command. Note that responses larger than the MQTT buffer are split across multiple publishes. `mosquitto_sub -v` reassembles them sequentially under the `1a2b3c/sh/tx` topic prefix.
+The `*` next to `shell_mqtt` marks the running thread, which is the shell that executed the command. Note that responses larger than the MQTT buffer are split across multiple publishes. `mosquitto_sub -v` reassembles them sequentially under the `1a2b3c/sh/tx` topic prefix.
 
 Example output for `net iface` on the FRDM-MCXN947, truncated to the IPv4 section:
 
@@ -392,7 +392,6 @@ IPv4 gateway : 192.168.1.1
 DHCPv4 state      : bound
 DHCPv4 server     : 192.168.1.1
 ```
-
 Example output for `net ping 192.168.1.1` (board pinging its gateway):
 
 ```output
@@ -402,7 +401,7 @@ Example output for `net ping 192.168.1.1` (board pinging its gateway):
 28 bytes from 192.168.1.1 to 192.168.1.41: icmp_seq=3 ttl=64 time=0 ms
 ```
 
-Replace `192.168.1.1` with the gateway address shown by `net iface`. The board sends three ICMP echo requests by default.
+To run `net ping`, replace `192.168.1.1` with the gateway address shown by `net iface`. The board sends three ICMP echo requests by default.
 
 {{% notice Note %}}
 The MQTT shell backend executes a command after it receives a newline character. The `printf 'kernel version\n' | ... mosquitto_pub -s` form sends the command with the required newline.

content/learning-paths/embedded-and-microcontrollers/zephyr_shell/4_uart_shell.md

@@ -157,6 +157,8 @@ kernel uptime
 kernel thread list
 ```
 
+The output is similar to:
+
 ![Zephyr UART shell terminal output showing the kernel version, kernel uptime, and kernel thread list commands and their responses at the uart:~$ prompt#center](images/uart_shell_output.webp "Zephyr UART shell command output")
 
 The `*` next to `shell_uart` in the thread list marks the currently running thread, which is the shell that executed the command.

content/learning-paths/embedded-and-microcontrollers/zephyr_shell/_index.md

@@ -15,7 +15,7 @@ learning_objectives:
 prerequisites:
     - Basic familiarity with embedded C programming
     - Visual Studio Code with the Workbench for Zephyr extension installed and configured
-    - Docker Desktop, Docker Engine, or another Docker-compatible runtime installed on your host computer (for the MQTT shell example only)
+    - Docker Desktop, Docker Engine, or another Docker-compatible runtime installed on your host computer (for the MQTT shell example, if you're not installing Mosquitto on host)
     - A Zephyr-supported Arm Cortex-M board (for example, NXP FRDM-MCXN947)
 
 author: