diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index 5d76e78..1ad5638 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -101,7 +101,7 @@ the worst political crisis after the re-democratization in Brazil.
 
 ![Deployment Pipeline](figures/pipeCD.png)
 
-The figure represents our CD pipeline. The pipeline started when new code arrived.
+The Figure 1 represents our CD pipeline. 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 got back to the first stage to release
 more new code.
@@ -218,7 +218,7 @@ constantly updated the VE based on their feedback. This made our relation
 strong and in moments that needed quick action they would rather give us access
 to production.
 
-### Shared Responsibility
+### Shared responsibility
 
 Before the adoption of the CD, the developers team could not track what happened to the code
 after its delivery, since government technicians were the only responsibles
@@ -236,7 +236,7 @@ order to speed up the process of making available, in the production environment
 new features for the platform.
 
 
-### Synchronicity between Government and Development
+### Synchronicity between government and development
 
 Despite the positive impacts that the CD pipeline brought to the project, its
 implementation was not easy at first. The good performance of the CD pipeline
@@ -255,9 +255,9 @@ scale of work and to request the access to production in time.
 
 Continuous delivery was also a tool that helped to strengthen trust in the
 relationship between developers and government analysts, as well as between the
-latter group and its superiors.Before using CD, analysts had access to the
+latter group and its superiors. Before using CD, analysts had access to the
 features developed only at the end of the release, usually every 4 months.
-However, this periodicity did not meet the requirements of their directors, who
+However, this periodicity did not meet the requirements of their leaders, who
 demanded monthly reports on the progress of the project. With the
 implementation of the CD, intermediate versions became available, allowing
 analysts to perform small validations over time. The constant monitoring of
@@ -310,6 +310,5 @@ between industry and government, specially regarding CD.
 
 1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27.
 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
-1. P. Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", in Proceedings of the 13th International Symposium on Open Collaboration, 2017.
 
 
--
libgit2 0.21.2