diff --git a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
index cc0625ba319..f1c94c8572a 100644
--- a/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
+++ b/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
@@ -648,10 +648,10 @@ The information exposed by the health endpoint varies depending on whether or no
 accessed anonymously, and whether or not the enclosing application is secure.
 By default, when accessed anonymously in a secure application, any details about the
 server's health are hidden and the endpoint will simply indicate whether or not the server
-is up or down. Furthermore, when accessed anonymously, the response is cached for a
-configurable period to prevent the endpoint being used in a denial of service attack.
-The `endpoints.health.time-to-live` property is used to configure the caching period in
-milliseconds. It defaults to 1000, i.e. one second.
+is up or down. Furthermore the response is cached for a configurable period to prevent the
+endpoint being used in a denial of service attack. The `endpoints.health.time-to-live`
+property is used to configure the caching period in milliseconds. It defaults to 1000,
+i.e. one second.
 
 The above-described restrictions can be enhanced, thereby allowing only authenticated
 users full access to the health endpoint in a secure application. To do so, set