diff --git a/opensym2017/content/02-spb.tex b/opensym2017/content/02-spb.tex
index db4c120..3da72d0 100644
--- a/opensym2017/content/02-spb.tex
+++ b/opensym2017/content/02-spb.tex
@@ -1,12 +1,10 @@
 \section{Background}
 \label{sec:spb}
 
-FOSS is a phenomenon that has gained notoriety in recent years and has been
-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 openness makes the code available
-for inspection, modification, and use by any person or organization
-\cite{hippel2003,kon2012}.
+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
+openness makes the code available for inspection, modification, and use by any
+person or organization \cite{hippel2003,kon2012}.
 
 The elements that distinguish FOSS from other types of software are the
 reasoning about the development process, the economic context, the relationship
diff --git a/opensym2017/content/07-process.tex b/opensym2017/content/07-process.tex
index 60b8e55..1a0871b 100644
--- a/opensym2017/content/07-process.tex
+++ b/opensym2017/content/07-process.tex
@@ -92,13 +92,12 @@ the Brazilian government and citizens interested in following the project. To
 handle those cases, we used a set of tools to communication and other to manage
 the project.
 
-For communication between member in different places, we used: Google
-handouts with tmate tool, IRC, and mailing lists. When one student had to
-work in pair with a senior, normally, they used Google hangout for
-communication and they shared a terminal session with tmate which allow
-them to share the same terminal, with both typing and seeing the screen.
-For questions and fast discussion, we used IRC. For general
-notification, we used the mailing lists.
+For communication between members in different places, we used: video
+conferencing with shared terminal tools, IRC, and mailing lists. For example,
+when one student had to work in pair with a senior, normally, they used video
+conferencing tool for talking and shared a terminal session (both typing and
+seeing the screen in real time). For questions and fast discussion, we used
+IRC. For general notification, we used the mailing lists.
 
 For managing the project we used the SPB Portal itself; first to validate it by
 ourselves, and also because it had all the required tools. We basically created
diff --git a/opensym2017/content/08-contributions.tex b/opensym2017/content/08-contributions.tex
index 286e18e..2801e8d 100644
--- a/opensym2017/content/08-contributions.tex
+++ b/opensym2017/content/08-contributions.tex
@@ -38,8 +38,8 @@ Colab uses this mechanism to manage the authentication.
 Noosfero was the tool that contemplated several functional requirements,
 therefore we made a large number of contributions with upstream. We helped to
 migrate to the latest Rails version (web framework used by Noosfero), enable
-the federation implementation (federation with other social networks), decouple
-the interface and the back-end, and so forth.
+the federation implementation (federation with other social networks), and
+decouple the interface and the back-end.
 
 We also made some contributions on the DevOps front. Some members of
 them team became maintainers of some python libraries that were used by
--
libgit2 0.21.2