diff --git a/opensym2017/content/05-requirements.tex b/opensym2017/content/05-requirements.tex
index 330d682..0b472dc 100644
--- a/opensym2017/content/05-requirements.tex
+++ b/opensym2017/content/05-requirements.tex
@@ -1,35 +1,28 @@
 \section{Requirements}
 \label{sec:requirements}
 
-By preparing the evolution the SPB Portal, the Brazilian Government executed
-three steps to collect the requirements. The first step consisted in order to
-collect proposals using an online tool called Pligg
-\footnote{\url{https://pligg.com}} and share them openly on the Internet. The
-citizens were able to write proposals as well as vote on those that most
-interested them. At the end of this step, the Brazilian Government collected
-about 100 proposals and the initial perspective was to prioritize the most
-voted of them to be implemented for the new SPB Portal.
+By preparing the SPB Portal evolution, the Brazilian Government has executed
+three steps to collect the requirements. The first step was the collection of proposals using an online tool called Pligg and the open sharing of them on the Internet.
+In this step, the citizens have written and voted on proposals they
+were more interested in. At the end, the Brazilian Government collected about 100 proposals and its initial perspective was to give to the most voted ones the priority of implementation on the new SPB Portal.
 
-The second step was two open face-to-face meetings that aimed to discuss ideas
-(not necessarily based on the proposals collect during the first step) to
-improve the SPB Portal and its specific environments. At the first day, the
+The second step was two face-to-face meetings that aimed to discuss ideas (not
+necessarily based on the previous collected proposals) to improve the SPB
+Portal and its environments. On the first day, the
 participants were divided in two groups to discuss (i) features and
-technologies as well as (ii) user experience and ideas in general regarding to
-SPB Portal. Each group generated a ``mind map'' to summarize and correlate its
+technologies as well as (ii) user experience and general ideas regarding the
+SPB Portal. Each group has generated a ``mind map'' to summarize and to correlate its
 ideas.  During the second day, the participants were allocated in three groups
 to discuss features related to (i) the process of software evaluation and
-acceptance in the SPB Portal, (ii) the approaches to share the SPB projects,
-and (iii) how to attract universities and students to collaborate to SPB
+acceptance in the SPB Portal, (ii) approaches to share the SPB projects,
+and (iii) ways to attract universities and students to collaborate to SPB
 projects.
 
-The last step was a workshop with IT representatives from a specific group at
-the Government and public organizations. One more time, the objective was to
-collect proposals to evolute the SPB Portal, but the discussions was not
-necessarily related to the ideas provided during the first and second steps.
+The last step was a workshop with some IT representatives of the Federal Government and public organizations and, again, it was focused on collecting new proposals to evolve the SPB Portal.
 
-After these uncoated three steps, the Brazilian government generated a list of
-145 requirements. By trying to mitigate the lack of focus from the requirement
-list, we propose to release an initial version that would replace the old SPB
+After these unconnected three steps, the Brazilian government has generated a list of
+145 requirements. In order to mitigate the lack of focus in the requirement
+list, we have proposed to release an initial version to replace the old SPB
 portal, prioritizing the following features:
 
 \begin{enumerate}
@@ -40,9 +33,9 @@ portal, prioritizing the following features:
 \item Mailing lists and discussion forums.
 \end{enumerate}
 
-Moreover, the new SPB Portal just would work properly if there is a unique
+Moreover, the new SPB Portal would only work properly if there was a unique
 authentication to use the provided features. Additionally, a unified interface
-was an important non-functional requirement to have a better user experience in
+was an important non-functional requirement to provide better user experience on
 the new platform.
 
 Other requirements were in the wishlist such as an integrated search engine and
--
libgit2 0.21.2