diff --git a/opensym2017/content/02-spb.tex b/opensym2017/content/02-spb.tex
index 97797e2..db4c120 100644
--- a/opensym2017/content/02-spb.tex
+++ b/opensym2017/content/02-spb.tex
@@ -2,9 +2,9 @@
 \label{sec:spb}
 
 FOSS is a phenomenon that has gained notoriety in recent years and has been
-attarcting the interest of academia. However, since the beginning of computing
+attracting the interest of academia. However, since the beginning of computing
 the majority of developers worked in the way that we now identify as free
-software, that is, sharing code openly. This feature makes the code available
+software, that is, sharing code openly. This openness makes the code available
 for inspection, modification, and use by any person or organization
 \cite{hippel2003,kon2012}.
 
@@ -16,7 +16,7 @@ and its development is based on open collaboration and development practices
 \cite{meirelles2013}.
 
 From the economic point of view, unlike what happens with proprietary software,
-FOSS promotes the establishment of several suppliers that compete with each
+FOSS promotes the establishment of several suppliers that can compete with each
 other based on the same software. This stronger competition among suppliers
 brings benefits to users because it gives better assurances regarding the
 evolution of the system and induces a reduction in prices \cite{kon2012}. These
@@ -31,14 +31,15 @@ study, adapt, and improve the software. Example of common FOSS licenses  are
 the \textit{GPL (GNU General Public License)}, the Apache license, the MIT
 license, and the BSD license.
 
-The SPB portal has been designed in 2005 and released in 2007. In a practical
-view, it is a web system that has consolidated itself as a software project
-sharing environment. It provides a space (community) for each software.
-Therefore, the current platform for SPB was designed to include tools that
-promote collaboration and interaction in communities (by managers, users, and
-developers) of the projects, according to the practices used in FOSS
-communities. This includes e-mail lists, discussion forums, issue trackers,
-version control systems, and social networking environments.
+The original incarnation of SPB portal has been designed in 2005 and
+released in 2007. From a practical point of view, it is a web system
+that has consolidated itself as an environment for sharing software
+projects.  It provides a space (community) for each software.
+Therefore, it was designed to include tools that promote collaboration
+and interaction in communities (by managers, users, and developers) of
+the projects, according to the practices used in FOSS communities. This
+includes mailing lists, discussion forums, issue trackers, version
+control systems, and social networking environments.
 
 Initially, the purpose of the portal was only to share the software developed
 in the Brazilian government, to reduce the costs of hiring software. However,
@@ -48,13 +49,14 @@ results obtained through the use of those solutions. In this way, some software
 development cooperatives and private companies have shown an interest in making
 their software available on the SPB platform.
 
-The concept of Brazilian Public Software goes beyond FOSS. In addition to being
-licensed under a FOSS license, a SPB needs to have explicit guarantees that it
-is a public good, and that project must be available in the SPB portal. Being a
-true public good assumes requirements that can not be met solely by means of
-FOSS licensing. For example, there must be a relaxed trademark usage policy by
-the original vendor that do not stop eventual competitors from adversiting
-services for that same software. Inclusion in the SPB project also has extra
-requirements, such as having a public version control system, installation
-manual, and hardware requirements specification.
+The concept of Brazilian Public Software goes beyond FOSS. In addition
+to being licensed under a FOSS license, a SPB needs to have explicit
+guarantees that it is a public good, and that project must be available
+in the SPB portal. Being a true public good assumes requirements that
+can not be met solely by means of FOSS licensing. For example, there
+must be a relaxed trademark usage policy by the original vendor that
+does not stop eventual competitors from advertising services for that
+same software. Inclusion in the SPB Portal also has extra requirements,
+such as having a public version control system, installation manual, and
+hardware requirements specification.
 
--
libgit2 0.21.2