Update README.md

README.md

@@ -11,7 +11,7 @@ So, imagine you are a frontend developer.
 
 And you want to write a javascript library, that other people will use in their projects.
 
-You want to make your library hugely reusable, maintainable and future-proof.
+You want to make your library hugely reusable, maintainable and future-proof.  
 But at the same time you obviously want to use the latest and coolest technologies:
 
  * ES6 features
@@ -20,7 +20,7 @@ But at the same time you obviously want to use the latest and coolest technologi
  * Measuring test coverage (just in case they ask)
  * Code quality checks
 
-And you do not want to force other developers to **rewrite** or **reconfigure** their projects.
+And you do not want to force other developers to **rewrite** or **reconfigure** their projects.  
 So you will need to support these tools:
 
 * RequireJS
@@ -31,7 +31,7 @@ So you will need to support these tools:
 * bower
 * jspm
 
-... and make the library useful for isomorphic apps (those written for both NodeJS and browser)...
+... and make the library useful for isomorphic apps (those written for both NodeJS and browser)...  
 ... and let those people who love global variables to use your library...
 
 **Sounds too complex?**
@@ -40,10 +40,10 @@ So you will need to support these tools:
 
 That's why we have created this library!
 
-It will allow you to build bulletproof frontend libraries, which can be used with all latest technologies (ES6, jspm, systemjs) and some older ones (CommonJS, AMD, UMD, npm, bower, ...).
+It will allow you to build **bulletproof frontend libraries**, which can be used with all latest technologies (ES6, jspm, systemjs) and some older ones (CommonJS, AMD, UMD, npm, bower, ...).
 
 Here is some docs to proceed:
 
 * [I want to know what cool things are inside!](./docs/inside.md)
 * [How do I start with that stuff?](./docs/start.md)
-* [How can I contribute?](./CONTRIBUTING.md)
+* [How can I contribute?](./CONTRIBUTING.md)