diff --git a/opensym2017/content/04-researchdesign.tex b/opensym2017/content/04-researchdesign.tex
index 878621c..8e4b959 100644
--- a/opensym2017/content/04-researchdesign.tex
+++ b/opensym2017/content/04-researchdesign.tex
@@ -1,43 +1,43 @@
 \section{Open Questions}
 \label{sec:researchdesign}
 
-In this paper, we aim to share our experience designing and developing the new
-SPB Portal by reporting, alongside the technical efforts carried out, our
-empirical work process and the lessons learned. In the begins of the new SPB
-Portal project, we had in mind 3 main challenges to overcome, as explained in
-the following open questions.
+In this paper, we share our experience in designing and developing the new
+SPB Portal by reporting the technical efforts carried out, our
+empirical work process, and the lessons learned. The new SPB Portal project
+presented three main challenges, related to the open questions described below.
 
 \begin{description}
 
 \item [Q1:] \textit{Which strategy could be used to integrate several existing
-FLOSS tools to promote the collaborative software development?}
+FLOSS tools to promote a collaborative software development?}
 %
 Based on an extensive list of functional requirements defined by the Brazilian
-Federal Government, we selected some FLOSS systems to form our solution,
-generating a non-trivial integration among them. We looked for system that
-together could provide the largest subset possible of the requirements, and
+Federal Government, we selected some FLOSS systems to compose our solution,
+engineering a nontrivial integration among them. We looked for the systems set
+realizing the largest possible subset of the requirements list. However, we
 were fully aware that we would need to improve those systems in order to
-provide the rest. We were also convinced that it would be impossible to provide
+satisfy the remaining requirements. We were also convinced that it would be impossible to satisfy
 all of those requirements with a single tool.
 
 \item [Q2:] \textit{How to involve students in real-world projects interacting with
 real customers?}
 %
 Our team was mainly composed of software engineering undergraduate
-students, who had the opportunity to interact with senior developers and
-designers on the team, as well as with the team of technicians and
-managers from the Brazilian Government, and the management team from
-UnB. For the majority of the students, this was a first professional experience. We have define an approach to involve the undergraduate students in this project with a central role in our development process.
+students, who had the opportunity to interact with the UnB managers, 
+senior developers, designers, and even with technicians and
+managers from the Brazilian Government.
+For the majority of the students, this was a first professional experience. 
+Even though, our development process defined a central role on students participation.
 
-\item [Q3:] \textit{How to introduce the FLOSS collaborative and agile
-practices to governmental development process?}
+\item [Q3:] \textit{How to introduce collaborative and agile
+practices typical in FLOSS environments in the governmental development process?}
 %
-The Brazilian government works based on a very traditional way regarding
-software developing, frequently focusing on documents. We have need to convince
-them to accept the idea of open scope and empirical development. They have
-certain expectations about the development of project according to RUP
+The software development on Brazilian government is based on a very traditional way,
+frequently focusing documentation deliveries. We had to convince
+them to accept the idea of open scope and empirical development. They had
+certain expectations about the project development according to RUP
 (Rational Unified Process) and PMBOK (Project Management Body of Knowledge)
-approaches, what not match our work based on agile and FLOSS practices. We have
-created strategies that would support different these organizational cultures.
+approaches, which mismatched our work style based on agile and FLOSS practices. So we
+created strategies to conciliate these different organizational cultures within the project.
 
 \end{description}
--
libgit2 0.21.2