Move development instructions to the bottom

Author: monochromata

README.md

@@ -9,12 +9,11 @@ Create [Docker machines](https://github.com/docker/machine) on [Hetzner Cloud](h
 You need to create a project-sepcific access token under `Access` > `API Tokens` in the project control panel
 and pass that to `docker-machine create` with the `--hetzner-api-token` option.
 
+
 ## Building
 
 Use an up-to-date version of [go](https://golang.org/dl)
 
-### For use
-
 To use the driver, you can download the sources and build it locally:
 
     # Get sources and build the binary at ~/go/bin/docker-machine-driver-hetzner
@@ -25,34 +24,6 @@ To use the driver, you can download the sources and build it locally:
     export GOBIN=$GOPATH/bin
     export PATH="$PATH:$GOBIN"
 
-    # Make docker-machine output help including hetzner-specific options
-    docker-machine create --driver hetzner
-
-### For development
-
-Fork this repository, yielding `github.com/<yourAccount>/docker-machine-driver-hetzner`.
-
-    # Get the sources of your fork and build it locally
-    go get github.com/<yourAccount>/docker-machine-driver-hetzner
-
-    # * This integrates your fork into the $GOPATH (typically pointing at ~/go)
-    # * Your sources are at $GOPATH/src/github.com/<yourAccount>/docker-machine-driver-hetzner
-    # * That folder is a local Git repository. You can pull, commit and push from there.
-    # * The binary will typically be at $GOPATH/bin/docker-machine-driver-hetzner
-    # * In the source directory $GOPATH/src/github.com/<yourAccount>/docker-machine-driver-hetzner
-    #   you may use go get to re-build the binary.
-    # * Note: when you build the driver from different repositories, e.g. from your fork
-    #   as well as github.com/jonasprogrammer/docker-machine-driver-hetzner,
-    #   the binary files generated by these builds are all called the same
-    #   and will hence override each other.
-
-    # Make the binary accessible to docker-machine
-    export GOPATH=$(go env GOPATH)
-    export GOBIN=$GOPATH/bin
-    export PATH="$PATH:$GOBIN"
-
-    # Make docker-machine output help including hetzner-specific options
-    docker-machine create --driver hetzner
 
 ## Usage
 
@@ -109,3 +80,30 @@ was used during creation.
 | `--hetzner-server-location`         | `HETZNER_LOCATION`                | - *(let Hetzner choose)*   |
 | `--hetzner-existing-key-path`       | `HETZNER_EXISTING_KEY_PATH`       | - *(generate new keypair)* |
 | `--hetzner-existing-key-id`         | `HETZNER_EXISTING_KEY_ID`         | 0 *(upload new key)*       |
+
+
+## Development
+
+Fork this repository, yielding `github.com/<yourAccount>/docker-machine-driver-hetzner`.
+
+    # Get the sources of your fork and build it locally
+    go get github.com/<yourAccount>/docker-machine-driver-hetzner
+
+    # * This integrates your fork into the $GOPATH (typically pointing at ~/go)
+    # * Your sources are at $GOPATH/src/github.com/<yourAccount>/docker-machine-driver-hetzner
+    # * That folder is a local Git repository. You can pull, commit and push from there.
+    # * The binary will typically be at $GOPATH/bin/docker-machine-driver-hetzner
+    # * In the source directory $GOPATH/src/github.com/<yourAccount>/docker-machine-driver-hetzner
+    #   you may use go get to re-build the binary.
+    # * Note: when you build the driver from different repositories, e.g. from your fork
+    #   as well as github.com/jonasprogrammer/docker-machine-driver-hetzner,
+    #   the binary files generated by these builds are all called the same
+    #   and will hence override each other.
+
+    # Make the binary accessible to docker-machine
+    export GOPATH=$(go env GOPATH)
+    export GOBIN=$GOPATH/bin
+    export PATH="$PATH:$GOBIN"
+
+    # Make docker-machine output help including hetzner-specific options
+    docker-machine create --driver hetzner