anchor.diff:  
   `{#request.path.startsWith('/my/api')}`
   
  +== Response
  +
  +=== Properties
  +|===
  +.^|Property      |Description            ^.^|Type            |Example
  +
  +.^|content       |Body content           ^.^|string          |-
  +.^|headers       |Headers                ^.^|key / value     |X-Custom -> myvalue
  +.^|status        |Status of the HTTP response      ^.^|int    |200
  +|===
  +
  +=== Example
  +
  +* Get the status of an HTTP response:
  +`{#response.status}`
  +
   == Policies
  -Expression language can be used to configure some aspects of policy configuration.
  +You can use the EL to update some aspects of policy configuration.
   The policy needs to specify if it supports EL or not.
   
   == Mixin
  
positive.code: The APIM Expression Language (EL for short) is one of the key features
  that can be used by API publishers to configure various aspects and services of an API.
  
  This expression language is a powerful language that supports querying and
  manipulating an object graph and is based on the http://docs.spring.io/spring/docs/current/spring-framework-reference/html/expressions.html[SpEL] (Spring Expression Language).
  This means that you can do everything described in the link.
  
  In addition, APIM extends the standard SpEL capabilities by providing extra objects and properties
  
negative.code: `{#properties['my-property']}`
  
  === Endpoints
  When you define endpoints for your API, you need to give them a _name_ which
  must be a unique identifier across all endpoints of the API. This identifier can be used to get an endpoint reference (i.e. uri).
  
  For example: when you create an API, a _default_ endpoint is created,
  corresponding to the value you set for the backend property. This endpoint can
  be retrieved with EL by using the following syntax:
  
  `{#endpoints['default']}`
  
  