anchor.diff:  
   
   [[using-boot-devtools-restart-exclude]]
  -==== Excluding resources
  -Certain resources don't necessarily need to trigger a restart when they are changed. For
  -example, Thymeleaf templates can just be edited in-place. By default changing resources
  -in `/META-INF/maven`, `/META-INF/resources`, `/resources`, `/static`, `/public` or
  -`/templates` will not trigger a restart but will trigger a
  -<<using-boot-devtools-livereload, live reload>>. If you want to customize these exclusions
  +==== Excluding Resources
  +Certain resources do not necessarily need to trigger a restart when they are changed. For
  +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:
  +`/static` and `/public` you would set the following property:
   
   [indent=0]
   ----
   	spring.devtools.restart.exclude=static/**,public/**
   ----
   
  -TIP: if you want to keep those defaults and _add_ additional exclusions, use the
  +TIP: If you want to keep those defaults and _add_ additional exclusions, use the
   `spring.devtools.restart.additional-exclude` property instead.
   
   
   [[using-boot-devtools-restart-additional-paths]]
  -==== Watching additional paths
  +==== Watching Additional Paths
   You may want your application to be restarted or reloaded when you make changes to files
   that are not on the classpath. To do so, use the
   `spring.devtools.restart.additional-paths` property to configure additional paths to watch
   for changes. You can use the `spring.devtools.restart.exclude` property
   <<using-boot-devtools-restart-exclude, described above>> to control whether changes
  -beneath the additional paths will trigger a full restart or just a
  +beneath the additional paths trigger a full restart or a
   <<using-boot-devtools-livereload, live reload>>.
   
   
   
   [[using-boot-devtools-restart-disable]]
  -==== Disabling restart
  -If you don't want to use the restart feature you can disable it using the
  -`spring.devtools.restart.enabled` property. In most cases you can set this in your
  -`application.properties` (this will still initialize the restart classloader but it won't
  +==== Disabling Restart
  +If you do not want to use the restart feature, you can disable it by using the
  +`spring.devtools.restart.enabled` property. In most cases, you can set this property in your
  +`application.properties` (doing so still initializes the restart classloader, but it does not
   watch for file changes).
   
  -If you need to _completely_ disable restart support, for example, because it doesn't work
  -with a specific library, you need to set a `System` property before calling
  -`SpringApplication.run(...)`. For example:
  +If you need to _completely_ disable restart support (for example, because it doesn't work
  +with a specific library), you need to set the `spring.devtools.restart.enabled` `System` property to `false` before calling
  +`SpringApplication.run(...)`, as shown in the following example:
   
   [source,java,indent=0]
   ----
  
positive.code: 	</dependencyManagement>
  ----
  
  That setup does not allow you to override individual dependencies using a property as
  explained above. To achieve the same result, you'd need to add an entry in the
  `dependencyManagement` of your project **before** the `spring-boot-dependencies`
  entry. For instance, to upgrade to another Spring Data release train you'd add the
  following to your `pom.xml`.
  
  [source,xml,indent=0,subs="verbatim,quotes,attributes"]
  ----
  
negative.code: [partintro]
  --
  This section goes into more detail about how you should use Spring Boot. It covers topics
  such as build systems, auto-configuration, and how to run your applications. We also cover
  some Spring Boot best practices. Although there is nothing particularly special about
  Spring Boot (it is just another library that you can consume), there are a few
  recommendations that, when followed, make your development process a
  little easier.
  
  If you are starting out with Spring Boot, you should probably read the
  _<<getting-started.adoc#getting-started, Getting Started>>_ guide before diving into
  this section.
  --
  