Introduction metadata parser

README.md

@@ -10,14 +10,16 @@
 
 # music-metadata-browser
 
-[music-metadata-borwser](https://github.com/Borewit/music-metadata-browser) is a node module, designed to run on the browser.
-Because modules don't run directly in the browser you need a _module bundler_, like [webpack](https://webpack.js.org).
+[music-metadata-borwser](https://github.com/Borewit/music-metadata-browser) is a metadata parser, supporting virtual any audio format and tag header around.
+
+[music-metadata-borwser](https://github.com/Borewit/music-metadata-browser) is a node module, designed for modern browser applications.
+Because modules don't run directly in the browser you need a _module bundler_, like [Webpack](https://webpack.js.org) or [Parcel](https://parceljs.org/).
 The _module bundler_ turns the modules (dependencies), together with you application code, into a static asset (typically a minified JavaScript file).
 The output of _module bundler_ is compatible and optimized for execution by a web browser.
 
 Integration with React or Angular should ne be a problem:
-* [example project with React](https://github.com/Borewit/music-metadata-react)
-* [example project with Angular](https://github.com/Borewit/audio-tag-analyzer)
+*   [example project using React framework](https://github.com/Borewit/music-metadata-react)
+*   [example project using Angular framework](https://github.com/Borewit/audio-tag-analyzer)
 
 If you prefer to parse files or streams server (node.js) side, you should use [music-metadata](https://github.com/Borewit/music-metadata) instead.