Make editorial changes to actuator documentation

See gh-27759

Author: Jay Bryant

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

@@ -40,11 +40,11 @@ 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.
+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/endpoints.adoc

@@ -6,13 +6,13 @@ You can turn it on by setting the configprop:spring.jmx.enabled[] configuration
 Spring Boot exposes the most suitable `MBeanServer` as a bean with an ID of `mbeanServer`.
 Any of your beans that are annotated with Spring JMX annotations (`@ManagedResource`, `@ManagedAttribute`, or `@ManagedOperation`) are exposed to it.
 
-If your platform provides a standard `MBeanServer`, Spring Boot will use that and default to the VM `MBeanServer` if necessary.
-If all that fails, a new `MBeanServer` will be created.
+If your platform provides a standard `MBeanServer`, Spring Boot uses that and defaults to the VM `MBeanServer`, if necessary.
+If all that fails, a new `MBeanServer` is created.
 
 See the {spring-boot-autoconfigure-module-code}/jmx/JmxAutoConfiguration.java[`JmxAutoConfiguration`] class for more details.
 
-Spring Boot also exposes management endpoints as JMX MBeans under the `org.springframework.boot` domain by default.
-To Take full control over endpoints registration in the JMX domain, consider registering your own `EndpointObjectNameFactory` implementation.
+By default, Spring Boot also exposes management endpoints as JMX MBeans under the `org.springframework.boot` domain.
+To take full control over endpoint registration in the JMX domain, consider registering your own `EndpointObjectNameFactory` implementation.
 
 
 
@@ -73,8 +73,8 @@ You can then expose the Jolokia endpoint by adding `jolokia` or `*` to the confi
 You can then access it by using `/actuator/jolokia` on your management HTTP server.
 
 NOTE: The Jolokia endpoint exposes Jolokia's servlet as an actuator endpoint.
-As a result, it is specific to servlet environments such as Spring MVC and Jersey.
-The endpoint will not be available in a WebFlux application.
+As a result, it is specific to servlet environments, such as Spring MVC and Jersey.
+The endpoint is not available in a WebFlux application.
 
 
 

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

