fix($merge): rolling back

README.md

@@ -648,6 +648,7 @@ If what you want is full-on compilation `chunk` objects (and any information it
 
 ## Contributing
 
+
 We use [commitizen](https://github.com/commitizen/cz-cli), so run `npm run cm` to make commits. A command-line form will appear, requiring you answer a few questions to automatically produce a nicely formatted commit. Releases, semantic version numbers, tags, changelogs and publishing to NPM will automatically be handled based on these commits thanks to [semantic-release](https://github.com/semantic-release/semantic-release). Be good.
 
 
@@ -657,4 +658,4 @@ Reviewing a module's tests are a great way to get familiar with it. It's direct
 
 Below is a screenshot of this module's tests running in [Wallaby](https://wallabyjs.com) *("An Integrated Continuous Testing Tool for JavaScript")* which everyone in the React community should be using. It's fantastic and has taken my entire workflow to the next level. It re-runs your tests on every change along with comprehensive logging, bi-directional linking to your IDE, in-line code coverage indicators, **and even snapshot comparisons + updates for Jest!** I requestsed that feature by the way :). It's basically a substitute for live-coding that inspires you to test along your journey.
 
-![require-universal-module wallaby tests screenshot](./tests-screenshot.png)
+![require-universal-module wallaby tests screenshot](./tests-screenshot.png)