Merge pull request #3108 from madeline-underwood/cmsis

Update documentation for CMSIS RTX learning path: enhance description…

Author: jasonrandrews

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

@@ -1,6 +1,7 @@
 ---
 title: Build an RTX5 RTOS application with Keil μVision
 
+description: Learn how to create, build, and debug an RTX5 RTOS-based application using Keil μVision with CMSIS-RTOS2 API and Event Recorder for embedded Cortex-M development.
 
 minutes_to_complete: 30
 

content/learning-paths/embedded-and-microcontrollers/cmsis_rtx/build_and_run.md

@@ -23,9 +23,9 @@ Click `Run` (`F5`) to start the application, and after a short time, click `Stop
 
 Observe in the `RTX RTOS` view that the threads have been created. Two other threads, `osRtxIdleThread` and `osRtxTimerThread` will also be created.
 
-![RTX RTOS #center](keil_rtos.png)
+![Screenshot of the RTX RTOS view in Keil μVision showing the list of created threads including thread_1, thread_2, osRtxIdleThread, and osRtxTimerThread with their status and priority information#center](keil_rtos.png "RTX RTOS threads view")
 
-However no output is seen in the `printf viewer`. This is because semihosting is not supported. You will learn how to address this in the next section.
+However no output is seen in the `printf viewer`. This is because semihosting isn't supported. You'll learn how to address this in the next section.
 
 Exit the debug session (`Ctrl+F5`).
 
@@ -48,13 +48,13 @@ You must now create a `Debug Configuration`:
 
 When debugging, use the `OS Data` view to observe RTOS information. Open from the `Window` > `Show View` menu. Use the pull down to select different categories.
 
-![OS Data #center](os_data.png)
+![Screenshot of the OS Data view showing RTOS thread information including task names, states, and stack usage#center](os_data.png "OS Data view with thread details")
 
 For thread aware debug, right-click on the debug connection in the `Debug Control` view, and select `Display threads`.
 
-![Debug Control #center](debug_control.png)
+![Screenshot of the Debug Control view with the context menu showing the Display threads option for thread-aware debugging#center](debug_control.png "Debug Control view with thread display option")
 
-You will see the printf() output in `Target Console` pane.
+You'll see the printf() output in `Target Console` pane.
 ```
 hello from thread 1
 hello from thread 2

content/learning-paths/embedded-and-microcontrollers/cmsis_rtx/create.md

