Improve tutorial visual

Author: Pixcell

content/docs/1.3.0/tutorial/deploy-our-microservice.md

@@ -254,7 +254,8 @@ Sensors		    RUNNING		local-agent	{}			            Moving Average
 
 ## Conclusion
 
-Have a look at new output of the Freeboard at <a href="http://localhost:10102/?load=dashboard.json" target="_blank">http://localhost:10102/?load=dashboard.json</a>. This should now display the values modified by moving average.
+Have a look at new output of the [Freeboard dashboard](http://localhost:10102/?load=dashboard.json). This should now display the values modified by moving average and look similar to this:
+<img src="/images/Freeboard_2.png" style="max-width:100%;border-radius: 0.3em;margin: 35px 0;" />
 
 The magic about microservices and ioFog is that none of those microservice is specifically designed or requires to work with the other microservice. Using ioFog, you can create smart and secure communication channels between independant microservices and easily manage a fleet of Edge devices and microservices.
 

content/docs/1.3.0/tutorial/manage-our-microservices.md

@@ -33,6 +33,9 @@ The _REST API_ is a generic microservice that provides a REST API web server, al
 
 _Freeboard_ is the last microservice that provides an HTML dashboard to view the real-time results coming from a rest API data source. In the case of our tutorial, the source of the data is our REST API microservice.
 
+Currently, loading the [freeboard dashboard](http://localhost:10102/?load=dashboard.json) should look similar to this:
+<img src="/images/Freeboard_1.png" style="max-width:100%;border-radius: 0.3em;margin: 35px 0;" />
+
 ## Routes
 
 The Sensors and REST API microservices are generic. They are not hardcoded to talk with each other, instead, the relationship dictating the flow of data was configured with the Controller. This is in the spirit of the microservice architecture, separating concerns into pieces so that we can combine and interchange them.