diff --git a/slides/k8s/dmuc-easy.md b/slides/k8s/dmuc-easy.md
index 001ad51d..07a7e90d 100644
--- a/slides/k8s/dmuc-easy.md
+++ b/slides/k8s/dmuc-easy.md
@@ -545,7 +545,38 @@ clusters:
 
 ]
 
-Success!
+If it works: great!
+
+If it complains about a "cgroup driver", check the next slide.
+
+---
+
+## Cgroup drivers
+
+- Cgroups ("control groups") are a Linux kernel feature
+
+- They're used to account and limit resources
+
+  (e.g.: memory, CPU, block I/O...)
+
+- There are multiple ways to manipulate cgroups, including:
+
+  - through a pseudo-filesystem (typically mounted in /sys/fs/cgroup)
+
+  - through systemd
+
+- Kubelet and the container engine need to agree on which method to use
+
+---
+
+## Setting the cgroup driver
+
+- If kubelet refused to start, mentioning a cgroup driver issue, try:
+  ```bash
+  kubelet --kubeconfig ~/.kube/config --cgroup-driver=systemd
+  ```
+
+- That *should* do the trick!
 
 ---
 
diff --git a/slides/k8s/dmuc-medium.md b/slides/k8s/dmuc-medium.md
index 70541513..2ae46664 100644
--- a/slides/k8s/dmuc-medium.md
+++ b/slides/k8s/dmuc-medium.md
@@ -873,7 +873,7 @@ This time, it should work.
 
 - Enable RBAC, and generate individual certificates for each controller
 
-  (check the [certificate paths][certpath] section in the Kubernetes documentatio
+  (check the [certificate paths][certpath] section in the Kubernetes documentation
   for a detailed list of all the certificates and keys that are used by the
   control plane, and which flags are used by which components to configure them!)