diff --git a/README.md b/README.md
index 156ea4e..90c6599 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ At the end script asks you to add TLS certificate to your key chain (the command
 
 Use credentials to log into [Kyma Console](https://console.local.kyma.dev)
 
-If you wan to use `kubectl` to connect to the cluster, you have to first execute command `k3d kubeconfig merge kyma --switch-context`
+If you wan to use `kubectl` to connect to the cluster, you have to first execute command `k3d kubeconfig merge kyma --kubeconfig-switch-context`
 You can get the password for `admin@kyma.cx` in the future by running `kubectl get secret admin-user -n kyma-system -o jsonpath="{.data.password}" | base64 --decode`
 
 Your cluster is ready!
diff --git a/kyma-k3d-start.sh b/kyma-k3d-start.sh
index 1fcf337..70e81f2 100755
--- a/kyma-k3d-start.sh
+++ b/kyma-k3d-start.sh
@@ -1,5 +1,5 @@
 k3d cluster start kyma --wait
-export KUBECONFIG="$(k3d kubeconfig merge kyma --switch-context)"
+export KUBECONFIG="$(k3d kubeconfig merge kyma --kubeconfig-switch-context)"
 # Wait for nodes to be ready before scheduling any workload
 while [[ $(kubectl get nodes -o 'jsonpath={..status.conditions[?(@.type=="Ready")].status}') != "True" ]]; do echo "Waiting for cluster nodes to be ready, elapsed time: $(( $SECONDS/60 )) min $(( $SECONDS % 60 )) sec"; sleep 2; done
 export REGISTRY_IP=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' /registry.localhost)