diff --git a/slides/containers/Container_Engines.md b/slides/containers/Container_Engines.md
index 4ab41b96..8da77c6c 100644
--- a/slides/containers/Container_Engines.md
+++ b/slides/containers/Container_Engines.md
@@ -104,22 +104,6 @@ like Windows, macOS, Solaris, FreeBSD ...
 
 ---
 
-## rkt
-
-* Compares to `runc`.
-
-* No daemon or API.
-
-* Strong emphasis on security (through privilege separation).
-
-* Networking has to be set up separately (e.g. through CNI plugins).
-
-* Partial image management (pull, but no push).
-
-  (Image build is handled by separate tools.)
-
----
-
 ## CRI-O
 
 * Designed to be used with Kubernetes as a simple, basic runtime.
diff --git a/slides/k8s/concepts-k8s.md b/slides/k8s/concepts-k8s.md
index 0e27a464..5dfc596b 100644
--- a/slides/k8s/concepts-k8s.md
+++ b/slides/k8s/concepts-k8s.md
@@ -191,12 +191,12 @@ No!
 
 - By default, Kubernetes uses the Docker Engine to run containers
 
-- We could also use `rkt` ("Rocket") from CoreOS
-
 - Or leverage other pluggable runtimes through the *Container Runtime Interface*
 
   (like CRI-O, or containerd)
 
+- Different install methods and distributions use different runtimes
+
 ---
 
 class: extra-details