diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index 8a2f2c2..6c174eb 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -26,9 +26,9 @@ developing similar software projects were all reduced. The society gained a
 transparent and collaborative mechanism, since anyone can check the government
 expenses on software and contribute to project communities. To achieve these
 goals, rather than writing everything from scratch, we decided to integrate
-several free software tools such as Gitlab (www.gitlab.com), Mailman
-(www.gnu.org/software/mailman), Noosfero (www.noosfero.org), and Colab
-(www.github.com/colab).
+several free software tools such as Noosfero (www.noosfero.org), Gitlab
+(www.gitlab.com), Mailman (www.gnu.org/software/mailman), Mezuro
+(www.mezuro.org), and Colab (www.github.com/colab).
 
 The project started in a presidential election year and everyone involved was
 under pressure to show results. Even with the re-election of the Brazilian
@@ -45,7 +45,9 @@ To achieve the SPB project goals, we had to overcome strong political bias tied
 with complicated technical issues and relatively low budget. Because the
 project is open to the public, the government representatives saw the platform
 as a marketing opportunity and sometimes ignored technical advice in favor of
-political decisions. Furthermore, integrating a number of distinct systems to
+political decisions. Furthermore, integrating a number of distinct systems
+(such as social and collaboration network, Git repository manager, mailing
+list, source code metric evaluation, and a systems integration platform) to
 work seamlessly was not an easy job. We had to learn how each system worked and
 to come up with ideas of how to integrate them as fast as possible, with a team
 of mostly inexperienced developers.
--
libgit2 0.21.2