From d62e6e93ba4aeacfae636fa7ba83a715f6784dee Mon Sep 17 00:00:00 2001 From: xxxxxxjun Date: Fri, 27 Mar 2026 01:02:22 +0900 Subject: [PATCH] Fix typo in @Bean Javadoc Signed-off-by: xxxxxxjun --- .../main/java/org/springframework/context/annotation/Bean.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-context/src/main/java/org/springframework/context/annotation/Bean.java b/spring-context/src/main/java/org/springframework/context/annotation/Bean.java index f32df0852928..27f116150b48 100644 --- a/spring-context/src/main/java/org/springframework/context/annotation/Bean.java +++ b/spring-context/src/main/java/org/springframework/context/annotation/Bean.java @@ -204,7 +204,7 @@ * ({@code BPP}) types. Because {@code BPP} objects must be instantiated early in the container * lifecycle, a non-static {@code @Bean} method that returns a {@code BPP} will cause eager * initialization of its declaring {@code @Configuration} class, which can make other beans in the - * {@code @Configuration} class (as well as depencencies of those beans) ineligible for full + * {@code @Configuration} class (as well as dependencies of those beans) ineligible for full * post-processing. To avoid these lifecycle issues, mark {@code BPP}-returning {@code @Bean} * methods as {@code static}. For example: *