docs: restructure

Author: saschanaz

README.md

@@ -1,7 +1,17 @@
 # types-web
 
+Get types for the latest web APIs as soon as they become widely available!
+
 ![An example showing types for MediaSession and MediaRecorder](docs/mediasession.png)
 
+[The default types generator](https://github.com/microsoft/TypeScript-DOM-lib-generator/) for TypeScript requires manual review for every update, and thus does not provide types for every latest API in a timely manner. `types-web` solves this issue by deploying automation by following tools:
+
+  * [`@mdn/browser-compat-data`](https://www.npmjs.com/package/@mdn/browser-compat-data) provides which features are supported by which browsers, so that undersupported features can be disabled automatically.
+  * [`browser-specs`](https://www.npmjs.com/package/browser-specs) provides a full list of web specs, so that every latest feature can be covered.
+  * [`webref`](https://github.com/w3c/webref) provides IDL code from the specs, so that the features can be properly typed.
+
+See how many types have been added in the [changelog](CHANGELOG.md).
+
 ## How to use
 
 1. Install the package by [`npm i types-web`](https://www.npmjs.com/package/types-web).
@@ -25,18 +35,6 @@
     }
     ```
 
-## How is this different from [TypeScript-DOM-lib-generator](https://github.com/microsoft/TypeScript-DOM-lib-generator/)?
-
-`types-web` tries automating everything with a set of relevant tools to reduce the hassle of manual reviewing:
-
-  * [`@mdn/browser-compat-data`](https://www.npmjs.com/package/@mdn/browser-compat-data) provides which features are supported by which browsers, so that undersupported features can be disabled automatically.
-  * [`browser-specs`](https://www.npmjs.com/package/browser-specs) provides a full list of web specs, so that every latest feature can be covered.
-  * [`webref`](https://github.com/w3c/webref) provides IDL code from the specs, so that the features can be properly typed.
-
-But so far some things still need manual modification and that is done by files in `inputfiles/` directory.
-
-See how many types have been added in the [changelog](CHANGELOG.md).
-
 ## Why not `@types`?
 
 To maintain the package by myself without waiting for external reviews.
@@ -47,6 +45,10 @@ A feature needs to be supported by more than two major browser engines to be inc
 
 If the condition is met but still is not available here, please [file an issue](https://github.com/saschanaz/types-web/issues/new).
 
+## Is it fully automated?
+
+Not yet. A small part of things still needs manual modification, which is done by files in `inputfiles/` directory.
+
 ## Build Instructions
 
 * To get things setup: