anchor.diff:  Gentics Mesh *users* can be physical persons or client apps interacting with elements in Gentics Mesh. Both have a user object counterpart in Gentics Mesh. 
   This user object has a standard set of properties, e.g.```firstname```, ```lastname```, ```username```, and ```emailAddress``` , which can be extended by referencing a custom user object. The property ```nodeReference``` is used for storing additional user-related data, thus allowing for extensible user profiles. 
   
  -In order to be able to store and retrieve content, a user needs to authenticate using one of the available http://getmesh.io/docs/beta/#_authentication[authentication] mechanisms. 
  +In order to be able to store and retrieve content, a user needs to authenticate using one of the available link:references.html#_authentication[authentication] mechanisms. 
   
   === API end points
   
  
positive.code: 
  Typically, each project will require a set of different content types. Together they can be considered the content model of your project. Staying with the example of a product catalogue website: a product, product category, product image, and product manual each represent a separate content type. In Gentics Mesh, a *schema* is used to define such content types in terms of a couple of standard fields (e.g. ```uuid```, ```name```, ```description```, ```version```, etc.) and an arbitrary number of custom fields (e.g., ```string```, ```number```, ```HTML```, ```date```, ```binary```, ```list```, ```node```, ```micronode```, ```boolean```). You can think of a schema as a blueprint for new content items.  
  
  TIP: Using the ```container``` property, a schema can be configured to allow for hierarchically structuring nodes. Nodes based on a such a schema may contain child nodes. This is the basis for building http://getmesh.io/docs/beta/#_contenttrees[content trees] in Gentics Mesh and leveraging the power of automatic http://getmesh.io/docs/beta/#_navigation[navigation menus], http://getmesh.io/docs/beta/#_breadcrumbs[breadcrumbs] and http://getmesh.io/docs/beta/#_prettyurls[pretty URLs].
  
  === API end points
  
  
negative.code: 
  | resolveLinks
  | string
  | The ```resolveLinks``` parameter can be set to either ```short```, ```medium``` or ```full```. With the parameter set the ```path``` property as well as the ```languagesPath``` property (for available language variants) will be included in the response. Gentics Mesh links in any HTML-typed field will automatically be resolved and replaced by the resolved link:features.html#_link_resolving[WebRoot path]. No resolving occurs if the query parameter is omitted.
  
  | role
  | string
  