anchor.diff:  
   ==== Updating a Release
   
  -A releases can be _renamed_ and new schema/microschema versions can be _assigned_ to it.
  +A release can be _renamed_ and new schema/microschema versions can be _assigned_ to it.
   
   Renaming is useful if you want to change your development release to be the current production release.
   
  
positive.code: 
  ====  Reading Nodes
  
  It is possible to load older version by specifying the ```?version``` parameter. Similarly the published version of can also be loaded using the parameter ```?version=published``` or the draft version via ```?version=draft```.
  
  NOTE: By default nodes will be loaded using ```?version=published```. A nodes list thus may not contain your previously created node because it was not yet published.
  
  NOTE: Reading published nodes requires the user to be assigned to a role which grants the ```readpublished``` permission.
  
  ==== Limitations
  
  
negative.code: | ```/api/v1/:projectName/tags/:uuid```  | Publish        | _Not used_
  |======
  
  ===== Nodes
  
  Recursive permission changes on ```/:projectName/nodes/:uuid``` will also affect children of the node.
  
  [options="header"]
  