From 9fb94be33b27186d792d09d369a6580ec99e0cf1 Mon Sep 17 00:00:00 2001
From: Marinka <marin.egorov@hotmail.com>
Date: Fri, 14 Nov 2025 23:38:24 +0100
Subject: [PATCH] Change order of slides

---
 slides/containers/Training_Environment.md | 92 +++++++++++------------
 1 file changed, 43 insertions(+), 49 deletions(-)

diff --git a/slides/containers/Training_Environment.md b/slides/containers/Training_Environment.md
index b5c8470f..1dd18ea3 100644
--- a/slides/containers/Training_Environment.md
+++ b/slides/containers/Training_Environment.md
@@ -49,50 +49,6 @@ individual Docker VM.*
 
 ---
 
-## What *is* Docker?
-
-- "Installing Docker" really means "Installing the Docker Engine and CLI".
-
-- The Docker Engine is a daemon (a service running in the background).
-
-- This daemon manages containers, the same way that a hypervisor manages VMs.
-
-- We interact with the Docker Engine by using the Docker CLI.
-
-- The Docker CLI and the Docker Engine communicate through an API.
-
-- There are many other programs and client libraries which use that API.
-
----
-
-class: pic
-
-![Docker Architecture](images/docker-engine-architecture.svg)
-
----
-
-## Can we run Docker locally?
-
-- If you already have Docker (or Podman) installed, you can use it!
-
-- The VMs can be convenient if:
-
-  - you can't/won't install Docker or Podman on your machine,
-
-  - your local internet connection is slow.
-
-- We're going to download many container images and distribution packages.
-
-- If the class takes place in a venue with slow WiFi, this can slow us down.
-
-- The remote VMs have good connectivity and downloads will be fast there.
-
-(Initially, we provided VMs to make sure that nobody would waste time
-with installers, or because they didn't have the right permissions
-on their machine, etc.)
-
----
-
 ## Connecting to your Virtual Machine
 
 You need an SSH client.
@@ -111,6 +67,7 @@ $ ssh <login>@<ip-address>
 
   * MobaXterm (https://mobaxterm.mobatek.net/)
 
+
 ---
 
 ## Checking your Virtual Machine
@@ -144,10 +101,47 @@ Server:
 
 If this doesn't work, raise your hand so that an instructor can assist you!
 
-???
+---
 
-:EN:Container concepts
-:FR:Premier contact avec les conteneurs
+## Installing Docker
+
+- "Installing Docker" really means "Installing the **Docker Engine** and **CLI**".
+
+- The Docker Engine is a **daemon** (a service running in the background) —— it manages containers, the same way that a hypervisor manages VMs.
+
+- We interact with the Docker Engine by using the Docker CLI.
+
+- The Docker CLI and the Docker Engine communicate through an API.
+
+- There are many other programs and client libraries which use that API.
+
+---
+
+class: pic
+
+![Docker Architecture](images/docker-engine-architecture.svg)
+
+
+
+---
+
+## Can we run Docker locally?
+
+- If you already have Docker (or Podman) installed, you can use it!
+
+- The VMs can be convenient if:
+
+  - you can't/won't install Docker or Podman on your machine,
+
+  - your local internet connection is slow.
+
+- We're going to download many container images and distribution packages.
+
+- If the class takes place in a venue with slow WiFi, this can slow us down.
+
+- The remote VMs have good connectivity and downloads will be fast there.
+
+(Initially, we provided VMs to make sure that nobody would waste time
+with installers, or because they didn't have the right permissions
+on their machine, etc.)
 
-:EN:- What's a container engine?
-:FR:- Qu'est-ce qu'un *container engine* ?