Updates readme

Author: arqex

README.md

@@ -1,11 +1,11 @@
 # react-dom-instance
 [![npm version](https://badge.fury.io/js/react-dom-instance.svg)](https://badge.fury.io/js/react-dom-instance) [![CircleCI](https://circleci.com/gh/arqex/react-dom-instance.svg?style=shield)](https://circleci.com/gh/arqex/react-dom-instance) [![Codecov Coverage](https://img.shields.io/codecov/c/gh/arqex/react-dom-instance)](https://codecov.io/gh/arqex/react-dom-instance/)
 
-When using `react-dom`'s `findDOMNode()` we get the HTML node generated by a react component instance.
+When using [`react-dom`](https://es.reactjs.org/docs/react-dom.html#finddomnode)'s `findDOMNode()` we get the HTML node generated by a react component instance.
 
 `react-dom-instance`'s `findInstance()` goes in the opposite direction: from an HTML node, we get the react component instance that generated it.
 
-** Only React v16 and higher is supported**
+**Only React v16 and higher is supported**
 
 ## How it works
 
@@ -50,7 +50,10 @@ Functional components don't have instances, so using `findInstance` with one DOM
 
 We can pass some options in order to retrieve the wanted instance from the DOM node:
 
+### Options
+
 **componentName**
+
 Sometimes there are more than one component instance linked to a DOM node. For example, when a component `render` method returns another component, or when using higher order components.
 
 In those cases we can use `componentName` to tell `findInstace` what type of component instance we want:
@@ -75,6 +78,7 @@ findInstance( domNode ); // ChildComponent instance
 ```
 
 **maxIteration**
+
 When there are more than one component linked to the same DOM node, `findInstance` navigates recursively through the react fibers looking for the instance of the right component we want. To make this process fast and avoid infinite loops there is a maximum number of iterations that the algorithm does until it decides that the instance can't be found. By default `findInstance` iterates `4` times looking for the instance and return `false` after not finding it.
 
 If you have a DOM node with a lot of instances linked and know that more iterations are needed to find the one you want, you can pass `maxIteration` as an option with a bigger number:
@@ -85,7 +89,7 @@ findInstance( domNode, {componentName: 'MyComponent', maxIterations: 6} );
 
 ## Usage with react testing library
 
-This library was thought as a helper for testing with react testing library: sometimes it is useful to access to the component instances in order to create tests. 
+This library was thought as a helper for testing with [react testing library](https://github.com/testing-library/react-testing-library): sometimes it is useful to access to the component instances in order to create tests. 
 
 To make the integration easier, `findInstance` accepts the container returned by react testing library and know how to extract the instance linked to it:
 
@@ -112,11 +116,10 @@ it('should say hello', () => {
 });
 ```
 
-
 ---
 
-Here's [the changelog](CHANGELOG.md)
-[MIT Licensed](LICENSE)
+* Here's [the changelog](CHANGELOG.md)
+* [MIT Licensed](LICENSE)