Fixes

Signed-off-by: Marco Emilio "sphakka" Poleggi <marcoep@ieee.org>

SwitchEngines/README.md

@@ -784,16 +784,18 @@ on KinD.
      package, install `kubectl` and `kind` via explicit `runcmd` scripts;
    - add any needed extra group for the default user.
 
-Run again terraform apply, **wait a couple of minutes** to let the installation of
-all extra packages to complete, then connect to your instance.
+Run again terraform apply, **wait a couple of minutes** to let the
+installation of all extra packages to complete, then connect to your instance
+and verify that the commands `kind` and `kubectl` are there.
 
+<!--
 Since KinD is not designed for remote use, you'll have to create your cluster
 on the instance as done during the K8s Lab:
 
 1. Write a minimal KinD configuration file for 2 worker nodes.
 1. Provision the cluster.
 1. Deploy the matallb load balancer service.
-
+-->
 
 ### Task #10: Handling Kubernetes deployments  ###
 
@@ -853,7 +855,8 @@ recipe with:
    - at least one [remote-exec
      provisioner](https://developer.hashicorp.com/terraform/language/resources/provisioners/remote-exec)
      which implements a script of shell commands to move around files, create
-     a KinD cluster and, finally, deploy your MetalLB service as done in [Lab K8s](https://gitedu.hesge.ch/lsds/teaching/bachelor/cloud-and-deployment/lab-k8s/-/blob/main/README.md#part-5-actually-deploying-an-application).
+     a KinD cluster and, finally, deploy your MetalLB service as done in [Lab
+     K8s](https://gitedu.hesge.ch/lsds/teaching/bachelor/cloud-and-deployment/lab-k8s/-/blob/main/README.md#part-5-actually-deploying-an-application).
 
 The solution might be something like: