Polish documentation

Author: philwebb

spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator/endpoints.adoc

@@ -158,7 +158,7 @@ This property takes precedence over the default access or an individual endpoint
 Set it to `none` to make all endpoints inaccessible.
 Set it to `read-only` to only allow read access to endpoints.
 
-For `@Endpoint`, `@JmxEndpoint`, and `@WebEndpoint`, read access equates to the endpoint methods annotated with `@ReadEndpoint`.
+For `@Endpoint`, `@JmxEndpoint`, and `@WebEndpoint`, read access equates to the endpoint methods annotated with `@ReadOperation`.
 For `@ControllerEndpoint` and `@RestControllerEndpoint`, read access equates to request mappings that can handle `GET` and `HEAD` requests.
 For `@ServletEndpoint`, read access equates to `GET` and `HEAD` requests.
 
@@ -674,7 +674,7 @@ TIP: The `ssl` `HealthIndicator` has a "warning threshold" property named config
 If an SSL certificate will be invalid within the time span defined by this threshold, the `HealthIndicator` will warn you but it will still return HTTP 200 to not disrupt the application.
 You can use this threshold to give yourself enough lead time to rotate the soon to be expired certificate.
 
-Additional `HealthIndicators` beans are available but are not enabled by default:
+Additional `HealthIndicator` beans are available but are not enabled by default:
 
 [cols="3,4,6"]
 |===

spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/logging.adoc

@@ -618,7 +618,7 @@ You can also declare implementations by listing them in a `META-INF/spring.facto
 === Supporting Other Structured Logging Formats
 
 The structured logging support in Spring Boot is extensible, allowing you to define your own custom format.
-To do this, implement the `StructuredLoggingFormatter` interface. The generic type argument has to be `ILoggingEvent` when using Logback and `LogEvent` when using Log4j2 (that means your implementation is tied to a specific logging system).
+To do this, implement the `StructuredLogFormatter` interface. The generic type argument has to be `ILoggingEvent` when using Logback and `LogEvent` when using Log4j2 (that means your implementation is tied to a specific logging system).
 Your implementation is then called with the log event and returns the `String` to be logged, as seen in this example:
 
 include-code::MyCustomFormat[]