Merge branches 'docs' and 'docs' of github.com:AceTheCreator/communit…

…y into docs

docs/README.md

@@ -1,3 +1,3 @@
-# Community Documetation
+## Community Documentation
 
-The community documentation directory helps the community maintains collaboratively a collection of helpful community-related documentations from how to start contributing to AsyncAPI to how it leverages other technologies to build and enhance it's software.
+The community documentation directory helps the community collaboratively maintain a collection of helpful community-related documentation. From becoming an AsyncAPI contributor to becoming a TSC member, and beyond.

docs/how-changes-in-the-spec-are-introduced.md

@@ -1,6 +1,5 @@
-**
 
-# How spec changes are introduced
+## How spec changes are introduced
 AsyncAPI Initiative always concentrates on the problems rather than the solution. This is because you are generally rather single-minded when you already have a solution in mind to a problem instead of fully diving into the issue, seeing alternatives, and finding the best solution. 
 
 ### RFCs & champions
@@ -49,7 +48,7 @@ This part of the lifecycle aims to describe all details of the process so that a
 - The coordinator keeps a closed watch on what is merged, documents it in release notes, and engages contributors and maintainers of the spec to collaborate on a release.
 - Maintainers trigger release when ready, release notes are published, and the world of open source won again.
 
-You can learn more about the release process [here](https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md#what). 
+Learn more about the [release process](https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md#what). 
 
 ### Release process visual
 The image below visualizes the whole process of how changes are introduced to the spec in a single glance.