anchor.diff:  example, Thymeleaf templates can be edited in-place. By default, changing resources
   in `/META-INF/maven`, `/META-INF/resources`, `/resources`, `/static`, `/public`, or
   `/templates` does not trigger a restart but does trigger a
  -<<using-boot-devtools-livereload, live reload>>. If you want to customize these exclusions,
  -you can use the `spring.devtools.restart.exclude` property. For example, to exclude only
  -`/static` and `/public` you would set the following property:
  +<<using-boot-devtools-livereload, live reload>>. If you want to customize these
  +exclusions, you can use the `spring.devtools.restart.exclude` property. For example, to
  +exclude only `/static` and `/public` you would set the following property:
   
   [indent=0]
   ----
  
positive.code: include::../../../target/generated-resources/production-starters.adoc[]
  
  Finally, Spring Boot also includes the following starters that can be used if you want to
  exclude
  or swap specific technical facets:
  
  .Spring Boot technical starters
  include::../../../target/generated-resources/technical-starters.adoc[]
  
negative.code: [[using-boot-auto-configuration]]
  == Auto-configuration
  Spring Boot auto-configuration attempts to automatically configure your Spring
  application based on the jar dependencies that you have added. For example, if `HSQLDB`
  is on your classpath, and you have not manually configured any database connection beans,
  then Spring Boot auto-configures an in-memory database.
  
  You need to opt-in to auto-configuration by adding the `@EnableAutoConfiguration` or
  `@SpringBootApplication` annotations to one of your `@Configuration` classes.
  