Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos

Browse Source 
Closes gh-3504
This commit is contained in:
izeye
2015-07-15 20:16:30 +09:00
committed by Stephane Nicoll
parent f2d32d3e98
commit f4589e7cc3
17 changed files with 20 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spring-boot-docs/src/main/asciidoc/appendix-application-properties.adoc
View File

@@ -133,7 +133,7 @@ content into your application; rather pick only the properties that you need.
spring.mvc.date-format= # set fixed date format, e.g. dd/MM/yyyy
spring.mvc.favicon.enabled=true
spring.mvc.message-codes-resolver-format= # PREFIX_ERROR_CODE / POSTFIX_ERROR_CODE
spring.mvc.ignore-default-model-on-redirect=true # if the the content of the "default" model should be ignored redirects
spring.mvc.ignore-default-model-on-redirect=true # if the content of the "default" model should be ignored redirects
spring.mvc.async.request-timeout= # async request timeout in milliseconds
spring.mvc.view.prefix= # MVC view prefix
spring.mvc.view.suffix= # ... and suffix

2
spring-boot-docs/src/main/asciidoc/appendix-configuration-metadata.adoc
View File

@@ -538,7 +538,7 @@ value but could highlight valid packages and class names that are not available
project's classpath.
The meta-data snippet below corresponds to the standard `logging.level` property, keys
are _logger names_ and values correspond to the the standard log levels or any custom
are _logger names_ and values correspond to the standard log levels or any custom
level:
[source,json,indent=0]

2
spring-boot-docs/src/main/asciidoc/appendix-executable-jar-format.adoc
View File

@@ -21,7 +21,7 @@ without unpacking.
To solve this problem, many developers use "`shaded`" jars. A shaded jar simply packages
all classes, from all jars, into a single 'uber jar'. The problem with shaded jars is
that it becomes hard to see which libraries you are actually using in your application.
It can also be problematic if the the same filename is used (but with different content)
It can also be problematic if the same filename is used (but with different content)
in multiple jars. Spring Boot takes a different approach and allows you to actually nest
jars directly.

2
spring-boot-docs/src/main/asciidoc/deployment.adoc
View File

@@ -348,7 +348,7 @@ or `systemd`.
[[deployment-initd-service]]
==== Installation as a init.d service (System V)
==== Installation as an init.d service (System V)
The default executable script that can be embedded into Spring Boot jars will act as an
`init.d` script when it is symlinked to `/etc/init.d`. The standard `start`, `stop`,
`restart` and `status` commands can be used. The script supports the following features:

2
spring-boot-docs/src/main/asciidoc/getting-started.adoc
View File

@@ -705,7 +705,7 @@ distribute a self-contained application.
To solve this problem, many developers use "`uber`" jars. An uber jar simply packages
all classes, from all jars, into a single archive. The problem with this approach is that
it becomes hard to see which libraries you are actually using in your application. It can
also be problematic if the the same filename is used (but with different content) in
also be problematic if the same filename is used (but with different content) in
multiple jars.
Spring Boot takes a <<appendix-executable-jar-format.adoc#executable-jar, different

4
spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View File

@@ -286,7 +286,7 @@ values can be injected directly into your beans using the `@Value` annotation, a
via Spring's `Environment` abstraction or bound to structured objects.
Spring Boot uses a very particular `PropertySource` order that is designed to allow
sensible overriding of values, properties are considered in the the following order:
sensible overriding of values, properties are considered in the following order:
. Command line arguments.
. JNDI attributes from `java:comp/env`.
@@ -2639,7 +2639,7 @@ TIP: It is also possible to {spring-reference}/#cache-annotations-put[update] or
=== Supported cache providers
The cache abstraction does not provide an actual store and relies on a abstraction
The cache abstraction does not provide an actual store and relies on abstraction
materialized by the `org.springframework.cache.Cache` and
`org.springframework.cache.CacheManager` interfaces. Spring Boot auto-configures a
suitable `CacheManager` according to the implementation as long as the caching support is