Use one sentence per line in Actuator and Gradle plugin doc source

Closes spring-projectsgh-18185

Author: wilkinsona

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/auditevents.adoc

@@ -8,14 +8,12 @@ The `auditevents` endpoint provides information about the application's audit ev
 [[audit-events-retrieving]]
 == Retrieving Audit Events
 
-To retrieve the audit events, make a `GET` request to `/actuator/auditevents`, as shown
-in the following curl-based example:
+To retrieve the audit events, make a `GET` request to `/actuator/auditevents`, as shown in the following curl-based example:
 
 include::{snippets}auditevents/filtered/curl-request.adoc[]
 
-The preceding example retrieves `logout` events for the principal, `alice`, that occurred
-after 09:37 on 7 November 2017 in the UTC timezone. The resulting response is similar to
-the following:
+The preceding example retrieves `logout` events for the principal, `alice`, that occurred after 09:37 on 7 November 2017 in the UTC timezone.
+The resulting response is similar to the following:
 
 include::{snippets}auditevents/filtered/http-response.adoc[]
 
@@ -24,8 +22,8 @@ include::{snippets}auditevents/filtered/http-response.adoc[]
 [[audit-events-retrieving-query-parameters]]
 === Query Parameters
 
-The endpoint uses query parameters to limit the events that it returns. The following
-table shows the supported query parameters:
+The endpoint uses query parameters to limit the events that it returns.
+The following table shows the supported query parameters:
 
 [cols="2,4"]
 include::{snippets}auditevents/filtered/request-parameters.adoc[]
@@ -35,8 +33,8 @@ include::{snippets}auditevents/filtered/request-parameters.adoc[]
 [[audit-events-retrieving-response-structure]]
 === Response Structure
 
-The response contains details of all of the audit events that matched the query. The
-following table describes the structure of the response:
+The response contains details of all of the audit events that matched the query.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}auditevents/all/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/beans.adoc

@@ -8,8 +8,7 @@ The `beans` endpoint provides information about the application's beans.
 [[beans-retrieving]]
 == Retrieving the Beans
 
-To retrieve the beans, make a `GET` request to `/actuator/beans`, as shown in the
-following curl-based example:
+To retrieve the beans, make a `GET` request to `/actuator/beans`, as shown in the following curl-based example:
 
 include::{snippets}beans/curl-request.adoc[]
 
@@ -22,8 +21,8 @@ include::{snippets}beans/http-response.adoc[]
 [[beans-retrieving-response-structure]]
 === Response Structure
 
-The response contains details of the application's beans. The following table describes
-the structure of the response:
+The response contains details of the application's beans.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}beans/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/caches.adoc

@@ -7,8 +7,7 @@ The `caches` endpoint provides access to the application's caches.
 
 [[caches-all]]
 == Retrieving All Caches
-To retrieve the application's caches, make a `GET` request to `/actuator/caches`, as
-shown in the following curl-based example:
+To retrieve the application's caches, make a `GET` request to `/actuator/caches`, as shown in the following curl-based example:
 
 include::{snippets}caches/all/curl-request.adoc[]
 
@@ -20,8 +19,8 @@ include::{snippets}caches/all/http-response.adoc[]
 
 [[caches-all-response-structure]]
 === Response Structure
-The response contains details of the application's caches. The following table describes
-the structure of the response:
+The response contains details of the application's caches.
+The following table describes the structure of the response:
 
 [cols="3,1,3"]
 include::{snippets}caches/all/response-fields.adoc[]
@@ -30,23 +29,22 @@ include::{snippets}caches/all/response-fields.adoc[]
 
 [[caches-named]]
 == Retrieving Caches by Name
-To retrieve a cache by name, make a `GET` request to `/actuator/caches/\{name}`,
-as shown in the following curl-based example:
+To retrieve a cache by name, make a `GET` request to `/actuator/caches/\{name}`, as shown in the following curl-based example:
 
 include::{snippets}caches/named/curl-request.adoc[]
 
