more tweaks

Author: anupras-mohapatra-arm

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

@@ -9,7 +9,7 @@ layout: learningpathall
 
 ## Before you begin
 
-In this section, you'll prepare your host computer and identify the hardware needed for two Zephyr shell examples. You'll use the shell over two transports:
+In this section, you'll prepare your host computer and identify the hardware you need for two Zephyr shell examples. You'll use the shell over two transports:
 
 - MQTT over Ethernet
 - UART over a USB serial connection
@@ -60,7 +60,7 @@ Workbench for Zephyr supports multiple debug runners depending on the connected
 
 ## Network requirements for the MQTT shell example
 
-For the MQTT shell example, the board needs access to an MQTT broker over Ethernet. You'll run Mosquitto locally with Docker Compose and use the Mosquitto command-line tools to send and receive shell messages.
+For the MQTT shell example, the board needs access to an MQTT broker over Ethernet. You'll run Mosquitto locally and use the Mosquitto command-line tools to send and receive shell messages.
 
 Make sure that:
 
@@ -72,7 +72,7 @@ Make sure that:
 The example configuration uses IPv4. If your network doesn't provide DHCP, use the static IPv4 settings shown in the next section.
 {{% /notice %}}
 
-## What you've accomplished and what's next
+## What you've learned and what's next
 
 You've now learned which boards to use, which host tools to install, and how the Zephyr shell fits into an embedded application.
 

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

@@ -35,11 +35,11 @@ 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 when the board has an IPv4 address. The backend 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 is IPv4-only and connects automatically when the board has an IPv4 address.
 
 ### UART backend 
 
-Enable the UART backend with `CONFIG_SHELL_BACKEND_SERIAL=y`. The UART backend routes shell commands and responses over the board's UART interface, accessible through a USB serial connection. Use PuTTY on Windows, or `screen` on macOS and Linux. This backend works on a wide range of Zephyr-supported development boards with no additional debug hardware required.
+Enable the UART backend with `CONFIG_SHELL_BACKEND_SERIAL=y`. The UART backend routes shell commands and responses over the board's UART interface, accessible through a USB serial connection. Use PuTTY on Windows, or `screen` on macOS and Linux. This backend works on a wide range of Zephyr-supported development boards without the need for additional debug hardware.
 
 ## What you've accomplished and what's next
 

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

@@ -392,6 +392,8 @@ IPv4 gateway : 192.168.1.1
 DHCPv4 state      : bound
 DHCPv4 server     : 192.168.1.1
 ```
+Next, run `net ping` with the gateway address shown by `net iface`. The board sends three ICMP echo requests by default. 
+
 Example output for `net ping 192.168.1.1` (board pinging its gateway):
 
 ```output
@@ -401,8 +403,6 @@ 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
 ```
 
-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.
 {{% /notice %}}