diff --git a/opensym2017/content/01-introduction.tex b/opensym2017/content/01-introduction.tex
index 3411e64..7699763 100644
--- a/opensym2017/content/01-introduction.tex
+++ b/opensym2017/content/01-introduction.tex
@@ -16,7 +16,7 @@ acquisition of a proprietary solution must be explicitly justified by
 demonstrating that there is no suitable option in the SPB Portal.
 
 Since 2009, however, the SPB Portal was having several technical issues.
-The original codebase was not being developed anymore, and there as a
+The original codebase was not being developed anymore, and there was a
 large amount of technical debt to overcome. The system was a modified
 version of an existing FOSS platform that was not being developed
 anymore, and the portal maintenance was becoming harder and harder.
@@ -32,7 +32,7 @@ this paper, we present an overview of this new generation of the SPB
 Portal.
 
 The project was developed by a team of 3 professors, 6 professionals, 2
-masters students, and approximately 40 undergrad students (not all of
+masters students, and approximately 40 undergraduate students (not all of
 them at the same time, though -- graduations and other events triggered
 changes in the team).
 
diff --git a/opensym2017/content/04-process.tex b/opensym2017/content/04-process.tex
index a25dffb..664e1f5 100644
--- a/opensym2017/content/04-process.tex
+++ b/opensym2017/content/04-process.tex
@@ -1,23 +1,10 @@
 \section{Development Organization and Process}
 \label{sec:process}
 
-The SPB members were composed of a variety of professionals with different
-levels and skills. Most of them were undergraduate students with major in
-software engineering (from 4th semester or upper), hence they could not
-dedicate many hours in the project per week. In their daily lives in the
-project, they had programming and devops tasks. It is important to highlight
-that the students always had the flexibility to negotiate their work hours
-during the semester, because we tried to not cause any damage to their grades.
-
-The development of SPB project required a vast experience and background that
-usually undergraduate students do not have yet, for this reason, some senior
-developer joined to the project to help with hard issues and to transfer
-knowledge to the students. Their main tasks provide solutions for hard
-problems, in other words, they worked as a developer. All the senior lived in a
-different states spread around Brazil, and all the communication was made via
-internet. Finally, those professionals are very skilful and the project could
-not afford a full time work for them, as a result, some of them worked
-partially on the project.
+The SPB team was composed of a variety of professionals with different levels and skills, where most of them were undergraduate students with major in software engineering (from 4th semester or upper). 
+Since the students could not dedicate many hours per week to the project, they always had the flexibility to negotiate their work schedule during the semester in order not to cause any damage to their grades. Their daily work routine in the project included programming and devops tasks. 
+
+The development of SPB project required a vast experience and background that usually undergraduate students do not have yet. For this reason, some senior developers have joined to the project to help with hard issues and to transfer knowledge to the students. Their main task was to provide solutions for complex problems, in other words, they worked as a developer. As these professionals are very skillful and the project could not fund a full time work for them, some of them worked partially on the project. In addition, they lived in a different states spread around Brazil which led much of the communication to be made via Internet.
 
 Finally, the last group of actors of this project was composed of employees
 formally working for the Brazilian Government, in the Ministery of Planning,
--
libgit2 0.21.2