-The preceding example retrieves information about the cache named `cities`. The
-resulting response is similar to the following:
+The preceding example retrieves information about the cache named `cities`.
+The resulting response is similar to the following:
 
 include::{snippets}caches/named/http-response.adoc[]
 
 
 
 [[caches-named-query-parameters]]
 === Query Parameters
-If the requested name is specific enough to identify a single cache, no extra parameter is
-required. Otherwise, the `cacheManager` must be specified. The following table shows the
-supported query parameters:
+If the requested name is specific enough to identify a single cache, no extra parameter is required.
+Otherwise, the `cacheManager` must be specified.
+The following table shows the supported query parameters:
 
 [cols="2,4"]
 include::{snippets}caches/named/request-parameters.adoc[]
@@ -55,8 +53,8 @@ include::{snippets}caches/named/request-parameters.adoc[]
 
 [[caches-named-response-structure]]
 === Response Structure
-The response contains details of the requested cache. The following table describes the
-structure of the response:
+The response contains details of the requested cache.
+The following table describes the structure of the response:
 
 [cols="3,1,3"]
 include::{snippets}caches/named/response-fields.adoc[]
@@ -65,30 +63,27 @@ include::{snippets}caches/named/response-fields.adoc[]
 
 [[caches-evict-all]]
 == Evict All Caches
-To clear all available caches, make a `DELETE` request to `/actuator/caches` as shown in
-the following curl-based example:
+To clear all available caches, make a `DELETE` request to `/actuator/caches` as shown in the following curl-based example:
 
 include::{snippets}caches/evict-all/curl-request.adoc[]
 
 
 
 [[caches-evict-named]]
 == Evict a Cache by Name
-To evict a particular cache, make a `DELETE` request to `/actuator/caches/\{name}` as shown
-in the following curl-based example:
+To evict a particular cache, make a `DELETE` request to `/actuator/caches/\{name}` as shown in the following curl-based example:
 
 include::{snippets}caches/evict-named/curl-request.adoc[]
 
-NOTE: As there are two caches named `countries`, the `cacheManager` has to be provided to
-specify which `Cache` should be cleared.
+NOTE: As there are two caches named `countries`, the `cacheManager` has to be provided to specify which `Cache` should be cleared.
 
 
 
 [[caches-evict-named-request-structure]]
 === Request Structure
-If the requested name is specific enough to identify a single cache, no extra parameter is
-required. Otherwise, the `cacheManager` must be specified. The following table shows the
-supported query parameters:
+If the requested name is specific enough to identify a single cache, no extra parameter is required.
+Otherwise, the `cacheManager` must be specified.
+The following table shows the supported query parameters:
 
 [cols="2,4"]
 include::{snippets}caches/evict-named/request-parameters.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/conditions.adoc

@@ -1,16 +1,14 @@
 [[conditions]]
 = Conditions Evaluation Report (`conditions`)
 
-The `conditions` endpoint provides information about the evaluation of conditions on
-configuration and auto-configuration classes.
+The `conditions` endpoint provides information about the evaluation of conditions on configuration and auto-configuration classes.
 
 
 
 [[conditions-retrieving]]
 == Retrieving the Report
 
-To retrieve the report, make a `GET` request to `/actuator/conditions`, as shown in
-the following curl-based example:
+To retrieve the report, make a `GET` request to `/actuator/conditions`, as shown in the following curl-based example:
 
 include::{snippets}conditions/curl-request.adoc[]
 
@@ -23,8 +21,8 @@ include::{snippets}conditions/http-response.adoc[]
 [[conditions-retrieving-response-structure]]
 === Response Structure
 
-The response contains details of the application's condition evaluation. The following
-table describes the structure of the response:
+The response contains details of the application's condition evaluation.
+The following table describes the structure of the response:
 
 [cols="3,1,3"]
 include::{snippets}conditions/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/configprops.adoc

@@ -1,16 +1,14 @@
 [[configprops]]
 = Configuration Properties (`configprops`)
 
