typos

Author: agarnung

_posts/2025-01-19-DOPvsOOP.md

@@ -173,7 +173,7 @@ OOP (Good Order by DOP) Execution time: 0.00575244 seconds
 
 Again a better result. This indicates that we are not thinking nonsense, but we can go even further, and this is just transfering to code naive knowledge about CPU architecture...
 
-> Note: With the command ```$ lscpu``` you can view the information about my CPU, to see the size in bytes that the CPU queries in each cycle, in order to know how to maximize the efficiency of my structure to avoid unnecessary gaps and perform operations in the fewest number of cycles (L1 and L2 cache sizes, 64-bit data bus size, etc.).
+> Note: With the command ```$ lscpu``` you can view the information about your CPU, to see the size in bytes that the CPU queries in each cycle, in order to know how to maximize the efficiency of my structure to avoid unnecessary gaps and perform operations in the fewest number of cycles (L1 and L2 cache sizes, 64-bit data bus size, etc.).
 
 ### ```Entity_OOP_GoodWithFooPadding```
 Now we manually add the necessary padding to align the data with the 64-bit boundaries of our CPU's memory architecture:
@@ -251,8 +251,6 @@ Below are the graph results after running the test many (1000) times and analyzi
 
 Mostly, the results align with what was experienced before; careful structuring of variables in memory enhances performance on both small and large scales, even with the optimizations that modern compilers may add.
 
-**GRAPH**
-
 ### Conclusion
 Modern CPUs access memory in blocks (typically 8 bytes or more). If the data is properly aligned in memory, access is faster because it can load and store the data in a single memory cycle. If the data is not properly aligned, the CPU may have to perform more memory accesses, which introduces performance penalties due to the need to correct the alignment at runtime.