anchor.diff:  populate your database when your application starts and be prepared to throw away
   data when your application ends.
   
  -TIP: The '`How-to`' section includes a _<<howto.adoc#howto-database-initialization, section
  -on how to initialize a database>>_
  +TIP: The '`How-to`' section includes a _<<howto.adoc#howto-database-initialization,
  +section on how to initialize a database>>_
   
   Spring Boot can auto-configure embedded http://www.h2database.com[H2],
  -http://hsqldb.org/[HSQL] and http://db.apache.org/derby/[Derby] databases. You don't
  -need to provide any connection URLs, simply include a build dependency to the
  -embedded database that you want to use.
  +http://hsqldb.org/[HSQL] and http://db.apache.org/derby/[Derby] databases. You don't need
  +to provide any connection URLs, simply include a build dependency to the embedded database
  +that you want to use.
   
   For example, typical POM dependencies would be:
   
  
positive.code: [[boot-features-using-jms-template]]
  [[boot-features-using-jms-sending]]
  ==== Sending a message
  Spring's `JmsTemplate` is auto-configured and you can autowire it directly into your
  own beans:
  
  [source,java,indent=0]
  ----
  
negative.code: http://docs.codehaus.org/display/BTM/Home[Bitronix] embedded transaction manager. JTA
  transactions are also supported when deploying to a suitable Java EE Application Server.
  
  When a JTA environment is detected, Spring's `JtaTransactionManager` will be used to
  manage transactions. Auto-configured JMS, DataSource and JPA beans will be upgraded to
  support XA transactions. You can use standard Spring idioms such as `@Transactional` to
  participate in a distributed transaction. If you are within a JTA environment and still
  want to use local transactions you can set the `spring.jta.enabled` property to `false` to
  disable the JTA auto-configuration.
  