Polish documentation title case
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
[[cli.groovy-beans-dsl]]
|
||||
== Developing Applications with the Groovy Beans DSL
|
||||
== Developing Applications With the Groovy Beans DSL
|
||||
Spring Framework 4.0 has native support for a `beans{}` "`DSL`" (borrowed from https://grails.org/[Grails]), and you can embed bean definitions in your Groovy application scripts by using the same format.
|
||||
This is sometimes a good way to include external features like middleware declarations, as shown in the following example:
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
[[cli.maven-setting]]
|
||||
== Configuring the CLI with settings.xml
|
||||
== Configuring the CLI With settings.xml
|
||||
The Spring Boot CLI uses Maven Resolver, Maven's dependency resolution engine, to resolve dependencies.
|
||||
The CLI makes use of the Maven configuration found in `~/.m2/settings.xml` to configure Maven Resolver.
|
||||
The following configuration settings are honored by the CLI:
|
||||
|
||||
@@ -50,7 +50,7 @@ The `version` command provides a quick way to check which version of Spring Boot
|
||||
|
||||
|
||||
[[cli.using-the-cli.run]]
|
||||
=== Running Applications with the CLI
|
||||
=== Running Applications With the CLI
|
||||
You can compile and run Groovy source code by using the `run` command.
|
||||
The Spring Boot CLI is completely self-contained, so you do not need any external Groovy installation.
|
||||
|
||||
@@ -197,7 +197,7 @@ However, to ensure consistent ordering of the dependency management, you can use
|
||||
|
||||
|
||||
[[cli.using-the-cli.multiple-source-files]]
|
||||
=== Applications with Multiple Source Files
|
||||
=== Applications With Multiple Source Files
|
||||
You can use "`shell globbing`" with all commands that accept file input.
|
||||
Doing so lets you use multiple files from a single directory, as shown in the following example:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user