docs: typos (#506)

Signed-off-by: guoguangwu <guoguangwu@magic-shield.com>

README.md

@@ -49,7 +49,7 @@ will create volumes that will be billed.
 
 1. Configure your environment correctly
    ```bash
-   export HCLOUD_TOKEN=<specifiy a project token>
+   export HCLOUD_TOKEN=<specify a project token>
    export K8S_VERSION=1.21.0 # The specific (latest) version is needed here
    export USE_SSH_KEYS=key1,key2 # Name or IDs of your SSH Keys within the Hetzner Cloud, the servers will be accessible with that keys
    ```

docs/docker-swarm/README.md

@@ -35,7 +35,7 @@ docker plugin enable hetznercloud/hcloud-csi-driver:swarm
 
 ## How to create a volume
 
-Example: Create a volume wih size 50G in Nuremberg:
+Example: Create a volume with size 50G in Nuremberg:
 
 ```bash
 docker volume create --driver hetznercloud/hcloud-csi-driver:swarm --required-bytes 50G --type mount --sharing onewriter --scope single hcloud-debug1 --topology-required csi.hetzner.cloud/location=nbg1

docs/v2.0.0-fix-volume-topology/fix-volume-topology.md

 # Updating the Topology selection for `PersistentVolumes` created with csi-driver v2.0.0
 
-This guide is intended for Kubernetes Cluster operators that installed the hcloud-csi-driver v2.0.0 and created Volumes. Unfortunatly this version included a change that we had to revert, for details you can read the [issue #333](https://github.com/hetznercloud/csi-driver/issues/333).
+This guide is intended for Kubernetes Cluster operators that installed the hcloud-csi-driver v2.0.0 and created Volumes. Unfortunately this version included a change that we had to revert, for details you can read the [issue #333](https://github.com/hetznercloud/csi-driver/issues/333).
 
 The affected `PersistentVolumes` reference a wrong label in the `spec.nodeAffinity.required` fields. The volumes work as they should, but for consistency and future compatibility we recommend that the `PersistentVolumes` should be fixed.
 
@@ -11,7 +11,7 @@ This is only possible if it is not attached to a node, so any workload using the
 
 You need to have `kubectl` and the `hcloud` cli tool installed for this guide.
 
-To avoid creating any new broken `PersistentVolumes` while you are still fixing old ones, you should ugprade to `v2.0.1` or `v2.1.0` before starting this guide. After all `PersistentVolumes` have been migrated, you should upgrade to `v2.1.0`
+To avoid creating any new broken `PersistentVolumes` while you are still fixing old ones, you should upgrade to `v2.0.1` or `v2.1.0` before starting this guide. After all `PersistentVolumes` have been migrated, you should upgrade to `v2.1.0`
 
 ## Find affected `PersistentVolumes`