diff --git a/_posts/2024/2024-02-06-about-caching-in-eo.md b/_posts/2024/2024-02-06-about-caching-in-eo.md
index e6b7638..d5fa140 100644
--- a/_posts/2024/2024-02-06-about-caching-in-eo.md
+++ b/_posts/2024/2024-02-06-about-caching-in-eo.md
@@ -34,7 +34,9 @@ To speed up the assembly of compiled languages, ccache and sccache are used.
Let's look at the compilation scheme using C++ as an example,
to imagine the build process in compiled languages:
-
+
+ 
+
1) First, preprocessor gets the input files. Input files are code files and header files.
The preprocessor removes comments from the code and converts the code into in accordance
@@ -81,9 +83,9 @@ which consist of `phases`. `Phases` in turn consist of sets of `goals`.
`Maven` has default `phases` and `goals` which build any projects:
-
-
-
+
+ 
+
In `Maven` all phases and goals are executed strictly in order, linearly.
But in `Maven` there is no build-time caching as such.
@@ -130,7 +132,9 @@ which contains the goals necessary for working with EO code.
As was written above, the assembly of projects in `Maven` occurs in a certain order of phases.
In the diagram you can see the main phases and their goals for the EO version of the compiler (specify version):
-
+
+ 
+
In [Picture 3](/images/EO.svg) the goals from the `eo-maven-plugin`
are highlighted in green.
@@ -140,7 +144,10 @@ But the actual work with EO code takes place in `AssembleMojo`.
`AssembleMojo` is the goal consisting of other goals that work with the EO file
[Picture 4](/images/AssembleMojo.svg).
-
+
+
+ 
+
Each goal in `AssembleMojo` is a specific compilation step for EO code, and we need to use
caching at each step to speed up the assembly of the EO program.