Update links and naming in contributing.md

Signed-off-by: Daniel Izquierdo Cortazar <[email protected]>

Author: dicortazar

CONTRIBUTING.md

@@ -2,19 +2,16 @@
 
 This book is built as a [Gitbook book](https://gitbook.com). This is written
 using [Markdown syntax](https://www.gitbook.com/book/gitbookio/markdown/).
-This is maintained under the [Daniel Izquierdo's GitHub account](https://github.com/dicortazar) in the
-[Managing Inner Source Projects repository](https://github.com/dicortazar/managing-inner-source-projects).
+This is maintained under the [InnerSource Commons' GitHub account](https://github.com/innersourcecommons) in the
+[Managing Inner Source Projects repository](https://github.com/innersourcecommons/managing-inner-source-projects).
 
 Thus you can follow the usual contribution process in GitHub through
 [Pull Requests](https://help.github.com/articles/about-pull-requests/). You can
 see for instance the pull requests open and closed at this point in time and for
-this repository at https://github.com/dicortazar/managing-inner-source-projects/pulls .
+this repository at https://github.com/innersourcecommons/managing-inner-source-projects/pulls .
 
 If you want to share an idea, comment or feature request, you can also open an issue
-in the [GitHub issues tracking for this repository](https://github.com/dicortazar/managing-inner-source-projects/issues).
-
-There is also another possibility and this is using the GitBook interface.
-You can [open discussions there](https://www.gitbook.com/book/dicortazar/managing-inner-source-projects/discussions).
+in the [GitHub issues tracking for this repository](https://github.com/innersourcecommons/managing-inner-source-projects/issues).
 
 Please be aware that all of your contributions will be opened by default and
 that those will be licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
@@ -23,4 +20,3 @@ that those will be licensed under [CC BY-SA 4.0](https://creativecommons.org/lic
 
 When using titles in Markdown, use # for main title, ## for the second header title, etc. It's just to follow the same style :).
 
-When mentioning inner source, we tend to use lower case and separated by a blank space as in open source. As an example, these are not correct cases: Inner Source, Inner source, InnerSource, innersource, inner sourcing. Again this is a matter of following a similar style.