diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index 71309c9..0742c06 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -134,14 +134,17 @@ Only after all tests passed we move to the next step down the pipeline.
 
 ### Preparing a new release
 
-Our release system was divided into two perspectives: the application and the
-SPB Portal. The application tag refers to the specific feature or bug fix and is a
-monotonically increasing. A new tag on any system yielded a new SPB Portal tag.
+Our release process was divided in two perspectives in terms of git tags: the
+application and the SPB Portal. The application tag refers to the specific
+feature or bug fix and is a monotonically increasing. A new tag on any system
+yielded a new SPB Portal tag.
 
 When all tests passed for a given component, we manually created a new
 application tag for it. As a consequence, that automatically created a new tag
 for the SPB Portal. Notice that we have forks of the original softwares and, as
-consequence, we had different tag values.  Packaging
+consequence, we had different tag values.
+
+### Packaging
 
 The SPB Portal platform is running under the CentOS GNU/Linux distribution.
 Basically, packaging a software for that distribution has three steps: (1)
--
libgit2 0.21.2