Polish

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/r2dbc/R2dbcObservationAutoConfiguration.java

@@ -50,6 +50,7 @@ public class R2dbcObservationAutoConfiguration {
 
 	/**
 	 * {@code @Order} value of the observation customizer.
+	 * @since 3.4.0
 	 */
 	public static final int R2DBC_PROXY_OBSERVATION_CUSTOMIZER_ORDER = 0;
 

spring-boot-project/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/graphql/GraphQlProperties.java

@@ -220,7 +220,7 @@ public static class Websocket {
 		/**
 		 * Maximum idle period before a server keep-alive ping is sent to client.
 		 */
-		private Duration keepAlive = null;
+		private Duration keepAlive;
 
 		public String getPath() {
 			return this.path;

spring-boot-project/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration.java

@@ -182,7 +182,7 @@ static class CustomizerConfiguration {
 
 		@Bean
 		@ConditionalOnBean(Customizer.class)
-		SpringLiquibaseCustomizer customizerSpringLiquibaseCustomizer(Customizer<Liquibase> customizer) {
+		SpringLiquibaseCustomizer springLiquibaseCustomizer(Customizer<Liquibase> customizer) {
 			return (springLiquibase) -> springLiquibase.setCustomizer(customizer);
 		}
 

spring-boot-project/spring-boot-devtools/src/test/java/org/springframework/boot/devtools/restart/MainMethodTests.java

@@ -66,7 +66,7 @@ void nestedMainMethod() throws Exception {
 	}
 
 	@Test // gh-39733
-	void vaiJarLauncher() throws Exception {
+	void viaJarLauncher() throws Exception {
 		FakeJarLauncher.action = (args) -> Valid.main(args);
 		MainMethod method = new TestThread(FakeJarLauncher::main).test();
 		Method expectedMain = Valid.class.getMethod("main", String[].class);

spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/using/devtools.adoc

@@ -243,7 +243,7 @@ If this causes issues, you can diagnose the problem by using the `spring.devtool
 By default, any open project in your IDE is loaded with the "`restart`" classloader, and any regular `.jar` file is loaded with the "`base`" classloader.
 The same is true if you use `mvn spring-boot:run` or `gradle bootRun`: the project containing your `@SpringBootApplication` is loaded with the "`restart`" classloader, and everything else with the "`base`" classloader.
 The classpath is printed on the console when you start the app, which can help to identify any problematic entries.
-Classes used reflectively, especially annotations, can be loaded into the parent (fixed) classloader on startup before the application classes which uses them, and this might lead to them not being detected by Spring in the application.
+Classes used reflectively, especially annotations, can be loaded into the parent (fixed) classloader on startup before the application classes which use them, and this might lead to them not being detected by Spring in the application.
 
 You can instruct Spring Boot to load parts of your project with a different classloader by creating a `META-INF/spring-devtools.properties` file.
 The `spring-devtools.properties` file can contain properties prefixed with `restart.exclude` and `restart.include`.

spring-boot-project/spring-boot-testcontainers/src/dockerTest/java/org/springframework/boot/testcontainers/service/connection/kafka/ApacheKafkaContainerConnectionDetailsFactoryIntegrationTests.java

@@ -41,7 +41,7 @@
 import static org.assertj.core.api.Assertions.assertThat;
 
 /**
- * Tests for {@link ConfluentKafkaContainerConnectionDetailsFactory}.
+ * Tests for {@link ApacheKafkaContainerConnectionDetailsFactory}.
  *
  * @author Moritz Halbritter
  * @author Andy Wilkinson