diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index c8445e6..0a0914f 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -194,26 +194,23 @@ We had to handle many tensions between development and political issues. Our CD
 pipeline gave us strong mechanisms to tackle most of the problems. As a result
 we came with some benefits from our decision to adopt CD. 
 
-[//]: # (TODO - Melhorar título - Ideias: Response to mistrust)
-
-### Response to tensions
-
-[//]: # (TODO - Decisão do secretario acima do diretor)
+### Response to mistrust
 
 The direct benefit from the CD pipeline was the fast response to the changes
 required by the government. That was vital for the project’s renewal over the
 years. We could manage the tension between the government and the development
 team better. Every meeting with the government leader was delicate and resulted
 on many new requirements, most of them motivated by political needs. For
-example, once it was demanded a completely layout change because one director
-suddenly decided to make a marketing campaign about the portal. They would use
-undelivered requirements as a means to suggest the project’s cancellation. We
-believed that if we took too long to attend their demands, the project would
-end. CD helped us to move fast on deploying to production, even of smaller
-parts of the requirements. That way, we always had something to show on the
-meetings, reducing their eagerness to end the project. For our team, it made
-the developers more confident the project would last a little longer and they
-would not go looking for another jobs.
+example, once it was demanded a completely layout change because another
+government leader suddenly decided to make a marketing campaign about the new
+SPB portal. They would use undelivered requirements as a means to justify the
+lack of financial resource already planned. We believed that if we took too
+long to attend their demands, the project would end. CD helped us to move fast
+on deploying to production, even of smaller parts of the requirements. That
+way, we always had something to show on the meetings, reducing their eagerness
+to end the project. For our team, it made the developers more confident the
+project would last a little longer and they would not go looking for another
+jobs.
 
 ### Build client’s trust
 
@@ -224,6 +221,16 @@ 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
+
+When the government technicians were responsible for deploying the project, the
+developers lost track of what happened after code was delivered. After adopting
+CD, they felt more responsible for what was getting into production. CD
+influenced developers on taking ownership of the project. In the end of the
+project, we noticed that the entire team was working to improve the CD pipeline
+since they wanted to their new features in production.
+
+
 ## Challenges
 
 We successfully built a functional CD pipeline. In the end, we took over the
--
libgit2 0.21.2