[doc] fixes for CONTRIBUTING

Author: simogasp

CONTRIBUTING.md

@@ -6,16 +6,15 @@ we recommend you to read the [code of conduct](CODE_OF_CONDUCT.md).
 
 ## Contributing Workflow
 
-The contributing workflow relies on [Github Pull Requests](https://help.github.com/articles/using-pull-requests/).
+The contributing workflow relies on [GitHub Pull Requests](https://help.github.com/articles/using-pull-requests/).
 
 1. If it is an important change, we recommend you to discuss it on the mailing-list before starting implementation.
-  This ensure that the development is aligned with other
-development already started and will be efficiently integrated.
+   This ensures that the development is aligned with other development already started and will be efficiently integrated.
 
 2. Create the corresponding issues.
 
 3. Create a branch and start a PR starting by [WIP], like "[WIP] My new feature" so everyone can follow the development.
-  Explain the implementation in the PR description with links to issues.
+   Explain the implementation in the PR description with links to issues.
 
 4. Implement the new feature(s). Add unit test if needed.
 One feature per PR is ideal for review, but linked features can be part of the same PR.