diff --git a/opensym2017/content/09-lessons.tex b/opensym2017/content/09-lessons.tex
index ab28333..2c4b0ad 100644
--- a/opensym2017/content/09-lessons.tex
+++ b/opensym2017/content/09-lessons.tex
@@ -1,34 +1,41 @@
 \section{Lessons Learned and Conclusion}
 \label{sec:lessons}
 
-The multidisciplinary of the development teams - mainly composed of software
-engineers and designers - it is necessary for the development of a software
-product that naturally fit the user requirements and consequently achieve a
-high quality. In the context of the SPB project, there was a stakeholders team
-of technicians and managers of the MP, as well as the administrative team of
-the UnB. The interaction with different professionals contributed as a great
-learning opportunity for the students, which had their first professional
-experience during their graduation course. On the other hand, the different
-perceptions of the stakeholders generated a high complex communication and
-management environment. All of this complication generated a lot of overhead
-for the professors because they were responsible for the project management.
-
-At the initial phases of the project, MP imposed the integration of Colab to
-the platform by the claim that it had gamification features, which would
-encourage MP managers to be active on the platform. Since the first moment that
-MP demands it to us, we were totally against the idea because we already knew
-that Colab was a very experimental project and its adoption could dramatically
-increase the project complexity. Even though we provided technical reasons to
-not utilize Colab, MP enforces it to us and we had to manage this problem. As
-explained in section \ref{sec:architecture} we did a massive change in it, and
-at the end of the project we completely rewrite Colab and made it stable. It is
-important to notice that the MP compelled us to accept a technical issue based
-only on political interests, without considering all the money they would spend
-with their decision. At the end of the project, we verified that Colab consumed
-a vast amount of the budget and indeed increased the project complexity. In the
-end of the project and after our analyses on the decisions made by the MP, we
-understand that MP's managers are capable of ignoring technical reasons in
-favor to a political decision.
+%%% Acho que podemos organizar em algo assim, explicitando a lição%%%
+%(Lesson 1 -- Students in real-world project interacting with real customers)
+
+The multidisciplinary of our development team - mainly composed of software
+engineers undergraduate students, senior developers, and designers - makes that
+naturally fit the project requirements and consequently achieve a high quality.
+To collaborate to that, there was a stakeholder team of technicians and
+managers from the Brazilian Government, as well as the management team from the
+UnB. In particular at the being of the project, the different perceptions of
+the Brazilian Government stakeholders generated a high complex communication
+and management environment. Once we were practicing an empirical development
+approach based on FOSS and agile methods, our development team also interacted
+directly with the stakeholders to mitigate several moments of management
+overhead, supporting the UnB professors those were responsible for the project
+management. The interaction with professionals, that have different expertises,
+and the participation in all levels of the software development process
+contributed with a great learning opportunity for the students, which majority
+have their first professional experience.
+
+
+At the initial phases of the project, by political and personal motivation, the
+main stakeholders from the Brazilian government imposed the use of Colab to
+guide the development of the new SPB  platform.  Our team were totally against
+the idea because we already knew that Colab was a very experimental project and
+its adoption could dramatically increase the project complexity.  Even though
+we provided technical reasons to not utilize Colab, MP enforces it to us and we
+had to manage this problem. As explained in section \ref{sec:architecture} we
+did a massive change in it, and at the end of the project we completely rewrite
+Colab and made it stable. It is important to notice that the MP compelled us to
+accept a technical issue based only on political interests, without considering
+all the money they would spend with their decision. At the end of the project,
+we verified that Colab consumed a vast amount of the budget and indeed
+increased the project complexity. In the end of the project and after our
+analyses on the decisions made by the MP, we understand that MP's managers are
+capable of ignoring technical reasons in favor to a political decision.
 
 In the process of deploying the SPB platform in the MP structure, we had to
 interact with the MP's technicians. We did several workshops, training and a
--
libgit2 0.21.2