-The `configprops` endpoint provides information about the application's
-`@ConfigurationProperties` beans.
+The `configprops` endpoint provides information about the application's `@ConfigurationProperties` beans.
 
 
 
 [[configprops-retrieving]]
 == Retrieving the `@ConfigurationProperties` Bean
 
-To retrieve the `@ConfigurationProperties` beans, make a `GET` request to
-`/actuator/configprops`, as shown in the following curl-based example:
+To retrieve the `@ConfigurationProperties` beans, make a `GET` request to `/actuator/configprops`, as shown in the following curl-based example:
 
 include::{snippets}configprops/curl-request.adoc[]
 
@@ -23,8 +21,8 @@ include::{snippets}configprops/http-response.adoc[]
 [[configprops-retrieving-response-structure]]
 === Response Structure
 
-The response contains details of the application's `@ConfigurationProperties` beans. The
-following table describes the structure of the response:
+The response contains details of the application's `@ConfigurationProperties` beans.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}configprops/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/env.adoc

@@ -8,8 +8,7 @@ The `env` endpoint provides information about the application's `Environment`.
 [[env-entire]]
 == Retrieving the Entire Environment
 
-To retrieve the entire environment, make a `GET` request to `/actuator/env`, as shown in
-the following curl-based example:
+To retrieve the entire environment, make a `GET` request to `/actuator/env`, as shown in the following curl-based example:
 
 include::{snippets}env/all/curl-request.adoc[]
 
@@ -22,8 +21,8 @@ include::{snippets}env/all/http-response.adoc[]
 [[env-entire-response-structure]]
 === Response Structure
 
-The response contains details of the application's `Environment`. The following table
-describes the structure of the response:
+The response contains details of the application's `Environment`.
+The following table describes the structure of the response:
 
 [cols="3,1,3"]
 include::{snippets}env/all/response-fields.adoc[]
@@ -33,13 +32,12 @@ include::{snippets}env/all/response-fields.adoc[]
 [[env-single-property]]
 == Retrieving a Single Property
 
-To retrieve a single property, make a `GET` request to `/actuator/env/{property.name}`,
-as shown in the following curl-based example:
+To retrieve a single property, make a `GET` request to `/actuator/env/{property.name}`, as shown in the following curl-based example:
 
 include::{snippets}env/single/curl-request.adoc[]
 
-The preceding example retrieves information about the property named
-`com.example.cache.max-size`. The resulting response is similar to the following:
+The preceding example retrieves information about the property named `com.example.cache.max-size`.
+The resulting response is similar to the following:
 
 include::{snippets}env/single/http-response.adoc[]
 
@@ -48,8 +46,8 @@ include::{snippets}env/single/http-response.adoc[]
 [[env-single-response-structure]]
 === Response Structure
 
-The response contains details of the requested property. The following table describes the
-structure of the response:
+The response contains details of the requested property.
+The following table describes the structure of the response:
 
 [cols="3,1,3"]
 include::{snippets}env/single/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/flyway.adoc

@@ -8,8 +8,7 @@ The `flyway` endpoint provides information about database migrations performed b
 [[flyway-retrieving]]
 == Retrieving the Migrations
 
-To retrieve the migrations, make a `GET` request to `/actuator/flyway`, as shown in the
-following curl-based example:
+To retrieve the migrations, make a `GET` request to `/actuator/flyway`, as shown in the following curl-based example:
 
 include::{snippets}flyway/curl-request.adoc[]
 
@@ -22,8 +21,8 @@ include::{snippets}flyway/http-response.adoc[]
 [[flyway-retrieving-response-structure]]
 === Response Structure
 
-The response contains details of the application's Flyway migrations. The following table
-describes the structure of the response:
+The response contains details of the application's Flyway migrations.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}flyway/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/health.adoc

@@ -6,8 +6,7 @@ The `health` endpoint provides detailed information about the health of the appl
 
 [[health-retrieving]]
 == Retrieving the Health of the application
-To retrieve the health of the application, make a `GET` request to `/actuator/health`,
-as shown in the following curl-based example:
+To retrieve the health of the application, make a `GET` request to `/actuator/health`, as shown in the following curl-based example:
 
 include::{snippets}health/curl-request.adoc[]
 
