Merge pull request #11073 from dreis2211:fix-duplicate-words

* pr/11073:
  Remove duplicate words

spring-boot-project/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/endpoint/Sanitizer.java

@@ -21,8 +21,8 @@ import java.util.regex.Pattern;
 import org.springframework.util.Assert;
 
 /**
- * Strategy that be be used by endpoint implementations to sanitize potentially sensitive
- * keys.
+ * Strategy that should be used by endpoint implementations to sanitize potentially
+ * sensitive keys.
  *
  * @author Christian Dupuis
  * @author Toshiaki Maki

spring-boot-project/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/endpoint/annotation/EndpointExtension.java

@@ -30,7 +30,7 @@ import org.springframework.core.annotation.AliasFor;
  * Meta-annotation used to indicate that an annotation provides extension support for an
  * endpoint. Extensions allow additional technology specific {@link Operation operations}
  * to be added to an existing endpoint. For example, a web extension may offer variations
- * of a read operation operation to support filtering based on a query parameter.
+ * of a read operation to support filtering based on a query parameter.
  * <p>
  * Extension annotations must provide an {@link EndpointFilter} to restrict when the
  * extension applies. The {@code endpoint} attribute is usually re-declared using

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

@@ -5524,7 +5524,7 @@ Spring Boot offers several conveniences for working with the Quartz scheduler, i
 the `spring-boot-starter-quartz` '`Starter`'. If Quartz is available, a `Scheduler` is
 auto-configured (via the `SchedulerFactoryBean` abstraction).
 
-Beans of the following types are automatically picked up and associated with the the
+Beans of the following types are automatically picked up and associated with the
 `Scheduler`:
 
 * `JobDetail`: defines a particular Job. `JobDetail` instances can be built with the
@@ -6683,7 +6683,7 @@ If you <<using-boot-structuring-your-code, structure your code>> in a sensible w
 the configuration of your tests.
 
 It then becomes important not to litter the application's main class with configuration
-settings that are are specific to a particular area of its functionality.
+settings that are specific to a particular area of its functionality.
 
 Assume that you are using Spring Batch and you rely on the auto-configuration for it.
 Your could define your `@SpringBootApplication` as follows:

spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/server/AbstractConfigurableWebServerFactory.java

@@ -72,7 +72,7 @@ public class AbstractConfigurableWebServerFactory
 	}
 
 	/**
-	 * The port that the web server server listens on.
+	 * The port that the web server listens on.
 	 * @return the port
 	 */
 	public int getPort() {

spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/servlet/context/ServletWebServerInitializedEvent.java

@@ -45,7 +45,7 @@ public class ServletWebServerInitializedEvent extends WebServerInitializedEvent
 	/**
 	 * Access the application context that the server was created in. Sometimes it is
 	 * prudent to check that this matches expectations (like being equal to the current
-	 * context) before acting on the server server itself.
+	 * context) before acting on the server itself.
 	 * @return the applicationContext that the server was created from
 	 */
 	@Override