@@ -149,7 +149,7 @@ within a JUnit test.
149149=== Using the CommandLineRunner
150150If you want access to the raw command line arguments, or you need to run some specific code
151151once the `SpringApplication` has started you can implement the `CommandLineRunner`
152- interface. The `run(String... args)` method will be called on all spring beans
152+ interface. The `run(String... args)` method will be called on all Spring beans
153153implementing this interface.
154154
155155[source,java,indent=0]
@@ -187,7 +187,7 @@ interface if they wish to return a specific exit code when the application ends.
187187
188188[[boot-features-external-config]]
189189== Externalized Configuration
190- Spring Boot likes you to externalize your configuration so you can work with the same
190+ Spring Boot allows you to externalize your configuration so you can work with the same
191191application code in different environments. You can use properties files, YAML files,
192192environment variables and command-line arguments to externalize configuration. Property
193193values can be injected directly into your beans using the `@Value` annotation, accessed
@@ -227,14 +227,14 @@ To provide a concrete example, suppose you develop a `@Component` that uses a
227227
228228You can bundle an `application.properties` inside your jar that provides a sensible
229229default `name`. When running in production, an `application.properties` can be provided
230- outside of your jar that overrides `name`; and for one off testing, you can launch with
230+ outside of your jar that overrides `name`; and for one- off testing, you can launch with
231231a specific command line switch (e.g. `java -jar app.jar --name="Spring"`).
232232
233233
234234
235235[[boot-features-external-config-command-line-args]]
236236=== Accessing command line properties
237- By default SpringApplication will convert any command line option arguments (starting
237+ By default ` SpringApplication` will convert any command line option arguments (starting
238238with ``--'', e.g. `--server.port=9000`) to a `property` and add it to the Spring
239239`Environment`. As mentioned above, command line properties always take precedence over
240240other property sources.
@@ -261,8 +261,8 @@ an alternative to '.properties'.
261261
262262If you don't like `application.properties` as the configuration file name you can switch
263263to another by specifying a `spring.config.name` environment property. You can also refer
264- to an explicit location using the `spring.config.location` environment property (comma-
265- separated list of directory locations, or file paths).
264+ to an explicit location using the `spring.config.location` environment property
265+ (comma- separated list of directory locations, or file paths).
266266
267267[indent=0]
268268----
@@ -506,7 +506,7 @@ property editors (via a `CustomEditorConfigurer` bean).
506506[[boot-features-external-config-validation]]
507507==== @ConfigurationProperties Validation
508508Spring Boot will attempt to validate external configuration, by default using JSR-303
509- (if it is on the classpath). You can simply add JSR-303 `javax.valididation ` constraint
509+ (if it is on the classpath). You can simply add JSR-303 `javax.validation ` constraint
510510annotations to your `@ConfigurationProperties` class:
511511
512512[source,java,indent=0]
0 commit comments