anchor.diff:  [[howto-enable-https]]
   === Enable HTTPS
   Ensuring that all your main endpoints are only available over HTTPS is an important
  -chore for any application.  If you are using Tomcat as a servlet container, then the
  +chore for any application.  If you are using Tomcat as a servlet container, then
   Spring Boot will add Tomcat's own `RemoteIpValve` automatically if it detects some
   environment settings, and you should be able to rely on the `HttpServletRequest` to
  -report whether or not it is secure (even downstream of the real SSL termination). The
  +report whether it is secure or not (even downstream of the real SSL termination). The
   standard behavior is determined by the presence or absence of certain request headers
   (`x-forwarded-for` and `x-forwarded-proto`), whose names are conventional, so it should
  -work with most front end proxies.  You switch on the valve by adding some entries to
  +work with most front end proxies. You can switch on the valve by adding some entries to
   `application.properties`, e.g.
   
   [source,properties,indent=0]
  
positive.code: 
  [[howto-build-an-executable-archive-with-ant]]
  === Build an executable archive with Ant
  To build with Ant you need to grab dependencies and compile and then create a jar or war
  archive as normal.  To make it executable:
  
  . Use the appropriate launcher as a `Main-Class`, e.g. `JarLauncher` for a jar file, and
    specify the other properties it needs as manifest entries, principally a `Start-Class`.
  
negative.code: 
  * `${PID}` the current process ID.
  * `${LOG_FILE}` if `logging.file` was set in Boot's external configuration.
  * `${LOG_PATH}` if `logging.path` was set (representing a directory for
  	log files to live in).
  
  Spring Boot also provides some nice ANSI colour terminal output on a console (but not in
  