anchor.diff:  
   * Java 1.8 as the default compiler level.
   * UTF-8 source encoding.
  -* A <<using-boot-dependency-management,Dependency Management section>>, allowing you to
  -  omit `<version>` tags for common dependencies, inherited from the
  -  `spring-boot-dependencies` POM.
  +* A <<using-boot-dependency-management,Dependency Management section>>, inherited from
  +the spring-boot-dependencies pom, that manages the versions of common dependencies. This
  +dependency management lets you omit <version> tags for those dependencies when used
  +in your own pom.
   * Sensible https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html[resource filtering].
   * Sensible plugin configuration (http://www.mojohaus.org/exec-maven-plugin/[exec plugin],
  -  https://github.com/ktoso/maven-git-commit-id-plugin[Git commit ID],
  +  https://github.com/ktoso/maven-git-commit-id-plugin[Git commit ID], and
     http://maven.apache.org/plugins/maven-shade-plugin/[shade]).
   * Sensible resource filtering for `application.properties` and `application.yml` including
  -  profile-specific files (e.g. `application-foo.properties` and `application-foo.yml`)
  -
  -On the last point: since the default config files accept
  -Spring style placeholders (`${...}`) the Maven filtering is changed to
  -use `@..@` placeholders (you can override that with a Maven property
  -`resource.delimiter`).
  +  profile-specific files (for example, `application-foo.properties` and `application-foo.yml`)
  +
  +Note that, since the `application.properties` and `application.yml` files accept
  +Spring style placeholders (`${...}`), the Maven filtering is changed to
  +use `@..@` placeholders. (You can override that by setting a Maven property called
  +`resource.delimiter`.)
   
   
   
   [[using-boot-maven-parent-pom]]
  -==== Inheriting the starter parent
  -To configure your project to inherit from the `spring-boot-starter-parent` simply set
  -the `parent`:
  +==== Inheriting the Starter Parent
  +To configure your project to inherit from the `spring-boot-starter-parent` set
  +the `parent`, as follows:
   
   [source,xml,indent=0,subs="verbatim,quotes,attributes"]
   ----
  
positive.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, will make your development process just a
  little easier.
  
  If you're just starting out with Spring Boot, you should probably read the
  _<<getting-started.adoc#getting-started, Getting Started>>_ guide before diving into
  this section.
  --
  
negative.code: 
  
  [[using-boot-configuration-classes]]
  == Configuration Classes
  Spring Boot favors Java-based configuration. Although it is possible to use
  `SpringApplication` with XML sources, we generally recommend that your primary
  source be a single `@Configuration` class. Usually the class that defines the `main`
  method is a good candidate as the primary `@Configuration`.
  
  TIP: Many Spring configuration examples have been published on the Internet that use XML
  configuration. If possible, always try to use the equivalent Java-based configuration.
  Searching for `+Enable*+` annotations can be a good starting point.
  
  
  
  [[using-boot-importing-configuration]]
  === Importing Additional Configuration Classes
  You need not put all your `@Configuration` into a single class. The `@Import`
  annotation can be used to import additional configuration classes. Alternatively, you
  can use `@ComponentScan` to automatically pick up all Spring components, including
  `@Configuration` classes.
  