Browse Source

Fix typos and grammar in reference manual

Closes gh-36022

Signed-off-by: Tran Ngoc Nhan <ngocnhan.tran1996@gmail.com>
pull/35344/merge
Tran Ngoc Nhan 4 days ago committed by Sam Brannen
parent
commit
a7863a0877
  1. 2
      framework-docs/modules/ROOT/pages/core/aop/ataspectj/pointcuts.adoc
  2. 2
      framework-docs/modules/ROOT/pages/core/expressions/language-ref/variables.adoc
  3. 2
      framework-docs/modules/ROOT/pages/data-access/jdbc/simple.adoc
  4. 2
      framework-docs/modules/ROOT/pages/integration/aot-cache.adoc
  5. 14
      framework-docs/modules/ROOT/pages/integration/appendix.adoc
  6. 2
      framework-docs/modules/ROOT/pages/languages/kotlin/classes-interfaces.adoc

2
framework-docs/modules/ROOT/pages/core/aop/ataspectj/pointcuts.adoc

@ -104,7 +104,7 @@ Note that pointcut definitions are generally matched against any intercepted met
If a pointcut is strictly meant to be public-only, even in a CGLIB proxy scenario with If a pointcut is strictly meant to be public-only, even in a CGLIB proxy scenario with
potential non-public interactions through proxies, it needs to be defined accordingly. potential non-public interactions through proxies, it needs to be defined accordingly.
If your interception needs include method calls or even constructors within the target If your interception needs to include method calls or even constructors within the target
class, consider the use of Spring-driven xref:core/aop/using-aspectj.adoc#aop-aj-ltw[native AspectJ weaving] instead class, consider the use of Spring-driven xref:core/aop/using-aspectj.adoc#aop-aj-ltw[native AspectJ weaving] instead
of Spring's proxy-based AOP framework. This constitutes a different mode of AOP usage of Spring's proxy-based AOP framework. This constitutes a different mode of AOP usage
with different characteristics, so be sure to make yourself familiar with weaving with different characteristics, so be sure to make yourself familiar with weaving

2
framework-docs/modules/ROOT/pages/core/expressions/language-ref/variables.adoc

@ -6,7 +6,7 @@ are set by using the `setVariable()` method in `EvaluationContext` implementatio
[NOTE] [NOTE]
==== ====
Variable names must be begin with a letter (as defined below), an underscore, or a dollar Variable names must be begun with a letter (as defined below), an underscore, or a dollar
sign. sign.
Variable names must be composed of one or more of the following supported types of Variable names must be composed of one or more of the following supported types of

2
framework-docs/modules/ROOT/pages/data-access/jdbc/simple.adoc

@ -350,7 +350,7 @@ parameters return the data read from the table.
You can declare `SimpleJdbcCall` in a manner similar to declaring `SimpleJdbcInsert`. You You can declare `SimpleJdbcCall` in a manner similar to declaring `SimpleJdbcInsert`. You
should instantiate and configure the class in the initialization method of your data-access should instantiate and configure the class in the initialization method of your data-access
layer. Compared to the `StoredProcedure` class, you need not create a subclass layer. Compared to the `StoredProcedure` class, you need not create a subclass
and you need not to declare parameters that can be looked up in the database metadata. and you need not declare parameters that can be looked up in the database metadata.
The following example of a `SimpleJdbcCall` configuration uses the preceding stored The following example of a `SimpleJdbcCall` configuration uses the preceding stored
procedure (the only configuration option, in addition to the `DataSource`, is the name procedure (the only configuration option, in addition to the `DataSource`, is the name
of the stored procedure): of the stored procedure):

2
framework-docs/modules/ROOT/pages/integration/aot-cache.adoc

@ -7,7 +7,7 @@ The ahead-of-time cache is a JVM feature introduced in Java 24 via the
https://openjdk.org/jeps/483[JEP 483] that can help reduce the startup time and memory https://openjdk.org/jeps/483[JEP 483] that can help reduce the startup time and memory
footprint of Java applications. AOT cache is a natural evolution of https://docs.oracle.com/en/java/javase/17/vm/class-data-sharing.html[Class Data Sharing (CDS)]. footprint of Java applications. AOT cache is a natural evolution of https://docs.oracle.com/en/java/javase/17/vm/class-data-sharing.html[Class Data Sharing (CDS)].
Spring Framework supports both CDS and AOT cache, and it is recommended that you use the Spring Framework supports both CDS and AOT cache, and it is recommended that you use the
later if available in the JVM version your are using (Java 24+). later if available in the JVM version you are using (Java 24+).
To use this feature, an AOT cache should be created for the particular classpath of the To use this feature, an AOT cache should be created for the particular classpath of the
application. It is possible to create this cache on the deployed instance, or during a application. It is possible to create this cache on the deployed instance, or during a

