Skip to content

Commit 29fdcf5

Browse files
committed
Polishing
1 parent 186deb7 commit 29fdcf5

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

framework-docs/modules/ROOT/pages/core/beans/dependencies/factory-collaborators.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ Kotlin::
162162
.[[beans-factory-ctor-arguments-type]]Constructor argument type matching
163163
--
164164
In the preceding scenario, the container can use type matching with simple types if
165-
you explicitly specify the type of the constructor argument by using the `type` attribute,
165+
you explicitly specify the type of the constructor argument via the `type` attribute,
166166
as the following example shows:
167167

168168
[source,xml,indent=0,subs="verbatim,quotes"]

framework-docs/modules/ROOT/pages/core/beans/java/composing-configuration-classes.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ the configuration model, in that references to other beans must be valid Java sy
116116
Fortunately, solving this problem is simple. As
117117
xref:core/beans/java/bean-annotation.adoc#beans-java-dependencies[we already discussed],
118118
a `@Bean` method can have an arbitrary number of parameters that describe the bean
119-
dependencies. Consider the following more real-world scenario with several `@Configuration`
119+
dependencies. Consider the following more realistic scenario with several `@Configuration`
120120
classes, each depending on beans declared in the others:
121121

122122
[tabs]

0 commit comments

Comments
 (0)