diff --git a/slides/swarm/btp-manual.md b/slides/swarm/btp-manual.md
index bc24eaf1..6aeed0a3 100644
--- a/slides/swarm/btp-manual.md
+++ b/slides/swarm/btp-manual.md
@@ -141,7 +141,7 @@ It alters the code path for `docker run`, so it is allowed only under strict cir
 
 - Update `webui` so that we can connect to it from outside:
   ```bash
-  docker service update webui --publish-add 8000:80 --detach=false
+  docker service update webui --publish-add 8000:80
   ```
 
 ]
@@ -197,7 +197,7 @@ It has been replaced by the new version, with port 80 accessible from outside.
 
 - Bring up more workers:
   ```bash
-  docker service update worker --replicas 10 --detach=false
+  docker service update worker --replicas 10
   ```
 
 - Check the result in the web UI
@@ -235,7 +235,7 @@ You should see the performance peaking at 10 hashes/s (like before).
 - Re-create the `rng` service with *global scheduling*:
   ```bash
     docker service create --name rng --network dockercoins --mode global \
-      --detach=false $REGISTRY/rng:$TAG
+      $REGISTRY/rng:$TAG
   ```
 
 - Look at the result in the web UI
diff --git a/slides/swarm/healthchecks.md b/slides/swarm/healthchecks.md
index 3433201f..b9fcac7a 100644
--- a/slides/swarm/healthchecks.md
+++ b/slides/swarm/healthchecks.md
@@ -146,7 +146,7 @@ First, let's make an "innocent" change and deploy it.
   docker-compose -f dockercoins+healthcheck.yml build
   docker-compose -f dockercoins+healthcheck.yml push
   docker service update dockercoins_hasher \
-           --detach=false --image=127.0.0.1:5000/hasher:$TAG
+           --image=127.0.0.1:5000/hasher:$TAG
   ```
 
 ]
@@ -170,7 +170,7 @@ And now, a breaking change that will cause the health check to fail:
   docker-compose -f dockercoins+healthcheck.yml build
   docker-compose -f dockercoins+healthcheck.yml push
   docker service update dockercoins_hasher \
-           --detach=false --image=127.0.0.1:5000/hasher:$TAG
+           --image=127.0.0.1:5000/hasher:$TAG
   ```
 
 ]