Update README.md

Author: piotrwitek

README.md

@@ -618,8 +618,8 @@ export const getTargetCurrencyRate = createSelector(
 # Extras
 
 ### tsconfig.json
-> Recommended setup for best benefits from type-checking, with support for JSX and ES2016 features.
-> `npm i tslib` - install [`tslib`](https://www.npmjs.com/package/tslib) dependency to externalize helper functions generated by transpiler and normally inlined in your modules to minimize bundle size
+> Recommended setup for best benefits from type-checking, with support for JSX and ES2016 features.  
+> Add [`tslib`](https://www.npmjs.com/package/tslib) to minimize bundle size: `npm i tslib` -  this will externalize helper functions generated by transpiler and otherwise inlined in your modules  
 ```js
 {
   "compilerOptions": {
@@ -664,9 +664,9 @@ export const getTargetCurrencyRate = createSelector(
 ```
 
 ### tslint.json
-> Recommended setup is to extend build-in preset `tslint:latest` (for all rules use `tslint:all`)  
+> Recommended setup is to extend build-in preset `tslint:latest` (for all rules use `tslint:all`).  
 > Add tslint react rules: `npm i -D tslint-react` https://github.com/palantir/tslint-react  
-> Amended some extended defaults for more flexibility  
+> Amended some extended defaults for more flexibility.  
 ```json
 {
   "extends": ["tslint:latest", "tslint-react"],
@@ -702,8 +702,8 @@ export const getTargetCurrencyRate = createSelector(
 ```
 
 ### Default and Named Module Exports
-> Most flexible solution is to use module folder pattern, because you can leverage both named and default import when you see fit.
-Using this solution you'll achieve better encapsulation for internal structure/naming refactoring without breaking your consumer code:
+> Most flexible solution is to use module folder pattern, because you can leverage both named and default import when you see fit.  
+Using this solution you'll achieve better encapsulation for internal structure/naming refactoring without breaking your consumer code:  
 ```ts
 // 1. in `components/` folder create component file (`select.tsx`) with default export:
 
@@ -728,7 +728,7 @@ import Select from '../components/select';
 ```
 
 ### Vendor Types Augmentation
-> Augmenting missing autoFocus Prop on `Input` and `Button` components in `antd` npm package (https://ant.design/)
+> Augmenting missing autoFocus Prop on `Input` and `Button` components in `antd` npm package (https://ant.design/).  
 ```ts
 declare module '../node_modules/antd/lib/input/Input' {
   export interface InputProps {
@@ -756,15 +756,15 @@ npm i -D @types/react @types/react-dom @types/react-redux
 ```
 
 ### - when to use `interface` and when `type` to behave consistently?
-> Use `type` when declaring simple object literal structs e.g. Component Props, Component State, Redux State, Redux Action.
-In other cases it's more flexible to use `interface` over `type` because interfaces can be implemented, extended and merged.
-Related `ts-lint` rule: https://palantir.github.io/tslint/rules/interface-over-type-literal/
+> Use `type` when declaring simple object literal structs e.g. Component Props, Component State, Redux State, Redux Action.  
+In other cases it's more flexible to use `interface` over `type` because interfaces can be implemented, extended and merged.  
+Related `ts-lint` rule: https://palantir.github.io/tslint/rules/interface-over-type-literal/  
 
 ### - should I use React.PropTypes?
-> No. In TypeScript it is completely unnecessary, you will get a much better free type checking and intellisense at compile time when declaring a "generic type" for component: `React.Component<{ myProp: string }, { myState: number}>`, this way you'll never get any runtime errors and get elegant way of describing component external API.
+> No. In TypeScript it is completely unnecessary, you will get a much better free type checking and intellisense at compile time when declaring a "generic type" for component: `React.Component<{ myProp: string }, { myState: number}>`, this way you'll never get any runtime errors and get elegant way of describing component external API.  
 
 ### - how to best declare component instance properties?
-> Don't use old-school React class constructors way, prefer to use Property Initializers (first class support in TypeScript)
+> Don't use old-school React class constructors way, prefer to use Property Initializers (first class support in TypeScript).  
 ```tsx
 class MyComponent extends React.Component<Props, State> {
   // default props using Property Initializers
@@ -782,7 +782,7 @@ class MyComponent extends React.Component<Props, State> {
 ```
 
 ### - how to best declare component handler functions?
-> Don't use old-school class methods and function bind way, prefer to use Class Fields with arrow functions (first class support in TypeScript) 
+> Don't use old-school class methods and function bind way, prefer to use Class Fields with arrow functions (first class support in TypeScript)  
 ```tsx
 class MyComponent extends React.Component<Props, State> {
 // handlers using Class Fields with arrow functions