Skip to content

Commit 452257e

Browse files
committed
Revise contribution
See gh-36022
1 parent a7863a0 commit 452257e

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ are set by using the `setVariable()` method in `EvaluationContext` implementatio
66

77
[NOTE]
88
====
9-
Variable names must be begun with a letter (as defined below), an underscore, or a dollar
9+
Variable names must begin with a letter (as defined below), an underscore, or a dollar
1010
sign.
1111
1212
Variable names must be composed of one or more of the following supported types of

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -349,11 +349,11 @@ parameters return the data read from the table.
349349

350350
You can declare `SimpleJdbcCall` in a manner similar to declaring `SimpleJdbcInsert`. You
351351
should instantiate and configure the class in the initialization method of your data-access
352-
layer. Compared to the `StoredProcedure` class, you need not create a subclass
353-
and you need not declare parameters that can be looked up in the database metadata.
354-
The following example of a `SimpleJdbcCall` configuration uses the preceding stored
355-
procedure (the only configuration option, in addition to the `DataSource`, is the name
356-
of the stored procedure):
352+
layer. In contrast to the `StoredProcedure` class, you do not need to create a subclass,
353+
and you do not need to declare parameters that can be looked up in the database metadata.
354+
The following `SimpleJdbcCall` configuration example uses the preceding stored procedure.
355+
The only configuration option (other than the `DataSource`) is the name of the stored
356+
procedure.
357357

358358
[tabs]
359359
======

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ The ahead-of-time cache is a JVM feature introduced in Java 24 via the
77
https://openjdk.org/jeps/483[JEP 483] that can help reduce the startup time and memory
88
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)].
99
Spring Framework supports both CDS and AOT cache, and it is recommended that you use the
10-
later if available in the JVM version you are using (Java 24+).
10+
latter if available in the JVM version you are using (Java 24+).
1111

1212
To use this feature, an AOT cache should be created for the particular classpath of the
1313
application. It is possible to create this cache on the deployed instance, or during a

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -313,7 +313,7 @@ xref:integration/jmx/naming.adoc#jmx-context-mbeanexport[Configuring Annotation-
313313
=== The `cache` Schema
314314

315315
You can use the `cache` elements to enable support for Spring's `@CacheEvict`, `@CachePut`,
316-
and `@Caching` annotations. It is also supports declarative XML-based caching. See
316+
and `@Caching` annotations. The `cache` schema also supports declarative XML-based caching. See
317317
xref:integration/cache/annotations.adoc#cache-annotation-enable[Enabling Caching Annotations] and
318318
xref:integration/cache/declarative-xml.adoc[Declarative XML-based Caching] for details.
319319

0 commit comments

Comments
 (0)