Polish

Closes gh-11510

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

@@ -139,10 +139,10 @@ content into your application. Rather, pick only the properties that you need.
 	spring.profiles.include= # Unconditionally activate the specified comma-separated list of profiles (or list of profiles if using YAML).
 
 	# QUARTZ SCHEDULER ({sc-spring-boot-autoconfigure}/quartz/QuartzProperties.{sc-ext}[QuartzProperties])
-	spring.quartz.job-store-type=memory # Quartz job store type.
-	spring.quartz.properties.*= # Additional Quartz Scheduler properties.
 	spring.quartz.jdbc.initialize-schema=embedded # Database schema initialization mode.
 	spring.quartz.jdbc.schema=classpath:org/quartz/impl/jdbcjobstore/tables_@@platform@@.sql # Path to the SQL file to use to initialize the database schema.
+	spring.quartz.job-store-type=memory # Quartz job store type.
+	spring.quartz.properties.*= # Additional Quartz Scheduler properties.
 
 	# REACTOR ({sc-spring-boot-autoconfigure}/reactor/core/ReactorCoreProperties.{sc-ext}[ReactorCoreProperties])
 	spring.reactor.stacktrace-mode.enabled=false # Whether Reactor should collect stacktrace information at runtime.
@@ -1085,7 +1085,7 @@ content into your application. Rather, pick only the properties that you need.
 	management.server.add-application-context-header=false # Add the "X-Application-Context" HTTP header in each response. Requires a custom management.server.port.
 	management.server.address= # Network address that to which the management endpoints should bind. Requires a custom management.server.port.
 	management.server.port= # Management endpoint HTTP port. Uses the same port as the application by default. Configure a different port to use management-specific SSL.
-	management.server.servlet.context-path= # Management endpoint context-path. For instance, `/management`. Requires a custom management.server.port
+	management.server.servlet.context-path= # Management endpoint context-path. For instance, `/management`. Requires a custom management.server.port.
 	management.server.ssl.ciphers= # Supported SSL ciphers. Requires a custom management.port.
 	management.server.ssl.client-auth= # Whether client authentication is wanted ("want") or needed ("need"). Requires a trust store. Requires a custom management.server.port.
 	management.server.ssl.enabled= # Whether to enable SSL support. Requires a custom management.server.port.

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

@@ -957,7 +957,7 @@ for all requests. Alternatively, when set to `false`, you can enable instrumenta
 adding `@Timed` to a request-handling method.
 
 By default, metrics are generated with the name, `http.server.requests`. The name can be
-customized by setting the `management.metrics.web.server.requests-metrics-name` property.
+customized by setting the `management.metrics.web.server.requests-metric-name` property.
 
 
 
@@ -980,7 +980,7 @@ controllers. You can also use a helper class, `RouterFunctionMetrics`, to instru
 applications that use WebFlux's functional programming model.
 
 By default, metrics are generated with the name `http.server.requests`. You can customize
-the name by setting the `management.metrics.web.server.requests-metrics-name` property.
+the name by setting the `management.metrics.web.server.requests-metric-name` property.
 
 
 
@@ -1015,7 +1015,7 @@ instrumentation of its requests. `MetricsRestTemplateCustomizer` can be used to
 your own `RestTemplate` instances.
 
 By default, metrics are generated with the name, `http.client.requests`. The name can be
-customized by setting the `management.metrics.web.client.requests-metrics-name` property.
+customized by setting the `management.metrics.web.client.requests-metric-name` property.
 
 
 

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

@@ -4391,7 +4391,7 @@ materialized by the `org.springframework.cache.Cache` and
 
 If you have not defined a bean of type `CacheManager` or a `CacheResolver` named
 `cacheResolver` (see
-{spring-javadoc}cache/annotation/CachingConfigurer.html[`CachingConfigurer`]),
+{spring-javadoc}/cache/annotation/CachingConfigurer.html[`CachingConfigurer`]),
 Spring Boot tries to detect the following providers (in the indicated order):
 
 . <<boot-features-caching-provider-generic,Generic>>
@@ -5406,7 +5406,7 @@ property with a different value for each instance of your application.
 
 [[boot-features-jta-bitronix]]
 === Using a Bitronix Transaction Manager
-https://github.com/bitronix/btm[Bitronix] is a  spopular open-source JTA transaction
+https://github.com/bitronix/btm[Bitronix] is a popular open-source JTA transaction
 manager implementation. You can use the `spring-boot-starter-jta-bitronix` starter to add
 the appropriate Bitronix dependencies to your project. As with Atomikos, Spring Boot
 automatically configures Bitronix and post-processes your beans to ensure that startup and
@@ -6158,7 +6158,7 @@ A list of the auto-configuration settings that are enabled by `@WebMvcTest` can
 
 [[boot-features-testing-spring-boot-applications-testing-autoconfigured-webflux-tests]]
 ==== Auto-configured Spring WebFlux Tests
-To test that {spring-reference}html/web-reactive.html[Spring WebFlux] controllers are
+To test that {spring-reference}/web-reactive.html[Spring WebFlux] controllers are
 working as expected, you can use the `@WebFluxTest` annotation. `@WebFluxTest`
 auto-configures the Spring WebFlux infrastructure and limits scanned beans to
 `@Controller`, `@ControllerAdvice`, `@JsonComponent`, `Converter`, `GenericConverter`, and
@@ -6444,7 +6444,7 @@ configures Spring Data Neo4j repositories. Regular `@Component` beans are not lo
 the `ApplicationContext`. (For more about using Neo4J with Spring Boot, see
 "<<boot-features-neo4j>>", earlier in this chapter.)
 
-The followig example shows a typical setup for using Neo4J tests in Spring Boot:
+The following example shows a typical setup for using Neo4J tests in Spring Boot:
 
 [source,java,indent=0]
 ----