anchor.diff:  
   === Resource Discoverability
   
  -A core principle of HATEOAS is that resources should be discoverable through the publication of links that point to the available resources.  There are a few competing de-facto standards of how to represent links in JSON.  By default, Spring Data REST uses HAL to render responses.  HAL defines links to be contained in a property of the returned document.
  -
  -Resource discovery starts at the top level of the application.  By issuing a request to the root URL under which the Spring Data REST application is deployed, the client can extract a set of links from the returned JSON object that represent the next level of resources that are available to the client.
  -
  -When enabled through `@Import(HypermediaConfiguration.class)` Spring Content REST will inject content resource and content collection resource links for both content and content collection associations into t	he HAL responses created by Spring Data REST. 
  -
  -== The Content Resource
  -
  -Spring Content REST exposes a content resource named after the uncapitalized, pluralized version of the domain class the exported store is handling.  The resource path can be customized using the `@StoreRestResource` on the store interface.
  +A core principle of HATEOAS is that Resources should be discoverable through the publication of links that point to the
  +available resources.  There are a few competing de-facto standards specifying how to represent links in JSON.  By default,
  +Spring Data REST uses HAL to render responses.  HAL defines links to be contained in a property of the returned document.
  +
  +Resource discovery starts at the top level of the application.  By issuing a request to the root URL under which the
  +Spring Data REST application is deployed, the client can extract a set of links from the returned JSON object that
  +represent the next level of resources that are available to the client.
  +
  +When enabled through `@Import(HypermediaConfiguration.class)` Spring Content REST will inject Store, Entity and Property
  +Resources links for both into the HAL responses created by Spring Data REST.
  +
  +== The Store Resource
  +
  +Spring Content REST exports Store Resources to `/{store}/**`.  The resource path can be customized using the
  +`@StoreRestResource` annotation on the Store interface.
  +
  +=== Supported HTTP Methods
  +
  +Store Resources support `GET`, `PUT`, `POST`, and `DELETE`.  All other HTTP methods will cause a `405 Method Not
  +Allowed`.
  +
  +==== GET
  +
  +Returns the Resource's content
  +
  +===== Supported media types
  +
  +All content types except `application/json`
  +
  +==== PUT/POST
  +
  +Sets the Resources's content
  +
  +===== Supported media types
  +
  +All content types except `application/json`
  +
  +==== DELETE
  +
  +Removes the Resource's content
  +
  +===== Supported media types
  +
  +All content types except `application/json`
  +
  +== The Entity Resource
  +
  +Spring Content REST exports Entity Resources to `/{store}/{id}`.  The resource path can be customized using the
  +`@StoreRestResource` annotation on the Store interface.
    
   === Supported HTTP Methods
   
  -Content resources support `GET`, `PUT`, `POST`, and `DELETE`.  All other HTTP methods will cause a `405 Method Not Allowed`.
  +Entity Resources support `GET`, `PUT`, `POST`, and `DELETE`.  All other HTTP methods will cause a `405 Method Not
  +Allowed`.
   
   ==== GET
   
  
positive.code: ----
  ====
  
  In this example many Resources can be associated with the chapters property of the `Dvd` Entity.
  
  As with Property Association the content resources are exposed under the URI `/dvds/{id}/chapters/{contentId}`.  In this case POSTing to `/dvds/{id}/chapters` a new content resource to be *appended* to the 'Chapters' collection.  This resource supports both POST and PUT HTTP methods.
  
  === Search
  
  
negative.code: ----
  ====  
  
  In this example separate Resources are associated with the `image` and `stream` properties of the `Dvd` Entity.
  
  When using JPA and its relational characteristics these associations are typically (but not always) also Entity
  associations as well, as shown here.  However when using NoSQL databases like MongoDB that are capable of storing
  hierarchical data they are true property associations.
  
  As before, Spring Data REST will export an item resource under the URI `/dvds/{id}`.  However, this time Spring Content
  REST will export Property Resources to the URI `/dvds/{id}/image/{contentId}` and `/dvds/{id}/stream/{contentId}`
  managed by the respective Store.  A property can be set by POSTing to `/dvds/{id}/image` (or `/dvds/{id}/stream`).
  
  NOTE: as these properties are both single values these Resources are also available under the simplified URI
  `/dvds/{id}/image` and `/dvds/{id}/stream` where the `{contentId}` is omitted for convenience.
  
  === Property Collection Resources
  
  Property Resources can also target Collections.
  
  Consider the following example:-
  
  ====
  [source, java]
  