Merge pull request #27759 from Buzzardo

* pr/27759:
  Make editorial changes to actuator documentation
  Update actuator docs to prefer "You can..."
  Improve actuator example lead-in text
  Polish actuator docs markup and formatting

Closes gh-27759

Author: philwebb

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/auditing.adoc

@@ -3,9 +3,9 @@
 Once Spring Security is in play, Spring Boot Actuator has a flexible audit framework that publishes events (by default, "`authentication success`", "`failure`" and "`access denied`" exceptions).
 This feature can be very useful for reporting and for implementing a lock-out policy based on authentication failures.
 
-Auditing can be enabled by providing a bean of type `AuditEventRepository` in your application's configuration.
+You can enable auditing by providing a bean of type `AuditEventRepository` in your application's configuration.
 For convenience, Spring Boot offers an `InMemoryAuditEventRepository`.
-`InMemoryAuditEventRepository` has limited capabilities and we recommend using it only for development environments.
+`InMemoryAuditEventRepository` has limited capabilities, and we recommend using it only for development environments.
 For production environments, consider creating your own alternative `AuditEventRepository` implementation.
 
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/cloud-foundry.adoc

@@ -4,18 +4,17 @@ Spring Boot's actuator module includes additional support that is activated when
 The `/cloudfoundryapplication` path provides an alternative secured route to all `@Endpoint` beans.
 
 The extended support lets Cloud Foundry management UIs (such as the web application that you can use to view deployed applications) be augmented with Spring Boot actuator information.
-For example, an application status page may include full health information instead of the typical "`running`" or "`stopped`" status.
+For example, an application status page can include full health information instead of the typical "`running`" or "`stopped`" status.
 
 NOTE: The `/cloudfoundryapplication` path is not directly accessible to regular users.
-In order to use the endpoint, a valid UAA token must be passed with the request.
+To use the endpoint, you must pass a valid UAA token with the request.
 
 
 
 [[actuator.cloud-foundry.disable]]
 === Disabling Extended Cloud Foundry Actuator Support
 If you want to fully disable the `/cloudfoundryapplication` endpoints, you can add the following setting to your `application.properties` file:
 
-
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
 	management:
@@ -41,12 +40,12 @@ If your Cloud Foundry UAA or Cloud Controller services use self-signed certifica
 
 [[actuator.cloud-foundry.custom-context-path]]
 === Custom Context Path
-If the server's context-path has been configured to anything other than `/`, the Cloud Foundry endpoints will not be available at the root of the application.
-For example, if `server.servlet.context-path=/app`, Cloud Foundry endpoints will be available at `/app/cloudfoundryapplication/*`.
+If the server's context-path has been configured to anything other than `/`, the Cloud Foundry endpoints are not available at the root of the application.
+For example, if `server.servlet.context-path=/app`, Cloud Foundry endpoints are available at `/app/cloudfoundryapplication/*`.
 
-If you expect the Cloud Foundry endpoints to always be available at `/cloudfoundryapplication/*`, regardless of the server's context-path, you will need to explicitly configure that in your application.
-The configuration will differ depending on the web server in use.
-For Tomcat, the following configuration can be added:
+If you expect the Cloud Foundry endpoints to always be available at `/cloudfoundryapplication/*`, regardless of the server's context-path, you need to explicitly configure that in your application.
+The configuration differs, depending on the web server in use.
+For Tomcat, you can add the following configuration:
 
 [source,java,indent=0,subs="verbatim"]
 ----

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/enabling.adoc

@@ -1,15 +1,15 @@
 [[actuator.enabling]]
 == Enabling Production-ready Features
 The {spring-boot-code}/spring-boot-project/spring-boot-actuator[`spring-boot-actuator`] module provides all of Spring Boot's production-ready features.
-The recommended way to enable the features is to add a dependency on the `spring-boot-starter-actuator` '`Starter`'.
+The recommended way to enable the features is to add a dependency on the `spring-boot-starter-actuator` "`Starter`".
 
 .Definition of Actuator
 ****
 An actuator is a manufacturing term that refers to a mechanical device for moving or controlling something.
 Actuators can generate a large amount of motion from a small change.
 ****
 
-To add the actuator to a Maven based project, add the following '`Starter`' dependency:
+To add the actuator to a Maven-based project, add the following '`Starter`' dependency:
 
 [source,xml,indent=0,subs="verbatim"]
 ----