Merge pull request #2601 from DougAnsonAustinTX/zephyr_LP_techreview

Zephyr LP Techreview - minor LP updates

Author: jasonrandrews

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

@@ -72,7 +72,7 @@ When the installation completes, select **Verify Host Tools** to check the versi
 
 Next, download and configure the toolchain by selecting **Import Toolchain** in the Workbench for Zephyr panel. Select the toolchain family (*Zephyr SDK*) and configure the SDK Type by choosing *Minimal* for basic functionality.
 
-Select your desired version (such as v0.17.0 or v0.17.3) and choose the target architectures. For this Learning Path, you only need to select *arm*. 
+Select your desired version (such as v0.17.4... your version may vary a little) and choose the target architectures. For this Learning Path, you only need to select *arm*. 
 
 Specify the parent directory for SDK installation and select **Import** to download and install the SDK.
 
@@ -85,14 +85,16 @@ Zephyr uses a Git-based workspace manager called West to organize its source cod
 
 In the Workbench for Zephyr panel, select **Initialize Workspace** to set up your project environment. Configure the workspace settings by selecting "Minimal from template" for the source location and using the default path `https://github.com/zephyrproject-rtos/zephyr`. 
 
-Choose a target-specific template (such as STM32 or NXP) and select your Zephyr version (such as v3.7.0 or v4.1.0). Specify the directory for your workspace, keeping in mind that initialization takes approximately 10 minutes to complete. 
+Choose a target-specific template (such as STM32 or NXP) and select your Zephyr version (such as v4.3.0... your version may vary a bit). Specify the directory for your workspace, keeping in mind that initialization takes approximately 10 minutes to complete. 
 
 Select **Import** to create and update the workspace.
 
 ![Initialize West Workspace #center](images/initialize_workspace.png)
 
 {{% notice Note %}}
-The workspace initialization downloads the Zephyr source code and dependencies. This process may take several minutes depending on your internet connection speed.
+The workspace initialization downloads the Zephyr source code and dependencies. This process may take several minutes depending on your internet connection speed. 
+
+Additionally, the selected revision you select may be a bit different from the one shown above.
 {{% /notice %}}
 
 ### Verify setup

content/learning-paths/embedded-and-microcontrollers/zephyr_vsworkbench/3_debug.md

@@ -31,7 +31,7 @@ The following steps show how to generate and review memory reports:
 
 ![Memory Analysis](images/memory_analysis.png)
 
-The RAM Report displays detailed memory allocation information:
+The RAM Report displays detailed memory allocation information and should look like this:
 
 ```
 Path                                                                                             Size       %  Address    Section
@@ -172,7 +172,7 @@ Workbench for Zephyr will automatically detect these tools when they are install
 
 ### Install Runners Utilities
 
-To install debug tools for your specific board, go to **Host Tools > Install Debug Tools** in the Zephyr Workbench panel and select the tools applicable to your board.
+To install debug tools for your specific board, go to **Host Tools > Install Debug Tools** in the Zephyr Workbench panel and select the tools applicable to your board. You may need to press the refresh symbol to get the latest installation state for the selected/installed runners:
 
 ![Debug Runners](images/install_runners.png)
 
@@ -205,6 +205,10 @@ You can start debugging from Workbench for Zephyr by selecting **Debug**, or fro
 
 ![Debug Application](images/debug_app.png)
 
+{{% notice Note %}}
+Depending on whether you are running on Windows or a Mac, the selection of the serial monitor port may be different from what is shown above. The above picture shows a serial port from the development board being connected to a Mac. 
+{{% /notice %}}
+
 ### Debug toolbar controls
 
 The debug toolbar provides the following controls for stepping through your code: