ArmDeveloperEcosystem · jasonrandrews · Feb 27, 2025 · Feb 26, 2025 · Feb 26, 2025
diff --git a/...t/learning-paths/laptops-and-desktops/windowsperf-vs-extension/SPE-settings.png b/...t/learning-paths/laptops-and-desktops/windowsperf-vs-extension/SPE-settings.png
diff --git a/...earning-paths/laptops-and-desktops/windowsperf-vs-extension/counting-feature.md b/...earning-paths/laptops-and-desktops/windowsperf-vs-extension/counting-feature.md
@@ -39,8 +39,8 @@ Check the `Timeline` check box create a timeline view.  Choose the number of ite
 To start the counting process click on the `Start` button. 
 
 If you’ve set a timeout, the process will run for the specified duration. Otherwise, you have the flexibility to end the counting manually using the `Stop` button.
-     
-For the current code example, you will see the counted events in the `Counting Output` located in the lower section of the dialog. 
+
+For the current code example, select `cpu_cycles` in the Event List and select `dache` in the Metrics List then you will see the counted events in the `Counting Output` located in the lower section of the dialog. 
 
 ![Start Counting](./start-counting.png)
 

diff --git a/content/learning-paths/laptops-and-desktops/windowsperf-vs-extension/debug.png b/content/learning-paths/laptops-and-desktops/windowsperf-vs-extension/debug.png
diff --git a/content/learning-paths/laptops-and-desktops/windowsperf-vs-extension/host-data.png b/content/learning-paths/laptops-and-desktops/windowsperf-vs-extension/host-data.png
diff --git a/content/learning-paths/laptops-and-desktops/windowsperf-vs-extension/release.png b/content/learning-paths/laptops-and-desktops/windowsperf-vs-extension/release.png
diff --git a/...rning-paths/laptops-and-desktops/windowsperf-vs-extension/sampling-overview.png b/...rning-paths/laptops-and-desktops/windowsperf-vs-extension/sampling-overview.png
diff --git a/...arning-paths/laptops-and-desktops/windowsperf-vs-extension/sampling-results.png b/...arning-paths/laptops-and-desktops/windowsperf-vs-extension/sampling-results.png
diff --git a/...rning-paths/laptops-and-desktops/windowsperf-vs-extension/sampling-settings.png b/...rning-paths/laptops-and-desktops/windowsperf-vs-extension/sampling-settings.png
diff --git a/.../learning-paths/laptops-and-desktops/windowsperf-vs-extension/settings-page.png b/.../learning-paths/laptops-and-desktops/windowsperf-vs-extension/settings-page.png
diff --git a/...ent/learning-paths/laptops-and-desktops/windowsperf-vs-extension/spe-feature.md b/...ent/learning-paths/laptops-and-desktops/windowsperf-vs-extension/spe-feature.md
@@ -11,6 +11,10 @@ layout: learningpathall
 
 The SPE feature is a subset of the Sampling feature that we just discussed.
 
+{{% notice Note %}}
+This section requires hardware that supports the SPE specification to function properly.
+{{% /notice %}}
+
 ## What is The Arm Statistical Profiling Extension (SPE)
 
 The Arm Statistical Profiling Extension (SPE) is an architectural feature designed for enhanced instruction execution profiling within Arm CPUs. This feature has been available since the introduction of the Neoverse N1 CPU platform in 2019, along with performance monitor units (PMUs) generally available in Arm CPUs.

diff --git a/...nt/learning-paths/laptops-and-desktops/windowsperf-vs-extension/spe-results.png b/...nt/learning-paths/laptops-and-desktops/windowsperf-vs-extension/spe-results.png
diff --git a/...learning-paths/laptops-and-desktops/windowsperf-vs-extension/start-counting.png b/...learning-paths/laptops-and-desktops/windowsperf-vs-extension/start-counting.png