diff --git a/opensym2017/content/05-architecture.tex b/opensym2017/content/05-architecture.tex
index c86177d..945f6d3 100644
--- a/opensym2017/content/05-architecture.tex
+++ b/opensym2017/content/05-architecture.tex
@@ -39,10 +39,10 @@ described how we integrated those tools and conclude with the deployment.
 
 \subsection{Colab}
 
-Colab\footnote{\url{https://github.com/colab/colab}} has integration of web
-applications as its main goal, the user of this integrated system should not
-notice the change between the integrated applications. To do that Colab was
-designed to use plugins of each application and has four levels of integration:
+Colab integrates web applications as its main goal, the user of this composed
+system should not notice the change between the integrated applications. Colab
+was designed to use one plugin for each system under its domain, this is
+guaranteed by four levels of integration:
 
 \begin{itemize}
   \item Authentication
@@ -51,13 +51,13 @@ designed to use plugins of each application and has four levels of integration:
   \item Data and search engine
 \end{itemize}
 
-Colab works as a reverse proxy, therefore all external requests pass through
-it, this is an advantage to manage these four levels of integration.
+The aforementioned integrations levels were possible, because Colab works as a
+reverse proxy, therefore all external requests pass through it.
 
 Single Sign-On (SSO) is used to login users throughout all integrated
 applications. REMOTE\_USER HTTP header is sent to the applications and we
 expect that they know how to handle it, since this is a common authentication
-mechanism. The integrated applications should be in a local network to avoid
+mechanism. The integrated applications should be on a local network to avoid
 security issues. With this the user will be able to navigate through the
 platform applications and will not be asked for authentication credentials.
 
--
libgit2 0.21.2