diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index e54ddcf..cff50a7 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -99,7 +99,7 @@ the worst political crisis after the re-democratization in Brazil.
 
 ## Our Continuous Delivery Pipeline
 
-![Deployment Pipeline](figures/pipeline.png)
+![Deployment Pipeline](figures/pipeCD.png)
 
 The figure represents our CD pipeline: it starts with new code arriving
 which is tested and improved during as necessary as it goes through each one
@@ -256,7 +256,7 @@ In the first three releases, government requirements analysts were validating
 all features to be released only at the end of a delivery cycle which often
 took almost four months. However their superintendents requested monthly
 reports about the project progress and this brought pressure on them which in
-turn put it on us. Making continuous deliveries, we really delivered
+turn put it on us. When we started to make continuous deliveries, we really delivered
 intermediate and candidate releases. Thus, the analysts could have validate a
 small set of features, making possible more accurate feedbacks and better
 reports for regular meetings with their superintendents. As a result, we
diff --git a/ieeeSW/releaseEng3/figures/pipeCD.png b/ieeeSW/releaseEng3/figures/pipeCD.png
new file mode 100644
index 0000000..4fdb1ec
Binary files /dev/null and b/ieeeSW/releaseEng3/figures/pipeCD.png differ
--
libgit2 0.21.2