Use JSON:API instead of JSON API in the read me and contributing files

kocsismate · kocsismate · commit 4fe1ec118863 · 2018-10-31T16:13:15.000+01:00
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -4,16 +4,16 @@
 Our issue tracker can always be used to address internal inconsistencies within
 the current specification, or updates to the website. Beyond this, we try to
 limit discussions to those which focus on problems that will be dealt with in
-the next version of JSON API. A roadmap can be found on the [about] section of
+the next version of JSON:API. A roadmap can be found on the [about] section of
 our website.
 
 The ideal world we are shooting for is an empty issue tracker on release days.
 
 ## Discussion Forum
 > http://discuss.jsonapi.org
 
-Our discussion forum is where general conversations about JSON API should take
+Our discussion forum is where general conversations about JSON:API should take
 place. Ideas for new extensions and questions about how to correctly implement
-or consume an API that adheres to the JSON API specification belong here.
+or consume an API that adheres to the JSON:API specification belong here.
 
 [about]: http://jsonapi.org/about
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-JSON API
+JSON:API
 ========
 
 Documentation for the [application/vnd.api+json media
@@ -38,6 +38,6 @@ when changes are pushed to the `gh-pages` branch.
 Archive
 -------
 
-older versions of the JSON-API documentations
+older versions of the JSON:API documentations
 
 * RC3 - http://jsonapi-rc3.herokuapp.com/