@@ -19,8 +18,8 @@ include::{snippets}health/http-response.adoc[]
 
 [[health-retrieving-response-structure]]
 === Response Structure
-The response contains details of the health of the application. The following table
-describes the structure of the response:
+The response contains details of the health of the application.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}health/response-fields.adoc[]
@@ -29,8 +28,7 @@ include::{snippets}health/response-fields.adoc[]
 
 [[health-retrieving-component]]
 == Retrieving the Health of a component
-To retrieve the health of a particular component of the application, make a `GET` request
-to `/actuator/health/\{component}`, as shown in the following curl-based example:
+To retrieve the health of a particular component of the application, make a `GET` request to `/actuator/health/\{component}`, as shown in the following curl-based example:
 
 include::{snippets}health/component/curl-request.adoc[]
 
@@ -52,10 +50,7 @@ include::{snippets}health/component/response-fields.adoc[]
 
 [[health-retrieving-component-instance]]
 == Retrieving the Health of a component instance
-If a particular component consists of multiple instances (as the `broker` indicator in
-the example above), the health of a particular instance of that component can be retrieved
-by issuing a `GET` request to `/actuator/health/\{component}/\{instance}`, as shown in the
-following curl-based example:
+If a particular component consists of multiple instances (as the `broker` indicator in the example above), the health of a particular instance of that component can be retrieved by issuing a `GET` request to `/actuator/health/\{component}/\{instance}`, as shown in the following curl-based example:
 
 include::{snippets}health/instance/curl-request.adoc[]
 
@@ -67,8 +62,8 @@ include::{snippets}health/instance/http-response.adoc[]
 
 [[health-retrieving-component-instance-response-structure]]
 === Response Structure
-The response contains details of the health of an instance of a particular component of
-the application. The following table describes the structure of the response:
+The response contains details of the health of an instance of a particular component of the application.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}health/instance/response-fields.adoc[]

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/heapdump.adoc

@@ -8,13 +8,11 @@ The `heapdump` endpoint provides a heap dump from the application's JVM.
 [[heapdump-retrieving]]
 == Retrieving the Heap Dump
 
-To retrieve the heap dump, make a `GET` request to `/actuator/heapdump`. The response
-is binary data in https://docs.oracle.com/javase/8/docs/technotes/samples/hprof.html[
-HPROF] format and can be large. Typically, you should save the response to disk for
-subsequent analysis. When using curl, this can be achieved by using the `-O` option,
-as shown in the following example:
+To retrieve the heap dump, make a `GET` request to `/actuator/heapdump`.
+The response is binary data in https://docs.oracle.com/javase/8/docs/technotes/samples/hprof.html[HPROF] format and can be large.
+Typically, you should save the response to disk for subsequent analysis.
+When using curl, this can be achieved by using the `-O` option, as shown in the following example:
 
 include::{snippets}heapdump/curl-request.adoc[]
 
-The preceding example results in a file named `heapdump` being written to the current
-working directory.
+The preceding example results in a file named `heapdump` being written to the current working directory.

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/asciidoc/endpoints/httptrace.adoc

@@ -8,8 +8,7 @@ The `httptrace` endpoint provides information about HTTP request-response exchan
 [[http-trace-retrieving]]
 == Retrieving the Traces
 
-To retrieve the traces, make a `GET` request to `/actuator/httptrace`, as shown in the
-following curl-based example:
+To retrieve the traces, make a `GET` request to `/actuator/httptrace`, as shown in the following curl-based example:
 
 include::{snippets}httptrace/curl-request.adoc[]
 
@@ -22,8 +21,8 @@ include::{snippets}httptrace/http-response.adoc[]
 [[http-trace-retrieving-response-structure]]
 === Response Structure
 
-The response contains details of the traced HTTP request-response exchanges. The
-following table describes the structure of the response:
+The response contains details of the traced HTTP request-response exchanges.
+The following table describes the structure of the response:
 
 [cols="2,1,3"]
 include::{snippets}httptrace/response-fields.adoc[]