Polish "Fix a broken Asciidoctor syntax"

See gh-17970
This commit is contained in:
Stephane Nicoll
2019-08-27 11:11:57 +02:00
parent 78a467f9d3
commit cda310ba0a

View File

@@ -254,8 +254,9 @@ Application events are sent in the following order, as your application runs:
except for the registration of listeners and initializers. except for the registration of listeners and initializers.
. An `ApplicationEnvironmentPreparedEvent` is sent when the `Environment` to be used in . An `ApplicationEnvironmentPreparedEvent` is sent when the `Environment` to be used in
the context is known but before the context is created. the context is known but before the context is created.
. An `ApplicationContextInitializedEvent` is sent when the `ApplicationContext` is prepared . An `ApplicationContextInitializedEvent` is sent when the `ApplicationContext` is
and ApplicationContextInitializers have been called but before any bean definitions are loaded. prepared and ApplicationContextInitializers have been called but before any bean
definitions are loaded.
. An `ApplicationPreparedEvent` is sent just before the refresh is started but after bean . An `ApplicationPreparedEvent` is sent just before the refresh is started but after bean
definitions have been loaded. definitions have been loaded.
. An `ApplicationStartedEvent` is sent after the context has been refreshed but before any . An `ApplicationStartedEvent` is sent after the context has been refreshed but before any
@@ -264,13 +265,14 @@ application and command-line runners have been called.
been called. It indicates that the application is ready to service requests. been called. It indicates that the application is ready to service requests.
. An `ApplicationFailedEvent` is sent if there is an exception on startup. . An `ApplicationFailedEvent` is sent if there is an exception on startup.
The above list only includes ``SpringApplicationEvent``s that are tied to a `SpringApplication`. The above list only includes ``SpringApplicationEvent``s that are tied to a
In addition to these, the following events are also published after `ApplicationPreparedEvent` `SpringApplication`. In addition to these, the following events are also published after
and before `ApplicationStartedEvent`: `ApplicationPreparedEvent` and before `ApplicationStartedEvent`:
. A `ContextRefreshedEvent` is sent when an `ApplicationContext` is refreshed. . A `ContextRefreshedEvent` is sent when an `ApplicationContext` is refreshed.
. A `WebServerInitializedEvent` is sent after the `WebServer` is ready. `ServletWebServerInitializedEvent` . A `WebServerInitializedEvent` is sent after the `WebServer` is ready.
and `ReactiveWebServerInitializedEvent` are the servlet and reactive variants respectively. `ServletWebServerInitializedEvent` and `ReactiveWebServerInitializedEvent` are the servlet
and reactive variants respectively.
TIP: You often need not use application events, but it can be handy to know that they TIP: You often need not use application events, but it can be handy to know that they
exist. Internally, Spring Boot uses events to handle a variety of tasks. exist. Internally, Spring Boot uses events to handle a variety of tasks.