Fix typos

core/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/AutoConfigurationReplacements.java

@@ -81,7 +81,7 @@ public int hashCode() {
 	}
 
 	/**
-	 * Loads the relocations from the classpath. Relactions are stored in files named
+	 * Loads the relocations from the classpath. Relocations are stored in files named
 	 * {@code META-INF/spring/full-qualified-annotation-name.replacements} on the
 	 * classpath. The file is loaded using {@link Properties#load(java.io.InputStream)}
 	 * with each entry containing an auto-configuration class name as the key and the

core/spring-boot-test/src/test/java/org/springframework/boot/test/context/runner/AbstractApplicationContextRunnerTests.java

@@ -296,7 +296,7 @@ void prepareDoesNotRefreshContext() {
 	}
 
 	@Test
-	void getWirhAdditionalContextInterfaceHasCorrectInstanceOf() {
+	void getWithAdditionalContextInterfaceHasCorrectInstanceOf() {
 		getWithAdditionalContextInterface()
 			.run((context) -> assertThat(context).isInstanceOf(AdditionalContextInterface.class));
 	}

documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/testing/test-modules.adoc

@@ -8,7 +8,7 @@ Spring Boot offers several focused, feature-specific `-test` modules:
 |Module | Purpose
 
 |`spring-boot-cache-test`
-|Testing applications that use Spring Framework's cache abstration.
+|Testing applications that use Spring Framework's cache abstraction.
 
 |`spring-boot-data-cassandra-test`
 |Testing applications that use Spring Data Cassandra. Provides the `@DataCassandraTest` test slice.

documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/testing/testcontainers.adoc

@@ -66,7 +66,7 @@ include-code::MyTestConfiguration[]
 == Lifecycle of Managed Containers
 
 If you have used the annotations and extensions provided by Testcontainers, then the lifecycle of container instances is managed entirely by Testcontainers.
-Please refer to the {url-testcontainers-docs}[offical Testcontainers documentation] for the information.
+Please refer to the {url-testcontainers-docs}[official Testcontainers documentation] for the information.
 
 When the containers are managed by Spring as beans, then their lifecycle is managed by Spring:
 

loader/spring-boot-loader/src/test/java/org/springframework/boot/loader/zip/VirtualZipPerformanceTests.java

@@ -43,7 +43,7 @@ class VirtualZipPerformanceTests {
 	Path temp;
 
 	@Test
-	void sequentialReadPerformace() throws IOException {
+	void sequentialReadPerformance() throws IOException {
 		File file = createZipWithLargeEntries();
 		long start = System.nanoTime();
 		try (ZipContent zipContent = ZipContent.open(file.toPath(), "test/")) {

module/spring-boot-health/src/test/java/org/springframework/boot/health/autoconfigure/actuate/endpoint/AvailabilityProbesAutoConfigurationTests.java

@@ -54,7 +54,7 @@ void probesWhenPropertyEnabledAddsBeans() {
 	}
 
 	@Test
-	void probesWhenNoActautorDependencyDoesNotAddBeans() {
+	void probesWhenNoActuatorDependencyDoesNotAddBeans() {
 		this.contextRunner.withClassLoader(new FilteredClassLoader(Endpoint.class.getName()))
 			.run(this::doesNotHaveProbeBeans);
 	}