Polish

See gh-39910

Author: izeye

spring-boot-project/spring-boot-autoconfigure/src/test/java/org/springframework/boot/autoconfigure/liquibase/LiquibasePropertiesTests.java

@@ -35,7 +35,7 @@
  *
  * @author Andy Wilkinson
  */
-public class LiquibasePropertiesTests {
+class LiquibasePropertiesTests {
 
 	@Test
 	void valuesOfShowSummaryMatchValuesOfUpdateSummaryEnum() {

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

@@ -1203,7 +1203,7 @@ The `info` endpoint publishes information about your Operating System, see {spri
 
 [[actuator.endpoints.info.process-information]]
 ==== Process Information
-The `info` endpoint publishes information about your process, see {spring-boot-module-api}/info/ProcessInfo.html[`Process`] for more details.
+The `info` endpoint publishes information about your process, see {spring-boot-module-api}/info/ProcessInfo.html[`ProcessInfo`] for more details.
 
 
 

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

@@ -72,7 +72,7 @@ To learn more about ahead-of-time processing, please see the <<native-image#nati
 https://wiki.openjdk.org/display/crac/Main[Coordinated Restore at Checkpoint] (CRaC) is an OpenJDK project that defines a new Java API to allow you to checkpoint and restore an application on the HotSpot JVM.
 It is based on https://github.com/checkpoint-restore/criu[CRIU], a project that implements checkpoint/restore functionality on Linux.
 
-The principle is the following: you start your application almost as usual but with a CRaC enabled version of the JDK like https://bell-sw.com/pages/downloads/?package=jdk-crac[Bellsoft Liberica JDK with CRaC] or https://www.azul.com/downloads/?package=jdk-crac#zulu[Azul Zulu JDK with CRaC].
+The principle is the following: you start your application almost as usual but with a CRaC enabled version of the JDK like https://bell-sw.com/pages/downloads/?package=jdk-crac[BellSoft Liberica JDK with CRaC] or https://www.azul.com/downloads/?package=jdk-crac#zulu[Azul Zulu JDK with CRaC].
 Then at some point, potentially after some workloads that will warm up your JVM by executing all common code paths, you trigger a checkpoint using an API call, a `jcmd` command, an HTTP endpoint, or a different mechanism.
 
 A memory representation of the running JVM, including its warmness, is then serialized to disk, allowing a fast restoration at a later point, potentially on another machine with a similar operating system and CPU architecture.

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

@@ -80,7 +80,7 @@ When used to secure a client-side connection, a `truststore` is typically config
 [TIP]
 ====
 PEM content can be used directly for both the `certificate` and `private-key` properties.
-If the property values contains `BEGIN` and `END` markers then they will be treated as PEM content rather than a resource location.
+If the property values contain `BEGIN` and `END` markers then they will be treated as PEM content rather than a resource location.
 
 The following example shows how a truststore certificate can be defined:
 

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

@@ -1055,7 +1055,7 @@ include::code:MyRedisConfiguration[]
 
 Spring Boot can't tell from `GenericContainer` which container image is used, so the `name` attribute from `@ServiceConnection` must be used to provide that hint.
 
-You can also can use the `name` attribute of `@ServiceConnection` to override which connection detail will be used, for example when using custom images.
+You can also use the `name` attribute of `@ServiceConnection` to override which connection detail will be used, for example when using custom images.
 If you are using the Docker image `registry.mycompany.com/mirror/myredis`, you'd use `@ServiceConnection(name="redis")` to ensure `RedisConnectionDetails` are created.
 
 

spring-boot-project/spring-boot-test-autoconfigure/src/main/java/org/springframework/boot/test/autoconfigure/actuate/observability/AutoConfigureObservability.java

@@ -30,7 +30,7 @@
  * observability.
  * <p>
  * If this annotation is applied to a sliced test, an in-memory {@code MeterRegistry}, a
- * no-op {@code Tracer} and an {@code ObservationRegistry} is added to the application
+ * no-op {@code Tracer} and an {@code ObservationRegistry} are added to the application
  * context.
  *
  * @author Moritz Halbritter

spring-boot-project/spring-boot-testcontainers/src/test/java/org/springframework/boot/testcontainers/lifecycle/TestContainersParallelStartupWithImportTestcontainersIntegrationTests.java

@@ -44,7 +44,7 @@
 @DisabledIfDockerUnavailable
 @ExtendWith(OutputCaptureExtension.class)
 @ImportTestcontainers(Containers.class)
-public class TestContainersParallelStartupWithImportTestcontainersIntegrationTests {
+class TestContainersParallelStartupWithImportTestcontainersIntegrationTests {
 
 	@Test
 	void startsInParallel(CapturedOutput out) {

spring-boot-project/spring-boot-tools/spring-boot-loader/src/test/java/org/springframework/boot/loader/launch/JarFileArchiveTests.java

@@ -113,7 +113,7 @@ void getClassPathUrlsWhenHasUnpackCommentUnpacksAndReturnsUrls() throws Exceptio
 		URL url = urls.iterator().next();
 		assertThat(url).isNotEqualTo(JarUrl.create(this.file, "nested.jar"));
 		// The unpack URL must be a raw file URL (see gh-38833)
-		assertThat(url.toString()).startsWith("file:").endsWith("/nested.jar").doesNotStartWith("jar:");
+		assertThat(url.toString()).startsWith("file:").endsWith("/nested.jar");
 	}
 
 	@Test

spring-boot-project/spring-boot/src/main/java/org/springframework/boot/context/properties/bind/DataObjectBinder.java

@@ -61,7 +61,7 @@ <T> T bind(ConfigurationPropertyName name, Bindable<T> target, Context context,
 	 * @param context the bind context
 	 * @param exception the exception about to be thrown
 	 */
-	default <T> void onUnableToCreateInstance(Bindable<T> target, Binder.Context context, RuntimeException exception) {
+	default <T> void onUnableToCreateInstance(Bindable<T> target, Context context, RuntimeException exception) {
 	}
 
 }

spring-boot-project/spring-boot/src/main/java/org/springframework/boot/diagnostics/analyzer/MissingParameterNamesFailureAnalyzer.java

@@ -39,7 +39,7 @@ class MissingParameterNamesFailureAnalyzer implements FailureAnalyzer {
 
 	static final String POSSIBILITY = "This may be due to missing parameter name information";
 
-	static String ACTION = """
+	static final String ACTION = """
 			Ensure that your compiler is configured to use the '-parameters' flag.
 			You may need to update both your build tool settings as well as your IDE.
 			(See https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x#parameter-name-retention)