From 2d9ded36c572a4d6dcb7069b8f87f4b509f381bc Mon Sep 17 00:00:00 2001 From: jen729w Date: Fri, 7 Sep 2018 17:47:44 +1000 Subject: [PATCH 1/2] Update BestPractice-Introduction.md Typo fix. --- site/learn/BestPractice-Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/learn/BestPractice-Introduction.md b/site/learn/BestPractice-Introduction.md index 6409f44ce2..586baf3f5f 100644 --- a/site/learn/BestPractice-Introduction.md +++ b/site/learn/BestPractice-Introduction.md @@ -16,7 +16,7 @@ Following are brief descriptions of some of the more common best practices and o ### HTTP -GraphQL is typically served over HTTP via a single endpoint which expresses the full set of capabilities of the service. This is in contrast to REST APIs which expose a suite of URLs each of which expose a single resource. While GraphQL could be used alongside a suite of resource URLs, this can make it harder to use with tools like GraphiQL. +GraphQL is typically served over HTTP via a single endpoint which expresses the full set of capabilities of the service. This is in contrast to REST APIs which expose a suite of URLs each of which expose a single resource. While GraphQL could be used alongside a suite of resource URLs, this can make it harder to use with tools like GraphQL. Read more about this in [Serving over HTTP](/learn/serving-over-http/). From 334b9eb14879d9d97e98a9599dc2a346c908c2e6 Mon Sep 17 00:00:00 2001 From: jen729w Date: Sat, 8 Sep 2018 09:49:29 +1000 Subject: [PATCH 2/2] GraphiQL is actually a thing! Corrected and linked --- site/learn/BestPractice-Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/learn/BestPractice-Introduction.md b/site/learn/BestPractice-Introduction.md index 586baf3f5f..2432c01ded 100644 --- a/site/learn/BestPractice-Introduction.md +++ b/site/learn/BestPractice-Introduction.md @@ -16,7 +16,7 @@ Following are brief descriptions of some of the more common best practices and o ### HTTP -GraphQL is typically served over HTTP via a single endpoint which expresses the full set of capabilities of the service. This is in contrast to REST APIs which expose a suite of URLs each of which expose a single resource. While GraphQL could be used alongside a suite of resource URLs, this can make it harder to use with tools like GraphQL. +GraphQL is typically served over HTTP via a single endpoint which expresses the full set of capabilities of the service. This is in contrast to REST APIs which expose a suite of URLs each of which expose a single resource. While GraphQL could be used alongside a suite of resource URLs, this can make it harder to use with tools like [GraphiQL](https://github.com/graphql/graphiql). Read more about this in [Serving over HTTP](/learn/serving-over-http/).