anchor.diff:  [[boot-features-spring-mvc-favicon]]
   ==== Custom Favicon
   Spring Boot looks for a `favicon.ico` in the configured static content locations and the
  -root of the classpath (in that order). If such a file is present, it is automatically used
  -as the favicon of the application.
  +root of the classpath (in that order). If such a file is present, it is automatically
  +used as the favicon of the application.
   
   
   
   [[boot-features-spring-mvc-web-binding-initializer]]
   ==== ConfigurableWebBindingInitializer
  -Spring MVC uses a `WebBindingInitializer` to initialize a `WebDataBinder` for a particular
  -request. If you create your own `ConfigurableWebBindingInitializer` `@Bean`, Spring Boot
  -automatically configures Spring MVC to use it.
  +Spring MVC uses a `WebBindingInitializer` to initialize a `WebDataBinder` for a
  +particular request. If you create your own `ConfigurableWebBindingInitializer` `@Bean`,
  +Spring Boot automatically configures Spring MVC to use it.
   
   
   
   [[boot-features-spring-mvc-template-engines]]
   ==== Template Engines
   As well as REST web services, you can also use Spring MVC to serve dynamic HTML content.
  -Spring MVC supports a variety of templating technologies, including Thymeleaf, FreeMarker,
  -and JSPs. Also, many other templating engines include their own Spring MVC integrations.
  +Spring MVC supports a variety of templating technologies, including Thymeleaf,
  +FreeMarker, and JSPs. Also, many other templating engines include their own Spring MVC
  +integrations.
   
   Spring Boot includes auto-configuration support for the following templating engines:
   
  
positive.code: [source,java,indent=0]
  ----
  	import org.junit.runner.RunWith;
      import org.springframework.boot.autoconfigure.mongo.embedded.EmbeddedMongoAutoConfiguration;
  	import org.springframework.boot.test.autoconfigure.data.mongo.DataMongoTest;
  	import org.springframework.test.context.junit4.SpringRunner;
  
  
negative.code: 	}
  ----
  
  NOTE: By default, Spring Boot puts `WebDriver` beans in a special "`scope`" to ensure
  that the driver is quit after each test and that a new instance is injected. If you do
  not want this behavior, you can add `@Scope("singleton")` to your `WebDriver` `@Bean`
  definition.
  
  A list of the auto-configuration settings that are enabled by `@WebMvcTest` can be
  <<appendix-test-auto-configuration#test-auto-configuration,found in the appendix>>.
  