anchor.diff:  through the `spring-boot-starter-hateoas` or if you are using
   http://projects.spring.io/spring-data-rest[Spring Data REST]) then the HTTP endpoints
   from the Actuator are enhanced with hypermedia links, and a "`discovery page`" is added
  -with links to all the endpoints. The "`discovery page`" is available on `/actuator` by
  +with links to all the endpoints. The "`discovery page`" is available on `/application` by
   default. It is implemented as an endpoint, allowing properties to be used to configure
   its path (`endpoints.actuator.path`) and whether or not it is enabled
   (`endpoints.actuator.enabled`).
   
   When a custom management context path is configured, the "`discovery page`" will
  -automatically move from `/actuator` to the root of the management context. For example,
  +automatically move from `/application` to the root of the management context. For example,
   if the management context path is `/management` then the discovery page will be available
   from `/management`.
   
  
positive.code: `health` endpoint provides basic application health information.
  
  The way that endpoints are exposed will depend on the type of technology that you choose.
  Most applications choose HTTP monitoring, where the ID of the endpoint is mapped
  to a URL. For example, by default, the `health` endpoint will be mapped to `/health`.
  
  The following technology agnostic endpoints are available:
  
  
negative.code: == Monitoring and management over HTTP
  If you are developing a Spring MVC application, Spring Boot Actuator will auto-configure
  all enabled endpoints to be exposed over HTTP. The default convention is to use the
  `id` of the endpoint with a prefix of `/application` as the URL path. For example, `health`
  is exposed as `/application/health`.
  
  
  
  