docs: fix typos (#993)

Update docs to fix several typos

Author: gmccue

README.md

@@ -54,7 +54,7 @@ skaffold dev
 
 On code change, skaffold will rebuild the image, redeploy it and print all logs.
 
-⚠️ Do not forget to clean up the development cluster once are finished:
+⚠️ Do not forget to clean up the development cluster once you are finished:
 
 ```sh
 make -C dev down

docs/explanation/provider-id.md

@@ -1,6 +1,6 @@
 # Provider ID
 
-The provider ID is a unique identifier of a machine assigned to a Kubernets Node object. It enables cloud providers to link Kubernetes Nodes with their underlying infrastructure. In Kubernetes, this ID is specified under `spec.providerID` in the Node specification. The Hetzner Cloud Controller Manager sets this value during node initialization.
+The provider ID is a unique identifier of a machine assigned to a Kubernetes Node object. It enables cloud providers to link Kubernetes Nodes with their underlying infrastructure. In Kubernetes, this ID is specified under `spec.providerID` in the Node specification. The Hetzner Cloud Controller Manager sets this value during node initialization.
 
 In the Hetzner ecosystem, the following provider ID formats are used:
 

docs/guides/load-balancer/quickstart.md

@@ -22,4 +22,4 @@ spec:
   type: LoadBalancer
 ```
 
-This sample service will create a Load Balancer in the location `hel1`. The `listen_port` will be 80. The `destination_port` will be a random random node port selected by Kubernetes. Traffic arriving at the Load Balancer on Port 80 will be routed to the public interface of the targets on a node port.
+This sample service will create a Load Balancer in the location `hel1`. The `listen_port` will be 80. The `destination_port` will be a random node port selected by Kubernetes. Traffic arriving at the Load Balancer on Port 80 will be routed to the public interface of the targets on a node port.

docs/guides/private-network-setup.md

@@ -2,7 +2,7 @@
 
 This guide teaches you how to setup HCCM with support for Private Networks. Please familiarize yourself with the explanation document about [Private Networks](../explanation/private-networks.md).
 
-Before setting up the hcloud-cloud-controller-manager you need to configure your cluster appropriatly. When creating your cluster you need to provide the `kubelet` [option](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) `--cloud-provider=external`. How this is done depends on your Kubernetes distribution.
+Before setting up the hcloud-cloud-controller-manager you need to configure your cluster appropriately. When creating your cluster you need to provide the `kubelet` [option](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) `--cloud-provider=external`. How this is done depends on your Kubernetes distribution.
 
 By default, the HCCM's route controller is enabled. For this reason, you need to choose an appropriate CNI plugin, which supports native routing capabilities of the underlying infrastructure. As an example, Cilium can be set to use the [`routing-mode: native`](https://docs.cilium.io/en/stable/network/concepts/routing/#native-routing).
 

docs/guides/quickstart.md

@@ -1,6 +1,6 @@
 # Quick start
 
-Before setting up the hcloud-cloud-controller-manager you need to configure your cluster appropriatly. When creating your cluster you need to provide the `kubelet` [option](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) `--cloud-provider=external`. How this is done depends on your Kubernetes distribution.
+Before setting up the hcloud-cloud-controller-manager you need to configure your cluster appropriately. When creating your cluster you need to provide the `kubelet` [option](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) `--cloud-provider=external`. How this is done depends on your Kubernetes distribution.
 
 1. Create a read+write API token in the [Hetzner Cloud Console](https://console.hetzner.cloud/) as described in [this document](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/).
 

docs/guides/robot/quickstart.md

@@ -1,6 +1,6 @@
 # Quickstart
 
-Before setting up the hcloud-cloud-controller-manager you need to configure your cluster appropriatly. When creating your cluster you need to provide the `kubelet` [option](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) `--cloud-provider=external`. How this is done depends on your Kubernetes distribution.
+Before setting up the hcloud-cloud-controller-manager you need to configure your cluster appropriately. When creating your cluster you need to provide the `kubelet` [option](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) `--cloud-provider=external`. How this is done depends on your Kubernetes distribution.
 
 1. Create a read+write API token in the [Hetzner Cloud Console](https://console.hetzner.cloud/) as described in [this document](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/).
 

docs/reference/helm/extra-envs.md

@@ -4,13 +4,13 @@ Extra environment variables can be set via the `env` Helm value. The well-known
 
 ```yaml
 env:
-  ROBUT_USER:
+  ROBOT_USER:
     value: "<robot-user>"
 ```
 
 ```yaml
 env:
-  ROBUT_USER:
+  ROBOT_USER:
     valueFrom:
       secretKeyRef:
         name: hcloud