diff --git a/slides/k8s/sealed-secrets.md b/slides/k8s/sealed-secrets.md
index 36db8ea0..0ca4664a 100644
--- a/slides/k8s/sealed-secrets.md
+++ b/slides/k8s/sealed-secrets.md
@@ -18,7 +18,7 @@
 
 - server side controller will re-create original secret, when the ciphered one are added to the cluster
 
-- it "safe" to add those secret to your source tree
+- it makes it "safe" to add those secret to your source tree
 
 - since version 0.9 key rotation are enable by default, so remember to backup private keys regularly.
   </br> (or you won't be able to decrypt all you keys, in a case of *disaster recovery*)
@@ -38,7 +38,7 @@
 
 - Install controller
   ```bash
-  helm install -n kube-system stable/sealed-secrets sealed-secrets-controller
+  helm install -n kube-system sealed-secrets-controller stable/sealed-secrets
   ```
 
 - Create a secret you don't want to leak
diff --git a/slides/k8s/testing.md b/slides/k8s/testing.md
index a2ef3543..b3822e1e 100644
--- a/slides/k8s/testing.md
+++ b/slides/k8s/testing.md
@@ -36,7 +36,7 @@ RUN <build code>
 CMD, EXPOSE ...
 ```
 
-- This leverages the Docker cache: it the code doesn't change, the tests don't need to run
+- This leverages the Docker cache: if the code doesn't change, the tests don't need to run
 
 - If the tests require a database or other backend, we can use `docker build --network`