Added Coding Style explanation

Author: Tristán

CONTRIBUTING.md

@@ -13,6 +13,7 @@ Please note that we have a code of conduct that we need to follow moving forward
 We use github to host code, to track issues and feature requests, as well as accept pull requests.
 
 ## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+
 Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
 
 1. Fork the repo and create your branch from `main`.
@@ -32,7 +33,7 @@ We use GitHub issues to track public bugs. Report a bug by [opening a new issue]
 ## Write bug reports with detail, background, and sample code
 [This is an example](http://stackoverflow.com/q/12488905/180626) of a bug report I wrote, and I think it's not a bad model. Here's [another example from Craig Hockenberry](http://www.openradar.me/11905408), an app developer whom I greatly respect.
 
-**Great Bug Reports** tend to have:
+*Great Bug Reports* tend to have:
 
 - A quick summary and/or background
 - Steps to reproduce
@@ -42,9 +43,10 @@ We use GitHub issues to track public bugs. Report a bug by [opening a new issue]
 - What actually happens
 - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
 
-People *love* thorough bug reports. I'm not even kidding.
+People love thorough bug reports. I'm not even kidding.
 
 ## Use a Consistent Coding Style
+You can check [here](https://docs.python-guide.org/writing/style/) for more information about a good coding style. It's important to respect and follow it up to keep good practices. If it's difficult for you please, take in consideration use `flake8`
 
 ## License
 By contributing, you agree that your contributions will be licensed under its MIT License.