Fix erros in .md files

.github/ISSUE_TEMPLATE/bug_report.md

@@ -21,15 +21,15 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+-  OS: (e.g. iOS)
+-  Browser (e.g. chrome, safari)
+-  Version (e.g. 22)
 
 **Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
+-  Device: (e.g. iPhone6)
+-  OS: (e.g. iOS8.1)
+-  Browser (e.g. stock browser, safari)
+-  Version (e.g. 22)
 
 **Additional context**
 Add any other context about the problem here.

CONTRIBUTING.md

@@ -2,11 +2,11 @@
 
 We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
 
-- Reporting a bug
-- Discussing the current state of the code
-- Submitting a fix
-- Proposing new features
-- Becoming a maintainer
+-   Reporting a bug
+-   Discussing the current state of the code
+-   Submitting a fix
+-   Proposing new features
+-   Becoming a maintainer
 
 ## We Develop with Github
 
@@ -16,12 +16,12 @@ We use github to host code, to track issues and feature requests, as well as acc
 
 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 `master`.
-2. If you've added code that should be tested, add tests (aiming at 100% coverage).
-3. If you've changed APIs, update the documentation.
-4. Ensure the test suite passes.
-5. Make sure your code lints.
-6. Issue that pull request!
+1.  Fork the repo and create your branch from `master`.
+2.  If you've added code that should be tested, add tests (aiming at 100% coverage).
+3.  If you've changed APIs, update the documentation.
+4.  Ensure the test suite passes.
+5.  Make sure your code lints.
+6.  Issue that pull request!
 
 ## Any contributions you make will be under the MIT Software License
 
@@ -37,8 +37,8 @@ Request a feature by [opening a new issue](https://github.com/boristane/stat-met
 
 ## Use a Consistent Coding Style
 
-- Make sure you're using our `.editorconfig` file
-- Make sure you're running `eslint`. You can check the integration with your editor in the [official documentation](https://eslint.org/docs/user-guide/integrations)
+-   Make sure you're using our `.editorconfig` file
+-   Make sure you're running `eslint`. You can check the integration with your editor in the [official documentation](https://eslint.org/docs/user-guide/integrations)
 
 ## License