diff --git a/slides/index.yaml b/slides/index.yaml
index 1f8687dd..7edf0a58 100644
--- a/slides/index.yaml
+++ b/slides/index.yaml
@@ -23,6 +23,15 @@
   speaker: jpetazzo
   attend: https://conferences.oreilly.com/velocity/vl-ny/public/schedule/detail/69875
 
+- date: 2018-09-17
+  country: fr
+  city: Paris
+  event: ENIX SAS
+  speaker: jpetazzo
+  title: Déployer ses applications avec Kubernetes (in French)
+  lang: fr
+  attend:  https://enix.io/fr/services/formation/deployer-ses-applications-avec-kubernetes/
+
 - date: 2018-07-17
   city: Portland, OR
   country: us
diff --git a/slides/kube/concepts-k8s.md b/slides/kube/concepts-k8s.md
index 95a2b7d4..3bf5c4db 100644
--- a/slides/kube/concepts-k8s.md
+++ b/slides/kube/concepts-k8s.md
@@ -239,7 +239,11 @@ Yes!
   - namespace (more-or-less isolated group of things)
   - secret (bundle of sensitive data to be passed to a container)
  
-  And much more! (We can see the full list by running `kubectl api-resources`)
+  And much more!
+
+- We can see the full list by running `kubectl api-resources`
+
+  (In Kubernetes 1.10 and prior, the command to list API resources was `kubectl get`)
 
 ---
 
diff --git a/slides/kube/kubectlget.md b/slides/kube/kubectlget.md
index 8098e788..988d85d9 100644
--- a/slides/kube/kubectlget.md
+++ b/slides/kube/kubectlget.md
@@ -83,7 +83,9 @@
 
 - `kubectl` has pretty good introspection facilities
 
-- We can list all available resource types by running `kubectl api-resources` (this used to be `kubectl get`)
+- We can list all available resource types by running `kubectl api-resources`
+  <br/>
+  (In Kubernetes 1.10 and prior, this command used to be `kubectl get`)
 
 - We can view details about a resource with:
   ```bash
diff --git a/slides/kube/namespaces.md b/slides/kube/namespaces.md
index 9993a0d9..87b5b546 100644
--- a/slides/kube/namespaces.md
+++ b/slides/kube/namespaces.md
@@ -151,7 +151,7 @@ Note: it might take a minute or two for the app to be up and running.
 
 - A pod in the `default` namespace can communicate with a pod in the `kube-system` namespace
 
-- `kube-dns` uses a different subdomain for each namespace
+- CoreDNS uses a different subdomain for each namespace
 
 - Example: from any pod in the cluster, you can connect to the Kubernetes API with:
 
diff --git a/slides/kube/whatsnext.md b/slides/kube/whatsnext.md
index 263da980..bbce2681 100644
--- a/slides/kube/whatsnext.md
+++ b/slides/kube/whatsnext.md
@@ -28,7 +28,7 @@ And *then* it is time to look at orchestration!
 
 - Each of the two `redis` services has its own `ClusterIP`
 
-- `kube-dns` creates two entries, mapping to these two `ClusterIP` addresses:
+- CoreDNS creates two entries, mapping to these two `ClusterIP` addresses:
 
   `redis.blue.svc.cluster.local` and `redis.green.svc.cluster.local`