Performance-and-memory-optimization.md

@@ -44,11 +44,13 @@ At the beginning seemed the vertices optimization will play an important role in
 
 This adds a new variable (the size of the structure, number of atoms) to determine the segments number of the atoms geometry.
 
-But later once using the *BufferGeometry* versions of the primitives I realized the vertices optimizations is hardly worth it. Some figures (testing on the supercell - 1300 atoms):
+But later once using the *BufferGeometry* versions of the primitives I realized the **vertices optimization is hardly worth it**. Some figures (testing on the supercell - 1300 atoms):
 
-Fixed 24 segments per atom: 150M (memory footprint) / 42M (javascript live memory) 
-Optimized (above expression): 100-120M (memory footprint) / 42M (javascript live memory) 
-Fixed 18 segments per atom: 115-120M (memory footprint) / 42M (javascript live memory)
+>  Fixed 24 segments per atom: 150M (memory footprint) / 42M (javascript live memory) 
+
+>  Optimized (above expression): 100-120M (memory footprint) / 42M (javascript live memory) 
+
+>  Fixed 18 segments per atom (**current implementation**): 115-120M (memory footprint) / 42M (javascript live memory)
 
 
 ### Reusing object attributes (geometry, materials, etc) for atoms (species prototype atom for each species) and bonds