add k8s comments

labs/docker-201/3.md

@@ -285,4 +285,6 @@ docker volume ls
 ![Storage 7](/posts/files/docker-201/assets/images/storage7.png)
 
 
-#### Congratulations! You have learned some different ways to provide connectivity and storage to containers, and what are the specific concerns for some of them. Read on to learn how to manage a number of containers belonging to a single service!
+#### Congratulations! You have learned some different ways to provide connectivity and storage to containers, and what are the specific concerns for some of them. It is important to remark that in real-life deployments you will use an orchestration solution (like Swarm or Kubernetes) to manage containers lifecycle, and other aspects like networking inside the clusters. 
+
+#### In any case please read on to learn how to manage a number of containers belonging to a single service!

labs/docker-201/4.md

@@ -1,6 +1,6 @@
 # Docker Compose
 
-Usually applications are composed by a number of containers that interact among them to provide the defined service. Docker Compose is a  useful tool to orchestrate these containers that belong to the same service, so that we do not need to manage them individually, but rather as a joint entity. The format of the file used by this tool is [YAML](https://en.wikipedia.org/wiki/YAML).
+Usually applications are composed by a number of containers that interact among them to provide the defined service. Docker Compose is a useful tool to orchestrate these containers that belong to the same service, so that we do not need to manage them individually, but rather as a joint entity. The format of the file used by this tool is [YAML](https://en.wikipedia.org/wiki/YAML).
 
 If you plan to use your own environment please make sure to [install Docker Compose](https://docs.docker.com/compose/install/) before starting this part of the lab. The [play-with-docker](http://play-with-docker.com) environment already includes it, so no additional installation is required.
 
@@ -129,4 +129,6 @@ However the *play-with-docker* environment does not offer you this option, but w
 
 You can now bring down both containers in this service with `docker-compose kill`, and then remove them with `docker-compose rm -f`.
 
-#### Congratulations! You have now learned how to manage several containers that belong to a single service! Please read on to understand how native orchestration works for Docker containers!
+#### Congratulations! You have now learned how to manage several containers that belong to a single service. Again, in a real-life deployment you will use an orchestration solution (like Swarm or Kubernetes) that will help with the management of service containers.
+
+#### Please read on to understand how Swarm native orchestration works for Docker containers!

labs/docker-201/5.md

@@ -1,6 +1,6 @@
 # Docker Swarm
 
-Docker provides its own orchestration solution for containers, called Docker Swarm. When moving containers to production you need an orchestration solution that aggregates the resources of a number of underlying hosts and offers them to containers users. This solution is also responsible for making sure the right number of containers are healthy for every defined service, starting new ones when it is required according to the policies defined by each user.
+Docker provides its own orchestration solution for containers, called [Docker Swarm](https://docs.docker.com/engine/swarm/) (although there are other options, like [Kubernetes](https://kubernetes.io) that was open-sourced by Google). When moving containers to production you need an orchestration solution that aggregates the resources of a number of underlying hosts and offers them to containers users. This solution is also responsible for making sure the right number of containers are healthy for every defined service, starting new ones when it is required according to the policies defined by each user.
 
 Its architecture includes 2 types of nodes: *managers* and *workers*, usually implemented in different hosts. *Managers* provide the control function for the whole architecture, and *workers* acutally run the containers that provide service to end users.