From 5bdd8f8640bb423dd8311bb45f6f4fce18e02daa Mon Sep 17 00:00:00 2001 From: Julien Bordellier Date: Sat, 20 Jun 2015 16:50:01 +0200 Subject: [PATCH] Update graphql-introduction.html There was a tiny mistake line 170 s/and/an/ :) --- blog/2015/05/01/graphql-introduction.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2015/05/01/graphql-introduction.html b/blog/2015/05/01/graphql-introduction.html index 51d9de26c0..b2ada378be 100644 --- a/blog/2015/05/01/graphql-introduction.html +++ b/blog/2015/05/01/graphql-introduction.html @@ -167,7 +167,7 @@

REST #

REST an acronym for Representational State Transfer, which is an architectural style rather than a formal protocol. There is actually much debate about what exactly REST is and is not. We wish to avoid such debates. We are interested in the typical attributes of systems that self-identify as REST, rather than systems which are formally REST.

-

Objects in a typical REST system are addressable by URI and interacted with using verbs in the HTTP protocol. An HTTP GET to a particular URI fetches and object and returns a server-specified set of fields. An HTTP PUT edits an object; an HTTP DELETE deletes an object; and so on.

+

Objects in a typical REST system are addressable by URI and interacted with using verbs in the HTTP protocol. An HTTP GET to a particular URI fetches an object and returns a server-specified set of fields. An HTTP PUT edits an object; an HTTP DELETE deletes an object; and so on.

We believe there are a number of weakness in typical REST systems, ones that are particularly problematic in mobile applications: