📃 Add descriptions for some chapters

slides/containers/Copy_On_Write.md

@@ -337,3 +337,9 @@ class: extra-details
   <br/>
   data should always be stored in volumes anyway!
 
+???
+
+:EN:- Copy-on-write filesystems
+:EN:- Docker graph drivers
+:FR:- Les systèmes de fichiers "copy-on-write"
+:FR:- Les "graph drivers" de Docker

slides/containers/Namespaces_Cgroups.md

@@ -1122,3 +1122,12 @@ See `man capabilities` for the full list and details.
 - LSMs add a layer of access control to all process operations.
 
 - Container engines take care of this so you don't have to.
+
+???
+
+:EN:Containers internals
+:EN:- Linux kernel namespaces
+:EN:- Control groups (cgroups)
+:FR:Fonctionnement interne des conteneurs
+:FR:- Les namespaces du noyau Linux
+:FR:- Les "control groups" (cgroups)

slides/containers/Orchestration_Overview.md

@@ -436,3 +436,7 @@ It depends on:
 
   - false, if we focus on what matters.
 
+???
+
+:EN:- Orchestration overview
+:FR:- Survol de techniques d'orchestration 

slides/containers/Publishing_To_Docker_Hub.md

@@ -122,3 +122,8 @@ There might be a long pause before the first layer is pulled,
 because the API behind `docker pull` doesn't allow to stream build logs, and there is no feedback during the build.
 
 It is possible to view the build logs by setting up an account on [ctr.run](https://ctr.run/).
+
+???
+
+:EN:- Publishing images to the Docker Hub
+:FR:- Publier des images sur le Docker Hub