SpringCloud/spring-cloud-task
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

3 spelling corrections

Browse Source
This commit is contained in:
Glenn Renfro
2016-06-16 14:46:51 -04:00
parent 2df7e95a5a
commit 319db45c4e
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -72,7 +72,7 @@ assumed to be 0.
|`taskName`
|The name for the task as determined by the configured `TaskNameResolver`.
|`starTime`
|`startTime`
|The time the task was started as indicated by the `SmartLifecycle#start` call.
|`endTime`
@@ -98,7 +98,7 @@ be of any use to you in the debugging of that.
As such, Spring Boot provides an interface, `ExitCodeExceptionMapper` that allows you to
map uncaught exceptions to exit codes. This allows you to be able to indicate at that
level what went wrong. Also, by mapping exit codes in this manor, Spring Cloud Task will
level what went wrong. Also, by mapping exit codes in this manner, Spring Cloud Task will
record the exit code returned.
NOTE: While the task is running the exit code will be stored as a null in the repository.

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

@@ -233,7 +233,7 @@ Spring Boot documentation.
==== The CommandLineRunner
In Spring, there are many ways to bootstrap an application's logic. Spring Boot provides
a convenient method of doing so in an organized manor via their `*Runner` interfaces
a convenient method of doing so in an organized manner via their `*Runner` interfaces
(`CommandLineRunner` or `ApplicationRunner`). A well behaved task will bootstrap any
logic via one of these two runners.