@@ -11,7 +11,7 @@ This learning path will introduce the steps to create a basic RTX based RTOS app
 
 For more information on the latest update, see the [CMSIS v6 is here](https://community.arm.com/arm-community-blogs/b/tools-software-ides-blog/posts/cmsis-v6-is-here) blog.
 
-You will use [Keil MDK](/install-guides/mdk) through this Learning Path. If you are using [Arm Development Studio](/install-guides/armds) refer to the appropriate comments.
+You'll use [Keil MDK](/install-guides/mdk) through this Learning Path. If you're using [Arm Development Studio](/install-guides/armds) refer to the appropriate comments.
 
 {{% notice  Note%}}
 If using `Arm Keil Studio for Visual Studio Code` please go to [Build an RTX5 RTOS application with Keil Studio (VS Code)](/learning-paths/embedded-and-microcontrollers/cmsis_rtx_vs/).
@@ -47,15 +47,15 @@ Then select `CMSIS C/C++ Project`, using `Arm Compiler for Embedded 6`.
 
 ### Select device
 
-You will then be prompted to `Select Device` for your project. A list of all devices with their CMSIS-Packs installed will be shown.
+You'll then be prompted to `Select Device` for your project. A list of all devices with their CMSIS-Packs installed will be shown.
 
 For this example, select `Arm` > `Arm Cortex-M4` > `ARMCM4`. Click `OK`.
 
 ## Manage Run-Time Environment
 
-You will first be presented with the `Manage Run-Time Environment` dialog, which allows you to specify the CMSIS software components that will be used in the project.
+You'll first be presented with the `Manage Run-Time Environment` dialog, which allows you to specify the CMSIS software components that will be used in the project.
 
-Under `CMSIS`, select `CORE`, as well as `RTOS2 (API)` > `Keil RTX5`, in `Source` form. You will also need to select `CMSIS` > `OS Tick (API)` > `SysTick`.
+Under `CMSIS`, select `CORE`, as well as `RTOS2 (API)` > `Keil RTX5`, in `Source` form. You'll also need to select `CMSIS` > `OS Tick (API)` > `SysTick`.
 
 Under `Device`, select `Startup` (`C Startup`).
 

content/learning-paths/embedded-and-microcontrollers/cmsis_rtx/eventrecorder.md

@@ -9,7 +9,7 @@ layout: "learningpathall"
 ---
 We saw in the last section that Keil MDK does not support semihosting.
 
-[CMSIS-View](https://arm-software.github.io/CMSIS_6/latest/View/index.html) provides [Event Recorder](https://arm-software.github.io/CMSIS-View/latest/evr.html) which can be used instead for the printf functionality. It is supported for both FVPs and real hardware.
+[CMSIS-View](https://arm-software.github.io/CMSIS_6/latest/View/index.html) provides [Event Recorder](https://arm-software.github.io/CMSIS-View/latest/evr.html) which can be used instead for the printf functionality. It's supported for both FVPs and real hardware.
 
 {{% notice  Arm Development Studio%}}
 Event Recorder and Component Viewer are not supported. This section can be ignored.
@@ -19,7 +19,7 @@ Event Recorder and Component Viewer are not supported. This section can be ignor
 
 Open the `Manage run-time environment` dialog, and enable `CMSIS-View` > `Event Recorder` (`DAP` variant).
 
-Enable `CMSIS-Compiler` > `STDOUT (API)`, and set to `Event recorder`. You will also need to enable `CMSIS-Compiler` > `Core`.
+Enable `CMSIS-Compiler` > `STDOUT (API)`, and set to `Event recorder`. You'll also need to enable `CMSIS-Compiler` > `Core`.
 
 Click `OK` to save.
 
@@ -87,13 +87,13 @@ Note that the RTX source contains many Event Recorder annotations.
 
 For ease of readability, click the `Filter` icon to hide these events. Ensure `STDIO` events are enabled.
 
-![Event Viewer filter #center](ev_filter.png)
+![Screenshot of the Event Viewer filter dialog showing event categories with STDIO enabled and RTX events disabled for easier readability#center](ev_filter.png "Event Viewer filter settings")
 
 Observe that printf output is in the form of the ASCII codes of the text output.
 
-![Event Viewer #center](ev_raw.png)
+![Screenshot of the Event Viewer showing STDIO events with printf output displayed as ASCII codes#center](ev_raw.png "Event Viewer showing ASCII output")
 
-For this view it is better to use [EventRecorder Data](https://www.keil.com/pack/doc/compiler/EventRecorder/html/group__EventRecorder__Data.html) rather than printf statements.
+For this view it's better to use [EventRecorder Data](https://www.keil.com/pack/doc/compiler/EventRecorder/html/group__EventRecorder__Data.html) rather than printf statements.
 
 
 ## EventRecorder Data
@@ -125,7 +125,7 @@ Use the filter to hide `STDIO` events, which shall remove the printf strings. En
 
 The thread number is output as the first `Value`:
 
-![Event Viewer #center](ev_data.png)
+![Screenshot of the Event Viewer displaying EventRecorder Data with thread numbers shown in the Value column#center](ev_data.png "Event Viewer showing thread data values")
 
 ## Component Viewer
 
@@ -156,8 +156,8 @@ Click `Debug` (`Ctrl+F5`), then `Run` (`F5`) to start the application.
 
 This file has now defined event `0x0`, and this is reflected in the filter view:
 
-![Event Viewer filter #center](ev_component.png)
+![Screenshot of the Event Viewer filter showing the custom EVR_Demo component with event 0x0 defined from the SCVD file#center](ev_component.png "Event Viewer filter with custom component")
 
 These events are now processed into meaningful messages in the Event Recorder viewer:
 
-![Event Viewer #center](ev_cv.png)
+![Screenshot of the Event Viewer displaying decoded messages from the Component Viewer showing goodbye from thread messages instead of raw data#center](ev_cv.png "Event Viewer with Component Viewer decoded messages")