anchor.diff:  
   Example: ```/api/v1/demo/webroot/Vehicle%20Images/ford-gt.jpg?width=1000```
   
  -This makes it possible to integrate mesh with many known routing frameworks.
  +This makes it possible to integrate Gentics Mesh with many known routing frameworks.
   
   [options="header"]
   |======
  
positive.code: 
  === Encoding
  
  Mesh expects and returns UTF-8 encoded data. Sending data in any other encoding format will result in encoding issues.
  
  === Headers
  
  It is important to set the ```Content-Type: application/json``` when sending JSON data and to also set the ```Accept``` header in order to signal Mesh that your client is accepting JSON.
  
  
  [source,bash]
  
negative.code: 
  === Cache Options
  
  Gentics Mesh does not manage any cache structure but it is possible to tweak the underlying graph database cache settings.
  
  == Concepts
  
  === Permissions
  
  Permissions exist between roles and other elements (including other roles). Most responses within Gentics Mesh will contain a list of permissions which may indicate that CRUD operations on the returned element is restricted in a way.
  
  The ```/api/v1/roles/:roleUuid/permissions``` endpoint can be used to assign or revoke permissions to/from a role. This endpoint can also be used to apply recursive permissions.
  It is important to note that permissions can be applied to individual elements and onto the set of elements which is identified by the endpoint name (e.g: /groups).
  