anchor.diff:  
   This part of the API is used by 'DCP administrators' to manage DCP configuration documents.
   Configuration documents use distinct structures depending on DCP feature they configure. 
  -They are referenced from DCP code by defined `id`. For list of supported confioguration document id's and related configuration document structure see DCP documentation.  
  -
  +They are referenced from DCP code by defined `id`. For list of supported confioguration document id's and related configuration document structure see [DCP documentation](https://github.com/jbossorg/dcp-api/blob/master/documentation/rest-api/management/).  
   --
   
   Get configuration document for given `id`.
  
positive.code: 
  --
  Content Push API
  This part of API is primarily used by *content providers* to manipulate content in DCP. 
  
  Each provider has set of 'provider types' defined in DCP, which are passed on this API as `{dcp_content_type}` URL path part.
  'Provider type' is one type of content object stored into DCP by given provider (eg. issue from provider's issue tracking system, blog post from provider's blogging system etc).
  
negative.code: Management API - content providers
  
  This part of the API allows to manage configurations of *content providers*. *Content provider* is an entity which stores content into DCP (see Content Push API).
  
  This part of the API is used by 'DCP administrators', some operations can be used by *content providers* alone too.
  
  [Data structure used on this API is documented here](https://github.com/jbossorg/dcp-api/blob/master/documentation/rest-api/management/content_provider.md).
  --
  
  Get configuration for provider of given name.
  