From b7ea06614d3c69b19854abcbf535ce94da642138 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Fri, 1 May 2015 17:01:59 -0700 Subject: [PATCH] Update 2015-05-01-graphql-introduction.md typo fix --- docs/_posts/2015-05-01-graphql-introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_posts/2015-05-01-graphql-introduction.md b/docs/_posts/2015-05-01-graphql-introduction.md index e9e9862500..779546d958 100644 --- a/docs/_posts/2015-05-01-graphql-introduction.md +++ b/docs/_posts/2015-05-01-graphql-introduction.md @@ -69,7 +69,7 @@ Obviously GraphQL is not the first system to manage client-server interactions. ### 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-identity* as REST, rather than systems which are formally 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.