Remove unneeded changes to end of final lines.

tdunkleArm · tdunkleArm · commit 910132358b40 · 2026-01-06T13:04:21.000-06:00
diff --git a/content/learning-paths/servers-and-cloud-computing/cpp-profile-guided-optimisation/how-to-3.md b/content/learning-paths/servers-and-cloud-computing/cpp-profile-guided-optimisation/how-to-3.md
@@ -101,3 +101,4 @@ sudo perf report --input=perf-division-base
 As the `perf report` graphic below shows, the program spends a significant amount of time in the short loops with no loop unrolling. There is also an expensive `sdiv` operation, and most of the execution time is spent storing the result of the operation.
 
 ![before-pgo](./before-pgo.gif)
+
diff --git a/content/learning-paths/servers-and-cloud-computing/cpp-profile-guided-optimisation/how-to-5.md b/content/learning-paths/servers-and-cloud-computing/cpp-profile-guided-optimisation/how-to-5.md
@@ -118,3 +118,4 @@ jobs:
 ```
 
 To use this workflow, save the YAML content into a file named `pgo_benchmark.yml` (or any other `.yml` name) inside the `.github/workflows/` directory of your GitHub repository. Ensure your `div_bench.cpp` file is present in the repository root. When you push changes to the `main` branch, GitHub Actions will automatically detect this workflow file and execute the defined steps on an Arm-based runner, compiling both versions of the benchmark and running them.
+

Original file line number	Diff line number	Diff line change
`@@ -101,3 +101,4 @@ sudo perf report --input=perf-division-base`
`101`	`101`	As the `perf report` graphic below shows, the program spends a significant amount of time in the short loops with no loop unrolling. There is also an expensive `sdiv` operation, and most of the execution time is spent storing the result of the operation.
`102`	`102`
`103`	`103`	`![before-pgo](./before-pgo.gif)`
	`104`	`+`
Original file line number	Diff line number	Diff line change
`@@ -118,3 +118,4 @@ jobs:`
`118`	`118`	```
`119`	`119`
`120`	`120`	To use this workflow, save the YAML content into a file named `pgo_benchmark.yml` (or any other `.yml` name) inside the `.github/workflows/` directory of your GitHub repository. Ensure your `div_bench.cpp` file is present in the repository root. When you push changes to the `main` branch, GitHub Actions will automatically detect this workflow file and execute the defined steps on an Arm-based runner, compiling both versions of the benchmark and running them.
	`121`	`+`