Use 'Kubernetes' instead of 'kubernetes'

Official it is written somtimes with a capital K, sometimes with a lower-case k.
But the documentation mostly uses capital K, thus we should follow that.

Author: dragetd

README.md

@@ -1,6 +1,6 @@
 # Preface
 
-In a perfect world every written service will work smooth, your test coverage is on top and there are no bugs in your API. But we all know, that we can't achieve this world, sadly. It's not unusual that there's a bug in an API and you have to debug this problem in a production environment. We have faced this problem with our go services in our kubernetes cluster and we want to show you how it's possible to remote debug a go service in a kubernetes cluster.
+In a perfect world every written service will work smooth, your test coverage is on top and there are no bugs in your API. But we all know, that we can't achieve this world, sadly. It's not unusual that there's a bug in an API and you have to debug this problem in a production environment. We have faced this problem with our go services in our Kubernetes cluster and we want to show you how it's possible to remote debug a go service in a Kubernetes cluster.
 
 ## Software Prerequisites
 
@@ -11,16 +11,16 @@ For this scenario we need some software:
 * [Kubectl](https://kubernetes.io/de/docs/tasks/tools/install-kubectl) (used version: 1.17.2)
 * [Visual Studio Code](https://code.visualstudio.com/download) (used version: 1.32.3)
 
-We decided to use `kind` instead of `minikube`, since it's a very good tool for testing kubernetes locally and we can use our docker images without a docker registry.
+We decided to use `kind` instead of `minikube`, since it's a very good tool for testing Kubernetes locally and we can use our docker images without a docker registry.
 
 ## Big Picture
 
 First we will briefly explain how it works:
 
-1. We create a new kubernetes cluster `local-debug-k8s` on our local system
+1. We create a new Kubernetes cluster `local-debug-k8s` on our local system
 
 * you need a docker container with [delve](https://github.com/go-delve/delve) (the go debugger) as the main process
-* delve needs access to the path with the project data. This is done by mounting `$GOPATH/src` on the pod which is running in the kubernetes cluster
+* delve needs access to the path with the project data. This is done by mounting `$GOPATH/src` on the pod which is running in the Kubernetes cluster
 * we start the delve container on port 30123 and bind this port to localhost, so that only our local debugger can communicate with delve
 * to debug an API with delve, it's necessary to set up an ingress network. For this we use port 8090.
 
@@ -186,7 +186,7 @@ You are ready to start the service in the debug mode:
 
 Let's go through the deployment.
 
-* Image name is what we loaded into the kind cluster with the command `kind load image...`. _imagePullPolicy_ must be set to _IfNotPresent_, because it is already loaded there and we don't want kubernetes to try doing it once more.
+* Image name is what we loaded into the kind cluster with the command `kind load image...`. _imagePullPolicy_ must be set to _IfNotPresent_, because it is already loaded there and we don't want Kubernetes to try doing it once more.
 
           image: setlog/debug-k8s:latest
           imagePullPolicy: IfNotPresent