replacing code

Author: hmmgo

.editorconfig

@@ -4,3 +4,5 @@ enabled:
   - phpdoc_order
   - phpdoc_separation
   - unalign_double_arrow
+
+linting: true

.gitattributes

@@ -1,6 +1,8 @@
 # Contributing
 
-Contributions are welcome.
+Contributions are **welcome** and will be fully **credited**.
+
+Please read and understand the contribution guide before creating an issue or pull request.
 
 ## Etiquette
 
@@ -36,14 +38,18 @@ Before submitting a pull request:
 
 ## Requirements
 
-- If your contribution changes the look of the generated documentation in some way, please include "before" and "after" screenshots in your pull request. 
+If the project maintainer has any additional requirements, you will find them listed here.
 
-- Add a description to your pull request so the reviewer knows what to look out for before looking through your changes
+- **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)** - The easiest way to apply the conventions is to install [PHP Code Sniffer](http://pear.php.net/package/PHP_CodeSniffer).
 
 - **Add tests!** - Your patch won't be accepted if it doesn't have tests.
 
 - **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.
 
+- **Consider our release cycle** - We try to follow [SemVer v2.0.0](http://semver.org/). Randomly breaking public APIs is not an option.
+
 - **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.
 
+- **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.
+
 **Happy coding**!