From 9c9b2fc56c722f68ab9c2458a55272e2f1c6b8de Mon Sep 17 00:00:00 2001
From: Alistair Mackay <34012094+fireflycons@users.noreply.github.com>
Date: Thu, 22 Sep 2022 20:22:50 +0100
Subject: [PATCH] Minor update

---
 README.md                                       | 4 ++++
 docs/11-tls-bootstrapping-kubernetes-workers.md | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c75834c..dbe2377 100644
--- a/README.md
+++ b/README.md
@@ -13,6 +13,10 @@ While the original one uses GCP as the platform to deploy kubernetes,  we use Vi
 
 > The results of this tutorial should not be viewed as production ready, and may receive limited support from the community, but don't let that stop you from learning!
 
+Please note that with this particular challenge, it is all about the minute detail. If you miss one tiny step anywhere along the way, it's going to break!
+
+Always run the `cert_verify` script at the places it suggests, and always ensure you are on the correct node when you do stuff. If `cert_verify` shows anything in red, then you have made an error in a previous step. For the master node checks, run the check on `master-1` and on `master-2`
+
 ## Target Audience
 
 The target audience for this tutorial is someone planning to support a production Kubernetes cluster and wants to understand how everything fits together.
diff --git a/docs/11-tls-bootstrapping-kubernetes-workers.md b/docs/11-tls-bootstrapping-kubernetes-workers.md
index 397b4af..9682e8c 100644
--- a/docs/11-tls-bootstrapping-kubernetes-workers.md
+++ b/docs/11-tls-bootstrapping-kubernetes-workers.md
@@ -449,7 +449,7 @@ Now, go back to `master-1` and approve the pending kubelet-serving certificate
 [//]: # (host:master-1)
 [//]: # (comment:Please now manually approve the certificate before proceeding)
 
-```
+```bash
 kubectl get csr --kubeconfig admin.kubeconfig
 ```