diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index 3564cf1..cb8a321 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -118,19 +118,21 @@ At this point a new set of requirements is built and a new release starts.
 [//]: # (TODO - Adicionar que as mudanças no Colab quebravam todos os plugins.)
 [//]: # (https://www.linux.com/blog/learn/chapter/dev-ops/2017/7/devops-fundamentals-part-3-continuous-delivery-and-deployment)
 
-The SPB portal is composed of a set of FOSS systems. All of them have their own
-automated test suite. So, we encouraged the teams to keep unit tests coverage
-high for each system. We implemented the systems integration using a plugin
-architecture and wrote integration tests to check if they were working
-properly. The plugin architecture made the PSPB’s components decoupled. That
-allowed us to be confident that changes on one system would not affect others.
-This characteristic allowed the test execution of only the component with
-changes instead of the entire system.
-
-Our CD’s first step was to execute each system’s automated test suite. If any
-error was found, the pipeline stopped and the developers were notified. Only
-after all tests passed we move to preparing the release.  Preparing a new
-release
+Each one of the Portal's software components had their own test suite which
+the development teams were required to maintain and expand if possible. The 
+integration of all these software was based on a plugin architecture and, 
+again, each plugin with its test suite to ensure this level of the platform
+stability.
+
+This two-level testing approach provided us the necessary speed and
+the trust that each software and the whole platform stability. By first running
+the software specific test suite we checked its stability and, if there was any
+errors, the developers were warned and the execution of the plugins test suite
+was not started.
+
+Only after all tests passed we move to the next step down the pipeline.
+
+### Preparing a new release
 
 Our release system was divided into two perspectives: the application and the
 PSPB. The application tag refers to the specific feature or bug fix and is a
--
libgit2 0.21.2