From fe8c70dddbeded57b4fdcdad3d552e6be90e67c1 Mon Sep 17 00:00:00 2001 From: Brenden Ehlers Date: Thu, 26 Dec 2024 12:47:13 -0700 Subject: [PATCH] Fix grammatical structure in "Basic Concepts" See gh-34165 --- .../modules/ROOT/pages/core/beans/java/basic-concepts.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/framework-docs/modules/ROOT/pages/core/beans/java/basic-concepts.adoc b/framework-docs/modules/ROOT/pages/core/beans/java/basic-concepts.adoc index beb9764a0f0..2b39ec6e55a 100644 --- a/framework-docs/modules/ROOT/pages/core/beans/java/basic-concepts.adoc +++ b/framework-docs/modules/ROOT/pages/core/beans/java/basic-concepts.adoc @@ -64,7 +64,7 @@ This prevents the same `@Bean` method from accidentally being invoked through a Java method call, which helps to reduce subtle bugs that can be hard to track down. When `@Bean` methods are declared within classes that are not annotated with -`@Configuration` - or when `@Configuration(proxyBeanMethods=false)` is declared -, +`@Configuration`—or when `@Configuration(proxyBeanMethods=false)` is declared— they are referred to as being processed in a "lite" mode. In such scenarios, `@Bean` methods are effectively a general-purpose factory method mechanism without special runtime processing (that is, without generating a CGLIB subclass for it).