Minor improvements to the REST principles chapter

Well written summary!
While reading through, I made some clarifications (from my POV).

In addendum, see [a post of mine clarifying REST concepts](http://hyperrest.github.io/2013-03-30-rest-api-concepts/#content). To a great extent, I think it still is a good analogy (1.5y after).
I see. Fielding is doing an overview of styles though.
In your summary, the focus is on rest as a client-server arch. The granularity is smaller and that's what lead me.

As for the linking - links may be broken but the server via HATEOAS decided there is a link.

Anyways, dont put time into this. It's a good crashcourse, people should read the thesis :)
Or even better - abstract it in a tool. Opinionated, sure, but irrelevant as long as it does not limit the style

PS: Looking forward to your EUC REST client talk although i predict where you are going :)

> On 09 Jun 2014, at 10:13, Loïc Hoguin <notifications@github.com> wrote:
> 
> In guide/rest_principles.md:
> 
> > @@ -21,10 +21,10 @@ REST architecture
> >  REST is a *client-server* architecture. The client and the server
> >  both have a different set of concerns. The client cares about how
> >  it will display information to the user. The server cares about
> > -how to store that information and how to make it available to
> > -users efficiently. This separation of concerns allows both the
> > -client and the server to evolve independently as it only requires
> > -that the interface stays the same.
> > +the content and the network of information, and how to make it
> Well Fielding says "By separating the user interface concerns from the data storage concerns..." so I just expanded on that. Not sure what lead you to Riak.
> 
> Also the server does not necessarily care about linking the content together at all, broken links are common.
> 
> —
> Reply to this email directly or view it on GitHub.