Polish

Closes gh-11050

spring-boot-project/spring-boot-docs/src/main/asciidoc/appendix-application-properties.adoc

@@ -1258,7 +1258,7 @@ content into your application; rather pick only the properties that you need.
 	spring.metrics.export.atlas.enabled= # Enable publishing to the backend.
 	spring.metrics.export.atlas.eval-uri= # URI for the Atlas LWC endpoint to evaluate the data for a subscription.
 	spring.metrics.export.atlas.lwc-enabled= # Enable streaming to Atlas LWC.
-	spring.metrics.export.atlas.meter-time-to-live= # Time to love for meters that do not have any activity. After this period the meter will be considered expired and will not get reported.
+	spring.metrics.export.atlas.meter-time-to-live= # Time to live for meters that do not have any activity. After this period the meter will be considered expired and will not get reported.
 	spring.metrics.export.atlas.num-threads= # Number of threads to use with the metrics publishing scheduler.
 	spring.metrics.export.atlas.read-timeout= # Read timeout for requests to the backend.
 	spring.metrics.export.atlas.step=1 # Step size (i.e. reporting frequency) to use.

spring-boot-project/spring-boot-docs/src/main/asciidoc/deployment.adoc

@@ -231,7 +231,7 @@ Your application should now be up and running on Heroku.
 [[cloud-deployment-openshift]]
 === OpenShift
 https://www.openshift.com/[OpenShift] is the Red Hat public (and enterprise) extension of
-the Kubernetes container orchestration platform.  Similarly to Kubernetes, OpenShift has
+the Kubernetes container orchestration platform. Similarly to Kubernetes, OpenShift has
 many options for installing Spring Boot based applications.
 
 OpenShift has many resources describing how to deploy Spring Boot applications, which

spring-boot-project/spring-boot-docs/src/main/asciidoc/index.adoc

@@ -40,7 +40,7 @@ Phillip Webb; Dave Syer; Josh Long; Stéphane Nicoll; Rob Winch; Andy Wilkinson;
 :spring-reference: http://docs.spring.io/spring/docs/{spring-docs-version}/spring-framework-reference/
 :spring-security-reference: http://docs.spring.io/spring-security/site/docs/{spring-security-docs-version}/reference/htmlsingle
 :spring-security-oauth2-reference: http://projects.spring.io/spring-security-oauth/docs/oauth2.html
-:spring-webservices-reference: http://docs.spring.io/spring-ws/docs/{spring-webservices-docs-version}/reference/htmlsingle
+:spring-webservices-reference: http://docs.spring.io/spring-ws/docs/{spring-webservices-docs-version}/reference/
 :spring-javadoc: http://docs.spring.io/spring/docs/{spring-docs-version}/javadoc-api/org/springframework
 :spring-amqp-javadoc: http://docs.spring.io/spring-amqp/docs/current/api/org/springframework/amqp
 :spring-batch-javadoc: http://docs.spring.io/spring-batch/apidocs/org/springframework/batch

spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -181,7 +181,7 @@ register an `EndpointFilter` bean.
 === Securing HTTP Endpoints
 You should take care to secure HTTP endpoints in the same way that you would any other
 sensitive URL. Spring Boot will not apply any security on your behalf, however, it does
-provide some convenient `ReqestMatchers` that can be used in combination with Spring
+provide some convenient `RequestMatcher`s that can be used in combination with Spring
 Security.
 
 A typical Spring Security configuration could look something like this:
@@ -203,7 +203,7 @@ A typical Spring Security configuration could look something like this:
 ----
 
 The above uses `EndpointRequest.toAnyEndpoint()` to match a request to any endpoint, then
-ensure that thet all have the `ENDPOINT_ADMIN` role. Several other matcher methods are
+ensure that all have the `ENDPOINT_ADMIN` role. Several other matcher methods are
 also available on `EndpointRequest` (see the API documentation for details).
 
 If you deploy applications behind a firewall, you may prefer that all your actuator
@@ -221,7 +221,7 @@ endpoints can be accessed without requiring authentication. You can do so by cha
 [[production-ready-customizing-endpoints]]
 === Customizing Endpoints
 Endpoints can be customized by using Spring properties. You can change whether an
-endpoint is `enabled` and the amount of time it will cache reponses.
+endpoint is `enabled` and the amount of time it will cache responses.
 
 For example, the following `application.properties` changes the time-to-live of the
 `beans` endpoint and also enables `shutdown`:
@@ -242,7 +242,7 @@ disable _all_ endpoints except for `info`:
 
 [source,properties,indent=0]
 ----
-	management.endpoints.enabled-by-default=flase
+	management.endpoints.enabled-by-default=false
 	management.endpoint.info.enabled=true
 ----
 
@@ -308,7 +308,7 @@ TIP: See {sc-spring-boot-actuator-autoconfigure}/endpoint/web/servlet/CorsEndpoi
 [[production-ready-customizing-endpoints-programmatically]]
 === Adding Custom Endpoints
 If you add a `@Bean` annotated with `@Endpoint`, any methods annotated with
-`@ReadOperation`, `@WriteOperation` or `@DeleteOperaion` are automatically exposed over
+`@ReadOperation`, `@WriteOperation` or `@DeleteOperation` are automatically exposed over
 JMX and, in a web application, over HTTP as well.
 
 You can also write technology specific endpoints by using `@JmxEndpoint` or

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -574,7 +574,7 @@ following:
 
 Alternatively, when custom config locations are configured by using
 `spring.config.addition-location`, they are used in addition to the default locations.
-Additional locations are search before the default locations. For example, if
+Additional locations are searched before the default locations. For example, if
 additional locations of `classpath:/custom-config/,file:./custom-config/` are configured,
 the search order becomes the following: