diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index b44fc29..a54097f 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -155,7 +155,7 @@ in partnership with a University is doomed to fail. Our team was not from a
 typical company, consisting mainly of undergraduate students coordinated by two
 professors. At the first year, we had a group composed of 24 undergraduate
 students, one designer, and two senior developers. In 2015, our team grew to 36
-students, two designers, eight senior developers. At the end, due to budget
+students, two designers, eight senior developers. In the end, due to budget
 constraint, we had 20 students, one designer, and two developers. On the
 government side, the SPB portal evolution was the first software development
 collaboration between university and government experienced by the MP agents
@@ -193,11 +193,11 @@ project, we became active participants in the deploy operations.
 
 ![Deployment Pipeline](figures/pipeline_3.png)
 
-Figure 1 represents our CD pipeline. A new feature might require changes on
+Figure 1 represents our CD pipeline. A new feature might require changes to
 more than one SPB integrated software project. Notice that each one of them
 could be modified independently. The pipeline started when new code arrived. As
 it went through each step, it was tested and improved until it finally reached
-the production environment. At this point we would restart the pipeline to
+the production environment. At this point, we would restart the pipeline to
 release more new code.
 
 ### Automated Tests
@@ -242,7 +242,7 @@ repository.
 We decided to create own packages for each software component for the following
 five reasons:
 
-1. Not all software was packaged by the community and those that existed were outdated;
+1. The community packaged not all software, and those that existed were outdated;
 1. Packaging makes it easy to manage the software on a given distribution;
 1. Packaging simplifies the deployment;
 1. Packaging follows the distribution's best practices and,
@@ -280,7 +280,7 @@ we moved forward.
 ### Production Environment Deployment
 
 When the MP agents finished the VE check, we could finally begin the deployment
-in the PE. For this we also used our configuration management tool, the same
+in the PE. For this, we also used our configuration management tool, the same
 scripts and package versions as in the VE. After the deploy was completed, both
 VE and PE were running identical software. Here was the point where new
 features and bug fixes were finally available to the end users.
--
libgit2 0.21.2