Enhance documentation for building and testing KleidiCV on macOS by clarifying steps and expected outputs

Author: madeline-underwood

content/learning-paths/laptops-and-desktops/kleidicv-on-mac/build-1.md

@@ -15,7 +15,13 @@ You can use KleidiCV as a standalone image processing library or integrate it wi
 
 ## Set up your environment 
 
-To follow this example you'll need a MacBook Pro with an Apple Silicon M4 processor. To check your operating system version, select the **Apple menu ()** in the top-left corner of your screen and choose **About This Mac**. Alternatively, open a terminal and run:
+To follow this example you'll need a MacBook Pro with an Apple Silicon M4 processor. 
+
+To check your operating system version, follow these steps:
+
+- Select the **Apple menu ()** in the top-left corner of your screen
+- Select **About This Mac**
+- Alternatively, open a terminal and run:
 
 ```console
 sw_vers
@@ -27,8 +33,9 @@ ProductName:		macOS
 ProductVersion:		15.5
 BuildVersion:		24F74
 ```
+### Install CMake
 
-You also need CMake. If CMake is not already installed on your host machine, you can install it using Homebrew:
+If CMake is not already installed on your host machine, you can install it using Homebrew:
 
 ```bash
 brew install cmake
@@ -115,7 +122,7 @@ export WORKSPACE=$HOME/kleidi
 
 To set up KleidiCV and OpenCV, first download the source code from GitLab. 
 
-In your $WORKSPACE directory, clone KleidiCV using the v0.6.0 release tag.
+In your $WORKSPACE directory, clone KleidiCV using the v0.6.0 release tag:
 
 ```bash
 cd $WORKSPACE
@@ -138,10 +145,11 @@ patch -p1 < ../kleidicv/adapters/opencv/opencv-4.12.patch
 patch -p1 < ../kleidicv/adapters/opencv/extra_benchmarks/opencv-4.12.patch
 ```
 
-
 ## Build options
 
-KleidiCV provides several CMake options to control which instruction sets and features are enabled during the build. Here are the most important options for Arm systems:
+KleidiCV provides several CMake options to control which instruction sets and features are enabled during the build. 
+
+Here are the most important options for Arm systems:
 
 - **KLEIDICV_ENABLE_SVE2**  
   Enables Scalable Vector Extension 2 (SVE2) code paths. This is on by default for popular compilers that support SVE2, but off otherwise.
@@ -191,7 +199,7 @@ ls ./build-kleidicv-benchmark-SME/benchmark/kleidicv-benchmark
 ```
 ## Build the OpenCV with KleidiCV
 
-The following command can be used to build OpenCV with KleidiCV:
+You can use the following command to build OpenCV with KleidiCV:
 
 ```bash
 cmake -S $WORKSPACE/opencv \

content/learning-paths/laptops-and-desktops/kleidicv-on-mac/run-test-2.md

@@ -86,7 +86,7 @@ The command for running the test is as follows:
   --gtest_repeat=3
 ```
 
-The output will appear as follows:
+The expected output is:
 
 ```output
 [ERROR:[email protected]] global persistence.cpp:566 open Can't open file: 'imgproc.xml' in read mode
@@ -428,8 +428,7 @@ kleidicv API:: kleidicv_remap_f32_u8_resolver,NEON backend.
 kleidicv API:: kleidicv_remap_f32_u16_resolver,NEON backend.
 kleidicv API:: kleidicv_warp_perspective_stripe_u8_resolver,NEON backend.
 ```
-
-The output is truncated, but you will see performance metrics for all operations at 1280x720 resolution.
+The output is truncated for brevity, but you will see detailed performance metrics for each operation at 1280x720 resolution. Look for lines showing the operation name, sample count, mean and median times, and standard deviation. These results help you compare the performance of different backends and confirm that SME or NEON acceleration is active.
 
 ## Use lldb to check the SME backend implementation
 
@@ -452,10 +451,35 @@ lldb ./build-kleidicv-benchmark-SME/test/api/kleidicv-api-test
 ```
 
 The interactions with the `(lldb)` command line are shown below. 
+Start by entering the following commands in the `lldb` debugger:
+
+```console
+target create "./build-kleidicv-benchmark-SME/test/api/kleidicv-api-test"
+b saturating_add_abs_with_threshold
+run
+```
+
+When the program stops at your breakpoint, enter:
+
+```console
+bt
+```
 
-Enter the `target` command followed by the `b` command for the breakpoint, and the `run` command. When the breakpoint is reached enter the `bt` command to see the stack trace followed by the `disassemble` command to display the assembly instructions in SME streaming mode. Use the `quit` command at the end to exit `lldb`. 
+This command displays the stack trace, showing how the function was called.
+
+Next, to view the assembly instructions (including SME streaming mode), enter:
+
+```console
+disassemble --frame
+```
+
+After you finish inspecting the output, exit `lldb` by typing:
+
+```console
+quit
+```
 
-Some of the paths will be different for you, but you can enter the commands and follow the output. 
+Note: Your file paths may differ, but the sequence of commands remains the same. Enter each command as shown and review the output at each step.
 
 ```console
 target create "./build-kleidicv-benchmark-SME/test/api/kleidicv-api-test"