@@ -5,7 +5,7 @@ The default convention is to use the `id` of the endpoint with a prefix of `/act
 For example, `health` is exposed as `/actuator/health`.
 
 TIP: Actuator is supported natively with Spring MVC, Spring WebFlux, and Jersey.
-If both Jersey and Spring MVC are available, Spring MVC will be used.
+If both Jersey and Spring MVC are available, Spring MVC is used.
 
 NOTE: Jackson is a required dependency in order to get the correct JSON responses as documented in the API documentation ({spring-boot-actuator-restapi-docs}[HTML] or {spring-boot-actuator-restapi-pdfdocs}[PDF]).
 
@@ -27,7 +27,7 @@ You can use the configprop:management.endpoints.web.base-path[] property to chan
 
 The preceding `application.properties` example changes the endpoint from `/actuator/\{id}` to `/manage/\{id}` (for example, `/manage/info`).
 
-NOTE: Unless the management port has been configured to <<actuator#actuator.monitoring.customizing-management-server-port,expose endpoints by using a different HTTP port>>, `management.endpoints.web.base-path` is relative to `server.servlet.context-path` (Servlet web applications) or `spring.webflux.base-path` (reactive web applications).
+NOTE: Unless the management port has been configured to <<actuator#actuator.monitoring.customizing-management-server-port,expose endpoints by using a different HTTP port>>, `management.endpoints.web.base-path` is relative to `server.servlet.context-path` (for servlet web applications) or `spring.webflux.base-path` (for reactive web applications).
 If `management.server.port` is configured, `management.endpoints.web.base-path` is relative to `management.server.base-path`.
 
 If you want to map endpoints to a different path, you can use the configprop:management.endpoints.web.path-mapping[] property.
@@ -60,15 +60,15 @@ You can set the configprop:management.server.port[] property to change the HTTP
 	    port: 8081
 ----
 
-NOTE: On Cloud Foundry, applications only receive requests on port 8080 for both HTTP and TCP routing, by default.
-If you want to use a custom management port on Cloud Foundry, you will need to explicitly set up the application's routes to forward traffic to the custom port.
+NOTE: On Cloud Foundry, by default, applications receive requests only on port 8080 for both HTTP and TCP routing.
+If you want to use a custom management port on Cloud Foundry, you need to explicitly set up the application's routes to forward traffic to the custom port.
 
 
 
 [[actuator.monitoring.management-specific-ssl]]
 === Configuring Management-specific SSL
-When configured to use a custom port, the management server can also be configured with its own SSL by using the various `management.server.ssl.*` properties.
-For example, doing so lets a management server be available over HTTP while the main application uses HTTPS, as shown in the following property settings:
+When configured to use a custom port, you can also configure the management server with its own SSL by using the various `management.server.ssl.*` properties.
+For example, doing so lets a management server be available over HTTP while the main application uses HTTPS, as the following property settings show:
 
 [source,yaml,indent=0,subs="verbatim",configprops,configblocks]
 ----
@@ -108,7 +108,7 @@ Alternatively, both the main server and the management server can use SSL but wi
 
 [[actuator.monitoring.customizing-management-server-address]]
 === Customizing the Management Server Address
-You can customize the address that the management endpoints are available on by setting the configprop:management.server.address[] property.
+You can customize the address on which the management endpoints are available by setting the configprop:management.server.address[] property.
 Doing so can be useful if you want to listen only on an internal or ops-facing network or to listen only for connections from `localhost`.
 
 NOTE: You can listen on a different address only when the port differs from the main server port.

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

@@ -2,10 +2,10 @@
 == Process Monitoring
 In the `spring-boot` module, you can find two classes to create files that are often useful for process monitoring:
 
-* `ApplicationPidFileWriter` creates a file containing the application PID (by default, in the application directory with a file name of `application.pid`).
-* `WebServerPortFileWriter` creates a file (or files) containing the ports of the running web server (by default, in the application directory with a file name of `application.port`).
+* `ApplicationPidFileWriter` creates a file that contains the application PID (by default, in the application directory with a file name of `application.pid`).
+* `WebServerPortFileWriter` creates a file (or files) that contain the ports of the running web server (by default, in the application directory with a file name of `application.port`).
 
-By default, these writers are not activated, but you can enable:
+By default, these writers are not activated, but you can enable them:
 
 * <<actuator#actuator.process-monitoring.configuration,By Extending Configuration>>
 * <<actuator#actuator.process-monitoring.programmatically>>
@@ -14,7 +14,7 @@ By default, these writers are not activated, but you can enable:
 
 [[actuator.process-monitoring.configuration]]
 === Extending Configuration
-In the `META-INF/spring.factories` file, you can activate the listener(s) that writes a PID file, as shown in the following example:
+In the `META-INF/spring.factories` file, you can activate the listener (or listeners) that writes a PID file:
 
 [indent=0]
 ----
@@ -26,6 +26,6 @@ In the `META-INF/spring.factories` file, you can activate the listener(s) that w
 
 
 [[actuator.process-monitoring.programmatically]]
-=== Programmatically
+=== Programmatically Enabling Process Monitoring
 You can also activate a listener by invoking the `SpringApplication.addListeners(...)` method and passing the appropriate `Writer` object.
 This method also lets you customize the file name and path in the `Writer` constructor.

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

@@ -1,10 +1,10 @@
 [[actuator.tracing]]
 == HTTP Tracing
 You can enable HTTP Tracing by providing a bean of type `HttpTraceRepository` in your application's configuration.
-For convenience, Spring Boot offers an `InMemoryHttpTraceRepository` that stores traces for the last 100 request-response exchanges, by default.
-`InMemoryHttpTraceRepository` is limited compared to other tracing solutions and we recommend using it only for development environments.
-For production environments, use of a production-ready tracing or observability solution, such as Zipkin or Spring Cloud Sleuth, is recommended.
-Alternatively, create your own `HttpTraceRepository` that meets your needs.
+For convenience, Spring Boot offers `InMemoryHttpTraceRepository`, which stores traces for the last 100 (the default) request-response exchanges.
+`InMemoryHttpTraceRepository` is limited compared to other tracing solutions, and we recommend using it only for development environments.
+For production environments, we recommend using a production-ready tracing or observability solution, such as Zipkin or Spring Cloud Sleuth.
+Alternatively, you can create your own `HttpTraceRepository`.
 
 You can use the `httptrace` endpoint to obtain information about the request-response exchanges that are stored in the `HttpTraceRepository`.