diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index 06d82d7..7a0a6eb 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -143,11 +143,13 @@ 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)
-write the script for the specific environment (RPM), (2) build the package, and
-(3) upload it to a package repository. We chose to package our components for
-several reasons: 
+The platform is running on the CentOS 7 GNU/Linux distribution.
+Basically, packaging a software for that distribution has three steps: write 
+the script for the specific environment (RPM); build the package; and upload
+it to a package repository.
+
+We chose to create our own packages for each software component for several
+reasons: 
 * Not all software was packaged by the community;
 * And those that existed were outdated;
 * Packaging makes it easy to manage the software on a given distribution;
@@ -157,11 +159,12 @@ several reasons:
 
 After creating a new tag for one component, the DevOps team was notified and
 packaging process began. In the normal case, the three packaging steps
-aforementioned are fully automated by a set of scripts. However, if the team
-reports to DevOps any eventual dependency change, the first step has to be
-manual. For instance, one system could start requiring another system to be
-initialized and that made necessary for someone to manually update the package
-script.
+aforementioned were fully automated by a set of scripts.
+
+However, if the developers reported to DevOps any eventual dependency change, 
+the first packaging step had to be manual. For instance, suppose one system 
+starts requiring another system to be initialized first. That required the 
+DevOps to manually update the packaging script respective to these systems.
 
 After all these scripts have run successfully, the new packages would be ready
 to use by our subsequent deployment scripts.
--
libgit2 0.21.2