Merge aa0ca70 into 85e0946

README.md

@@ -19,14 +19,14 @@ cd YOURFOLDERNAME
 npm install
 ```
 
-**Start coding!** `package.json` and entry files are already set up for you, so don't worry about linking to your main file, typings, etc. Just keep those files with the same names.
+**Start coding!** `package.json` and entry files are already set up for you, so don't worry about linking to your main file, typings, etc. Just keep those files with the same name.
 
 ### Features
 
- - Zero-setup. After running `npm install` things will be setup for you :wink:
- - **[RollupJS](https://rollupjs.org/)** for multiple optimized bundles following the [standard convention](http://2ality.com/2017/04/setting-up-multi-platform-packages.html) and [Tree-shaking](https://alexjoverm.github.io/2017/03/06/Tree-shaking-with-Webpack-2-TypeScript-and-Babel/).
+ - Zero-setup. After running `npm install` things will setup for you :wink:
+ - **[RollupJS](https://rollupjs.org/)** for multiple optimized bundles following the [standard convention](http://2ality.com/2017/04/setting-up-multi-platform-packages.html) and [Tree-shaking](https://alexjoverm.github.io/2017/03/06/Tree-shaking-with-Webpack-2-TypeScript-and-Babel/)
  - Tests, coverage and interactive watch mode using **[Jest](http://facebook.github.io/jest/)**
- - **[Prettier](https://github.com/prettier/prettier)** and **[TSLint](https://palantir.github.io/tslint/)** for code formatting and consistency.
+ - **[Prettier](https://github.com/prettier/prettier)** and **[TSLint](https://palantir.github.io/tslint/)** for code formatting and consistency
  - **Docs automatic generation and deployment** to `gh-pages`, using **[TypeDoc](http://typedoc.org/)**
  - Automatic types `(*.d.ts)` file generation
  - **[Travis](https://travis-ci.org)** integration and **[Coveralls](https://coveralls.io/)** report
@@ -36,12 +36,12 @@ npm install
 
 On library development, one might want to set some peer dependencies, and thus remove those from the final bundle. You can see in [Rollup docs](https://rollupjs.org/#peer-dependencies) how to do that.
 
-The good news is here is setup for you, you only must include the dependency name in `external` property within `rollup.config.js`. For example, if you wanna exclude `lodash`, just write there `external: ['lodash']`.
+The good news is, the setup is here for you, you must only include the dependency name in `external` property within `rollup.config.js`. For example, if you want to exclude `lodash`, just write there `external: ['lodash']`.
 
 ### NPM scripts
 
  - `npm t`: Run test suite
- - `npm start`: Runs `npm run build` in watch mode
+ - `npm start`: Run `npm run build` in watch mode
  - `npm run test:watch`: Run test suite in [interactive watch mode](http://facebook.github.io/jest/docs/cli.html#watch)
  - `npm run test:prod`: Run linting and generate coverage
  - `npm run build`: Generage bundles and typings, create docs
@@ -50,10 +50,10 @@ The good news is here is setup for you, you only must include the dependency nam
 
 ### Automatic releases
 
-If you'd like to have automatic releases with Semantic Versioning, follow these simple steps.
+If you'd like to have automatic releases with Semantic Versioning, follow these simple steps-
 
 _**Prerequisites**: you need to create/login accounts and add your project to:_
- - npm
+ - [npm](https://www.npmjs.com/)
  - Travis
  - Coveralls
 
@@ -65,7 +65,7 @@ npm run semantic-release-prepare
 
 Follow the console instructions to install semantic release run it (answer NO to "Generate travis.yml").
 
-_Note: make sure you've setup `repository.url` in your `package.json` file_
+_Note: make sure you've setup `repository.url` in your `package.json` file_ 
 
 ```bash
 npm install -g semantic-release-cli
@@ -75,15 +75,15 @@ semantic-release setup
 
 From now on, you'll need to use `npm run commit`, which is a convenient way to create conventional commits.
 
-Automatic releases are possible thanks to [semantic release](https://github.com/semantic-release/semantic-release), which publishes your code automatically on github and npm, plus generates automatically a changelog. This setup is highly influenced by [Kent C. Dodds course on egghead.io](https://egghead.io/courses/how-to-write-an-open-source-javascript-library)
+Automatic releases are possible thanks to [semantic release](https://github.com/semantic-release/semantic-release), which publishes your code automatically on [github](https://github.com/) and [npm](https://www.npmjs.com/), plus generates automatically a changelog. This setup is highly influenced by [Kent C. Dodds course on egghead.io](https://egghead.io/courses/how-to-write-an-open-source-javascript-library)
 
 ### Git Hooks
 
 There is already set a `precommit` hook for formatting your code with Prettier :nail_care:
 
 By default, there are 2 disabled git hooks. They're set up when you run the `npm run semantic-release-prepare` script. They make sure:
  - You follow a [conventional commit message](https://github.com/conventional-changelog/conventional-changelog)
- - Your build is not gonna fail in [Travis](https://travis-ci.org) (or your CI server), since it's runned locally before `git push`
+ - Your build is not going to fail in [Travis](https://travis-ci.org) (or your CI server), since it's runned locally before `git push`
 
 This makes more sense in combination with [automatic releases](#automatic-releases)
 
@@ -102,10 +102,10 @@ import "core-js/fn/promise"
 ...
 ```
 
-#### What is `npm install` doing the first time runned?
+#### What is `npm install` doing on first run?
 
 It runs the script `tools/init` which sets up everything for you. In short, it:
- - Configures RollupJS for the build, which creates the bundles.
+ - Configures RollupJS for the build, which creates the bundles
  - Configures `package.json` (typings file, main file, etc)
  - Renames main src and test files