Rearrange and extend readme.

Author: atombender

README.md

@@ -2,6 +2,47 @@
 
 This tool generates Go data types and structs that corresponds to definitions in the schema, along with unmarshaling code that validates the input JSON according to the schema's validation rules.
 
+## Installing
+
+* **Binary install**: Get a release [here](https://github.com/atombender/go-jsonschema/releases).
+
+* **From source**: Go 1.11 or later, with Go modules enabled, is advisable in order to get the right dependencies. To install:
+
+```shell
+$ go get github.com/atombender/go-jsonschema/...
+$ go install github.com/atombender/go-jsonschema/cmd/gojsonschema
+```
+
+## Usage
+
+At its most basic:
+
+```shell
+$ gojsonschema -p main schema.json
+```
+
+This will write a Go source file to standard output, declared under the package `main`.
+
+You can generate code for multiple schemas in the same invocation, optionally writing to different files inside different packages:
+
+```shell
+$ gojsonschema \
+  --schema-package=https://example.com/schema1=github.com/myuser/myproject \
+   --schema-output=https://example.com/schema1=schema1.go \
+  --schema-package=https://example.com/schema2=github.com/myuser/myproject/stuff \
+   --schema-output=https://example.com/schema2=stuff/schema2.go \
+  schema1.json schema2.json
+```
+
+This will create `schema1.go` (declared as `package myproject`) and `stuff/schema2.go` (declared as `package stuff`). If `schema1.json` refers to `schema2.json` or vice versa, the two Go files will import the other package that it depends on. Note the flag format:
+
+```
+--schema-package=https://example.com/schema1=github.com/myuser/myproject \
+                 ^                           ^
+                 |                           |
+                 schema $id                  full import URL
+```
+
 ## Status
 
 While not finished, go-jsonschema can be used today. Aside from some minor features, only specific validations remain to be fully implemented.
@@ -80,45 +121,6 @@ While not finished, go-jsonschema can be used today. Aside from some minor featu
     - [ ] JSON pointers
     - [ ] Regex
 
-## Usage
-
-At its most basic:
-
-```shell
-$ gojsonschema -p main schema.json
-```
-
-This will write a Go source file to standard output, declared under the package `main`.
-
-You can generate code for multiple schemas in the same invocation, optionally writing to different files inside different packages:
-
-```shell
-$ gojsonschema \
-  --schema-package=https://example.com/schema1=github.com/myuser/myproject \
-   --schema-output=https://example.com/schema1=schema1.go \
-  --schema-package=https://example.com/schema2=github.com/myuser/myproject/stuff \
-   --schema-output=https://example.com/schema2=stuff/schema2.go \
-  schema1.json schema2.json
-```
-
-This will create `schema1.go` (declared as `package myproject`) and `stuff/schema2.go` (declared as `package stuff`). If `schema1.json` refers to `schema2.json` or vice versa, the two Go files will import the other package that it depends on. Note the flag format:
-
-```
---schema-package=https://example.com/schema1=github.com/myuser/myproject \
-                 ^                           ^
-                 |                           |
-                 schema $id                  full import URL
-```
-
-## Installing
-
-Requires Go 1.11 or later, with Go modules enabled. To install:
-
-```shell
-$ go get github.com/atombender/go-jsonschema/...
-$ go install github.com/atombender/go-jsonschema/cmd/gojsonschema
-```
-
 ## License
 
-BSD license. See `LICENSE` file.
+MIT license. See `LICENSE` file.