Update section headings to enhance clarity in memory subsystem documentation

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/memory-subsystem/multicore-bandwidth.md

@@ -142,7 +142,7 @@ On Graviton4, the knee appears between 30 and 20 injected NOPs, where latency ju
 
 Graviton4 has higher idle DRAM latency than Graviton2 (approximately 115 ns vs 96 ns), which is consistent with the `latency-sweep` results. Despite this higher baseline latency, Graviton4's knee occurs at a much higher absolute bandwidth (around 340 GB/s vs 126 GB/s), giving significantly more headroom for bandwidth-sensitive workloads before latency degrades.
 
-## What you've accomplished and what's next
+## What you've learned and what's next
 
 In this section you:
 - Measured peak system bandwidth across multiple traffic patterns with `peak-bandwidth`

content/learning-paths/servers-and-cloud-computing/memory-subsystem/pointer-chase-latency.md

@@ -117,7 +117,7 @@ You can view the full list of available benchmarks and their keywords with:
 asct list
 ```
 
-## What you've accomplished and what's next
+## What you've learned and what's next
 
 In this section you:
 - Ran the ASCT `latency-sweep` benchmark to measure pointer-chase latency across the full cache hierarchy and DRAM

content/learning-paths/servers-and-cloud-computing/memory-subsystem/streaming-bandwidth.md

@@ -87,11 +87,11 @@ To run all bandwidth benchmarks at once:
 sudo asct run bandwidth
 ```
 
-## What you've accomplished and what's next
+## What you've learned and what's next
 
 In this section you:
 - Ran the ASCT `bandwidth-sweep` benchmark to measure single-core streaming bandwidth at each cache level
 - Observed bandwidth plateaus corresponding to L1, L2, LLC, and DRAM
 - Learned about additional ASCT benchmarks for peak and cross-NUMA bandwidth
 
-The next section extends this to multi-core bandwidth, showing how shared resources like L3 and DRAM behave under contention.
+The next section extends this to multi-core bandwidth, showing how shared resources like L3 and DRAM behave under contention.

content/learning-paths/servers-and-cloud-computing/memory-subsystem/system-overview.md

@@ -359,11 +359,11 @@ Below is a summary of each system.
 | L3 (shared) | 32 MB | 36 MB |
 | DRAM type | DDR4 | DDR5 |
 
-## What you've accomplished and what's next
+## What you've learned and what's next
 
 In this section you:
 - Identified the CPU model, core count, and NUMA topology of your test systems
 - Explored the cache hierarchy and cluster layout using `lscpu`, `hwloc`, and `sysfs`
 - Built a reference table of system properties for later comparison
 
-The next section dives deeper into the cache hierarchy and explains what each level does and why the architectural choices matter for performance.
+The next section dives deeper into the cache hierarchy and explains what each level does and why the architectural choices matter for performance.