typos

Author: agarnung

_posts/2025-01-19-DOPvsOOP.md

@@ -54,7 +54,7 @@ Let us define the number of class instances (entities) we will create to test at
 const int num_entities = 1000000;
 ```
 
-### ```Entity_OOP_Bad````
+### ```Entity_OOP_Bad```
 OOP class with poor attribute ordering, causing padding
 Padding will be used to properly align the attributes in memory.
 The attribute order is random and does not take into account the size of each data type.
@@ -114,7 +114,7 @@ OOP (Bad Order) Execution time: 0.0066837 seconds
 
 ...but that's pretty fast, right? Well... yes, but let's continue going deeper.
 
-### ```Entity_OOP_Good````
+### ```Entity_OOP_Good```
 OOP class with proper attribute ordering, minimizing padding
 Here, padding is reduced by grouping similar types together.
 The attributes are reordered from largest to smallest size (first double, then float, followed by int, char, and finally bool).
@@ -134,8 +134,8 @@ public:
         uint16_t something2; // 2 bytes
         char id;             // 1 byte
         bool active;         // 1 byte
-                                // _______
-                                // 56 bytes total, alignment 8 bytes
+                             // _______
+                             // 56 bytes total, alignment 8 bytes
     };
 
     atributes mAtributes;
@@ -176,7 +176,7 @@ Again a better result. This indicates that we are not thinking nonsense, but we
 > [!NOTE]
 > Con el comando ```$ 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.).
 
-### ```Entity_OOP_GoodWithFooPadding````
+### ```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:
 ```cpp
 class Entity_OOP_GoodWithFooPadding {