From 319db45c4ecebf398a77174cdd928fd949c4a54f Mon Sep 17 00:00:00 2001 From: Glenn Renfro Date: Thu, 16 Jun 2016 14:46:51 -0400 Subject: [PATCH] 3 spelling corrections --- spring-cloud-task-docs/src/main/asciidoc/features.adoc | 4 ++-- spring-cloud-task-docs/src/main/asciidoc/getting-started.adoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/spring-cloud-task-docs/src/main/asciidoc/features.adoc b/spring-cloud-task-docs/src/main/asciidoc/features.adoc index 33d437db..15b9c067 100644 --- a/spring-cloud-task-docs/src/main/asciidoc/features.adoc +++ b/spring-cloud-task-docs/src/main/asciidoc/features.adoc @@ -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. diff --git a/spring-cloud-task-docs/src/main/asciidoc/getting-started.adoc b/spring-cloud-task-docs/src/main/asciidoc/getting-started.adoc index 4481a5ff..3d7ee091 100644 --- a/spring-cloud-task-docs/src/main/asciidoc/getting-started.adoc +++ b/spring-cloud-task-docs/src/main/asciidoc/getting-started.adoc @@ -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.