From 0cd526c2662f89c7b66f320dd91f829cb7a60d5f Mon Sep 17 00:00:00 2001 From: Toshiaki Maki Date: Thu, 4 Jun 2020 15:08:23 +0900 Subject: [PATCH] Fix event name in documentation See gh-21692 --- .../src/docs/asciidoc/spring-boot-features.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc index dcd76a4720..90d8c26c1b 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc @@ -313,7 +313,7 @@ Application events are sent in the following order, as your application runs: . An `ApplicationStartedEvent` is sent after the context has been refreshed but before any application and command-line runners have been called. . An `AvailabilityChangeEvent` is sent right after with `LivenessState.CORRECT` to indicate that the application is considered as live. . An `ApplicationReadyEvent` is sent after any application and command-line runners have been called. -. An `LivenessState` is sent right after with `ReadinessState.ACCEPTING_TRAFFIC` to indicate that the application is ready to service requests. +. An `AvailabilityChangeEvent` is sent right after with `ReadinessState.ACCEPTING_TRAFFIC` to indicate that the application is ready to service requests. . An `ApplicationFailedEvent` is sent if there is an exception on startup. The above list only includes ``SpringApplicationEvent``s that are tied to a `SpringApplication`.