updates

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/false-sharing-arm-spe/how-to-3.md

@@ -9,7 +9,7 @@ layout: learningpathall
 ## Example code
 
 {{% notice Learning Goal%}}
-The example code in this section demonstrates how false sharing affects performance by comparing two multithreaded programs — one with cache-aligned data structures and one without. You’ll compile and run both versions, observe the runtime difference, and learn how memory layout affects cache behavior. This sets the stage for analyzing performance with Perf C2C in the next section.
+The example code in this section demonstrates how false sharing affects performance by comparing two multithreaded programs; one with cache-aligned data structures, and one without. You’ll compile and run both versions, observe the runtime difference, and learn how memory layout affects cache behavior. This sets the stage for analyzing performance with `perf c2c` in the next section.
 {{% /notice %}}
 
 Use a text editor to copy and paste the C example code below into a file named `false_sharing_example.c`

content/learning-paths/servers-and-cloud-computing/false-sharing-arm-spe/how-to-4.md

@@ -9,10 +9,10 @@ layout: learningpathall
 ## Compare Performance with perf stat
 
 {{% notice Learning goal %}}
-In this section, you’ll learn how to use Linux Perf tools and Arm SPE to identify performance bottlenecks in multithreaded applications. You’ll compare aligned and unaligned workloads, detect cache-related slowdowns like false sharing, and trace memory contention down to the source code using Perf C2C.
+In this section, you’ll learn how to use Linux Perf tools and Arm SPE to identify performance bottlenecks in multithreaded applications. You’ll compare aligned and unaligned workloads, detect cache-related slowdowns such as false sharing, and trace memory contention down to the source code using Perf C2C.
 {{% /notice %}}
 
-A straightforward method to observe the performance characteristics of both binaries would be to use the `perf stat` command. 
+A simple way to observe the performance difference of both binaries is to use the `perf stat` command. 
 
 For example, run the false sharing version using: