Update docs

Author: scriptcoded

CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contribution guidelines
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. This avoids extra work for both you and us.
+
+## Pull Request Process
+
+1. Fork the repo and create your branch from `master`.
+1. Implement your changes.
+1. If applicable to your changes, add, remove or update tests.
+1. If applicable to your change, update the readme accordingly.
+1. Run the tests and make sure they pass using `npm run test`. This will also run the linter.
+1. Create a new pull request!
+
+## We use the MIT licence
+
+You can read our licence [here](https://github.com/scriptcoded/sql-highlight/blob/master/LICENSE).
+
+## License
+By contributing, you agree that your contributions will be licensed under its MIT License.

README.md

@@ -21,12 +21,10 @@ npm install sql-highlight
 ```
 
 ## Usage
-> Note that we're using ES6 import statements here. Usage with `require` works
-> just as well.
 
 **In its most basic form:**
 ```js
-import { highlight } from 'sql-highlight'
+const { highlight } = require('sql-highlight')
 
 const sqlString = "SELECT `id`, `username` FROM `users` WHERE `email` = '[email protected]'"
 
@@ -37,7 +35,7 @@ console.log(highlighted)
 
 **Output:**
 
-![Screenshot 1](screenshot1.png)
+![Screenshot](screenshot.png)
 
 **HTML mode:**
 
@@ -91,11 +89,15 @@ The following options may be passed to the `highlight` function.
 
 ## Contributing
 
-1. Fork it (<https://github.com/scriptcoded/sql-highlight/fork>)
-2. Create your feature branch (`git checkout -b feature/fooBar`)
-3. Commit your changes (`git commit -am 'Add some fooBar'`)
-4. Push to the branch (`git push origin feature/fooBar`)
-5. Create a new Pull Request
+See the [contribution guidelines](CONTRIBUTING.md).
+
+## Tests
+
+We use [Jest](https://jestjs.io/) for running our tests. The test suite can be run by running `npm run test`. This will run both Jest and ESLint.
+
+## Code style
+
+We use [ESLint](https://eslint.org/) for making sure that our code remains pretty and consistent throughout the project. If your editor doesn't automatically pick up our config you can lint the code using `npm run lint`.
 
 ## Additional information