14
framework-docs/modules/ROOT/pages/integration/appendix.adoc

@ -172,7 +172,7 @@ different properties with `jee`:
The `<jee:local-slsb/>` element configures a reference to a local EJB Stateless Session Bean. The `<jee:local-slsb/>` element configures a reference to a local EJB Stateless Session Bean.
The following example shows how to configures a reference to a local EJB Stateless Session Bean The following example shows how to configure a reference to a local EJB Stateless Session Bean
without `jee`: without `jee`:
[source,xml,indent=0,subs="verbatim,quotes"] [source,xml,indent=0,subs="verbatim,quotes"]
@ -184,7 +184,7 @@ without `jee`:
</bean> </bean>
---- ----
The following example shows how to configures a reference to a local EJB Stateless Session Bean The following example shows how to configure a reference to a local EJB Stateless Session Bean
with `jee`: with `jee`:
[source,xml,indent=0,subs="verbatim,quotes"] [source,xml,indent=0,subs="verbatim,quotes"]
@ -200,7 +200,7 @@ with `jee`:
The `<jee:local-slsb/>` element configures a reference to a local EJB Stateless Session Bean. The `<jee:local-slsb/>` element configures a reference to a local EJB Stateless Session Bean.
The following example shows how to configures a reference to a local EJB Stateless Session Bean The following example shows how to configure a reference to a local EJB Stateless Session Bean
and a number of properties without `jee`: and a number of properties without `jee`:
[source,xml,indent=0,subs="verbatim,quotes"] [source,xml,indent=0,subs="verbatim,quotes"]
@ -215,7 +215,7 @@ and a number of properties without `jee`:
</bean> </bean>
---- ----
The following example shows how to configures a reference to a local EJB Stateless Session Bean The following example shows how to configure a reference to a local EJB Stateless Session Bean
and a number of properties with `jee`: and a number of properties with `jee`:
[source,xml,indent=0,subs="verbatim,quotes"] [source,xml,indent=0,subs="verbatim,quotes"]
@ -234,7 +234,7 @@ and a number of properties with `jee`:
The `<jee:remote-slsb/>` element configures a reference to a `remote` EJB Stateless Session Bean. The `<jee:remote-slsb/>` element configures a reference to a `remote` EJB Stateless Session Bean.
The following example shows how to configures a reference to a remote EJB Stateless Session Bean The following example shows how to configure a reference to a remote EJB Stateless Session Bean
without `jee`: without `jee`:
[source,xml,indent=0,subs="verbatim,quotes"] [source,xml,indent=0,subs="verbatim,quotes"]
@ -251,7 +251,7 @@ without `jee`:
</bean> </bean>
---- ----
The following example shows how to configures a reference to a remote EJB Stateless Session Bean The following example shows how to configure a reference to a remote EJB Stateless Session Bean
with `jee`: with `jee`:
[source,xml,indent=0,subs="verbatim,quotes"] [source,xml,indent=0,subs="verbatim,quotes"]
@ -313,7 +313,7 @@ xref:integration/jmx/naming.adoc#jmx-context-mbeanexport[Configuring Annotation-
=== The `cache` Schema === The `cache` Schema
You can use the `cache` elements to enable support for Spring's `@CacheEvict`, `@CachePut`, You can use the `cache` elements to enable support for Spring's `@CacheEvict`, `@CachePut`,
and `@Caching` annotations. It it also supports declarative XML-based caching. See and `@Caching` annotations. It is also supports declarative XML-based caching. See
xref:integration/cache/annotations.adoc#cache-annotation-enable[Enabling Caching Annotations] and xref:integration/cache/annotations.adoc#cache-annotation-enable[Enabling Caching Annotations] and
xref:integration/cache/declarative-xml.adoc[Declarative XML-based Caching] for details. xref:integration/cache/declarative-xml.adoc[Declarative XML-based Caching] for details.

2
framework-docs/modules/ROOT/pages/languages/kotlin/classes-interfaces.adoc

@ -13,4 +13,4 @@ running the Kotlin compiler with its `-java-parameters` flag for standard Java p
You can declare configuration classes as You can declare configuration classes as
{kotlin-docs}/nested-classes.html[top level or nested but not inner], {kotlin-docs}/nested-classes.html[top level or nested but not inner],
since the later requires a reference to the outer class. since the latter requires a reference to the outer class.

Loading…
Cancel
Save