diff --git a/.travis.yml b/.travis.yml
index 823032b5..b6f5ef5d 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -33,8 +33,11 @@ install:
     - pwd
     - sh build    
 
-script:
+before_script:
+    - go get github.com/golang/lint/golint
+
 
+script:
 
 notifications:
     email: false
diff --git a/doc/tutorial/fogflow.md b/doc/tutorial/fogflow.md
index 29c55ceb..a9cb0163 100644
--- a/doc/tutorial/fogflow.md
+++ b/doc/tutorial/fogflow.md
@@ -22,9 +22,11 @@ and also usage context on the expected QoS defined by users. More details can be
 
 # System View
 
-This section explains an example usecase implementation using Fogflow and Fiware Orion in integration with each other as shown in the diagram. The context data generated by Fogflow worker is subscribed by the Orion Broker. As soon as the subscribed context entity is available with the Fogflow Broker, an NGSI update notification will be sent to FIWARE Orion.
+This section explains an example usecase implementation using FogFlow and FIWARE Orion in integration with each other. 
 
-Let us consider temperature sensor example. The temperature sensors send temperature context data based on location to Fogflow Broker in the form of NGSI updates, assuming that IOT agent sits in the middle if IOT devices are non-NGSI.The Worker tasks process that data flow and send an NGSI update to Fogflow Broker. In no time, this update notification is also sent to FIWARE Orion. From FIWARE Orion, these context entities can also be used by other FIWARE GEs using pub-sub requests.
+AS shown in the following diagram, in this use case a connected temperature sensor sends an update message to the FogFlow system, which triggers some running task instance of a pre-defined fog function to generate some analytics result. The fog function is specified in advance via the FogFlow dashboard, however, it is triggerred only when the temperature sensor joins the sytem. In a real distributed setup, the running task instance will be deployed at the edge node closed to the temperature sensor. 
+
+Once the generated analytics result is generated, it will be forwarded from the FogFlow system to Orion Context Broker. This is because a subscription with Orion Context Broker as the reference URL has been issued.  
 
 ![System View for Fogflow and Fiware Orion Integration](images/systemview.png)
 
@@ -57,6 +59,8 @@ you need to change the following addresses in config.json according to your own
 - **external_hostip**: this is the same as coreservice_ip, for the cloud part of FogFlow;        
 - **internal_hostip**: is the IP of your default docker bridge, which is the "docker0" network interface on your host
 
+**notice:**: please DO NOT use "127.0.0.1" as the IP address of **coreservice_ip** and **external_hostip**, because they will be used by a running task inside a docker container. 
+
 **Firewall rules:** to make your FogFlow web portal accessible via the external_ip; the following ports must be open as well: 80, 443, 8080, and 5672 for TCP
     
 Pull the docker images of all FogFlow components and start the FogFlow system