Use American English spellings

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/metrics.adoc

@@ -224,7 +224,7 @@ The https://graphiteapp.org[Graphite server] host and port to use can be provide
 
 Micrometer provides a default `HierarchicalNameMapper` that governs how a dimensional meter id is {micrometer-registry-docs}/graphite#_hierarchical_name_mapping[mapped to flat hierarchical names].
 
-TIP: To take control over this behaviour, define your `GraphiteMeterRegistry` and supply your own `HierarchicalNameMapper`.
+TIP: To take control over this behavior, define your `GraphiteMeterRegistry` and supply your own `HierarchicalNameMapper`.
 An auto-configured `GraphiteConfig` and `Clock` beans are provided unless you define your own:
 
 [source,java,indent=0]
@@ -297,7 +297,7 @@ The domain to use can be provided using:
 
 Micrometer provides a default `HierarchicalNameMapper` that governs how a dimensional meter id is {micrometer-registry-docs}/jmx#_hierarchical_name_mapping[mapped to flat hierarchical names].
 
-TIP: To take control over this behaviour, define your `JmxMeterRegistry` and supply your own `HierarchicalNameMapper`.
+TIP: To take control over this behavior, define your `JmxMeterRegistry` and supply your own `HierarchicalNameMapper`.
 An auto-configured `JmxConfig` and `Clock` beans are provided unless you define your own:
 
 [source,java,indent=0]

spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/developing-auto-configuration.adoc

@@ -220,7 +220,7 @@ Concretely, a custom starter can contain the following:
 In a nutshell, adding the starter should provide everything needed to start using that library.
 
 This separation in two modules is in no way necessary.
-If "acme" has several flavours, options or optional features, then it is better to separate the auto-configuration as you can clearly express the fact some features are optional.
+If "acme" has several flavors, options or optional features, then it is better to separate the auto-configuration as you can clearly express the fact some features are optional.
 Besides, you have the ability to craft a starter that provides an opinion about those optional dependencies.
 At the same time, others can rely only on the `autoconfigure` module and craft their own starter with different opinions.
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/messaging.adoc

@@ -391,7 +391,7 @@ include::{docs-java}/features/messaging/kafka/streams/MyKafkaStreamsConfiguratio
 ----
 
 By default, the streams managed by the `StreamBuilder` object it creates are started automatically.
-You can customize this behaviour using the configprop:spring.kafka.streams.auto-startup[] property.
+You can customize this behavior using the configprop:spring.kafka.streams.auto-startup[] property.
 
 
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/howto/data-access.adoc

@@ -288,7 +288,7 @@ For details, refer to {hibernate-docs}#caching-provider-jcache[the Hibernate use
 === Use Dependency Injection in Hibernate Components
 By default, Spring Boot registers a `BeanContainer` implementation that uses the `BeanFactory` so that converters and entity listeners can use regular dependency injection.
 
-You can disable or tune this behaviour by registering a `HibernatePropertiesCustomizer` that removes or changes the `hibernate.resource.beans.container` property.
+You can disable or tune this behavior by registering a `HibernatePropertiesCustomizer` that removes or changes the `hibernate.resource.beans.container` property.
 
 
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/using/structuring-your-code.adoc

@@ -22,7 +22,7 @@ The <<using#using.using-the-springbootapplication-annotation, `@SpringBootApplic
 For example, if you are writing a JPA application, the package of the `@SpringBootApplication` annotated class is used to search for `@Entity` items.
 Using a root package also allows component scan to apply only on your project.
 
-TIP: If you don't want to use `@SpringBootApplication`, the `@EnableAutoConfiguration` and `@ComponentScan` annotations that it imports defines that behaviour so you can also use those instead.
+TIP: If you don't want to use `@SpringBootApplication`, the `@EnableAutoConfiguration` and `@ComponentScan` annotations that it imports defines that behavior so you can also use those instead.
 
 The following listing shows a typical layout: