Fix typos in JDBC & JPA docs

(cherry picked from commit 92cfd0ed05)

src/reference/antora/modules/ROOT/pages/jdbc/inbound-channel-adapter.adoc

@@ -62,7 +62,7 @@ The `value` in each parameter expression can be any valid SpEL expression.
 The `#root` object for the expression evaluation is the constructor argument defined on the `parameterSource` bean.
 It is static for all evaluations (in the preceding example, an empty `String`).
 
-Starting with version 5.0, you ca supply `ExpressionEvaluatingSqlParameterSourceFactory` with `sqlParameterTypes` to specify the target SQL type for the particular parameter.
+Starting with version 5.0, you can supply `ExpressionEvaluatingSqlParameterSourceFactory` with `sqlParameterTypes` to specify the target SQL type for the particular parameter.
 
 The following example provides SQL types for the parameters being used in the query:
 

src/reference/antora/modules/ROOT/pages/jdbc/message-store.adoc

@@ -21,7 +21,7 @@ Before starting to use JDBC message store components, you should provision a tar
 Spring Integration ships with some sample scripts that can be used to initialize a database.
 In the `spring-integration-jdbc` JAR file, you can find scripts in the `org.springframework.integration.jdbc` package.
 It provides an example create and an example drop script for a range of common database platforms.
-A common way to use these scripts is to reference them in a https://docs.spring.io/spring/docs/current/spring-framework-reference/html/jdbc.html#jdbc-intializing-datasource[Spring JDBC data source initializer].
+A common way to use these scripts is to reference them in a https://docs.spring.io/spring-framework/reference/data-access/jdbc/initializing-datasource.html[Spring JDBC data source initializer].
 Note that the scripts are provided as samples and as specifications of the required table and column names.
 You may find that you need to enhance them for production use (for, example, by adding index declarations).
 
@@ -126,7 +126,7 @@ When polling a message channel, you have the option to configure the associated
 
 [IMPORTANT]
 ====
-Keep in mind, though, that if you use a JDBC backed message channel and you plan to poll the channel and consequently the message store transactionally with multiple threads, you should ensure that you use a relational database that supports https://en.wikipedia.org/wiki/Multiversion_concurrency_control[Multiversion Concurrency Control] (MVCC).
+Keep in mind, though, that if you use a JDBC backed message channel, and you plan to poll the channel and consequently the message store transactional with multiple threads, you should ensure that you use a relational database that supports https://en.wikipedia.org/wiki/Multiversion_concurrency_control[Multiversion Concurrency Control] (MVCC).
 Otherwise, locking may be an issue and the performance, when using multiple threads, may not materialize as expected.
 For example, Apache Derby is problematic in that regard.
 

src/reference/antora/modules/ROOT/pages/jdbc/outbound-channel-adapter.adoc

@@ -7,7 +7,7 @@ By default, the message payload and headers are available as input parameters to
 [source,xml]
 ----
 <int-jdbc:outbound-channel-adapter
-    query="insert into foos (id, status, name) values (:headers[id], 0, :payload[something])"
+    query="insert into items (id, status, name) values (:headers[id], 0, :payload[something])"
     data-source="dataSource"
     channel="input"/>
 ----

src/reference/antora/modules/ROOT/pages/jdbc/stored-procedures.adoc

@@ -35,7 +35,7 @@ If you want to execute stored functions instead, the following databases are ful
 =====
 Even though your particular database may not be fully supported, chances are that you can use the stored procedure Spring Integration components quite successfully anyway, provided your RDBMS supports stored procedures or stored functions.
 
-As a matter of fact, some provided integration tests use the https://www.h2database.com/[H2 database].
+As a matter of fact, some provided integration tests use the https://www.h2database.com[H2 database].
 Nevertheless, it is very important to thoroughly test those usage scenarios.
 =====
 
@@ -105,7 +105,7 @@ This means that, by using a default `BeanPropertySqlParameterSourceFactory`, the
 However, if procedure parameters are passed in, this property (by default) evaluates to `false`.
 `ProcedureParameter` lets SpEL Expressions be provided.
 Therefore, it is highly beneficial to have access to the entire `Message`.
-The property is set on the underlying `StoredProcExecutor`.
+The property set on the underlying `StoredProcExecutor`.
 Optional.
 
 [[sp-common-config-subelements]]

src/reference/antora/modules/ROOT/pages/jpa/namespace-support.adoc

@@ -83,7 +83,7 @@ The following example shows how to set an expression-based parameter:
 ----
 
 Value-based Parameters::
-The following example shows how to set an value-based parameter:
+The following example shows how to set a value-based parameter:
 +
 [source,xml]
 ----
@@ -143,7 +143,7 @@ You can also configure this JPA operation to run as a new transaction, as the fo
 ----
 
 In the preceding example, the transactional element of the outbound gateway or adapter specifies the transaction attributes.
-It is optional to define this child element if you have `DirectChannel` as an input channel to the adapter and you want the adapter to execute the operations in the same transaction context as the caller.
+It is optional to define this child element if you have `DirectChannel` as an input channel to the adapter, and you want the adapter to execute the operations in the same transaction context as the caller.
 If, however, you use an `ExecutorChannel`, you must have the `transactional` element, because the invoking client's transaction context is not propagated.
 
 NOTE: Unlike the `transactional` element of the poller, which is defined in Spring Integration's namespace, the `transactional` element for the outbound gateway or adapter is defined in the JPA namespace.

src/reference/antora/modules/ROOT/pages/jpa/outbound-channel-adapter.adoc

@@ -249,7 +249,7 @@ The default value is set to `0`, which means "'no flush'".
 This attribute is geared towards messages with `Iterable` payloads.
 For instance, if `flush-size` is set to `3`, then `entityManager.flush()` is called after every third entity.
 Furthermore, `entityManager.flush()` is called once more after the entire loop.
-If the 'flush-size' attribute is specified with a value greater than '0', you need not configure the `flush` attribute.
+If the 'flush-size' attribute specified with a value greater than '0', you need not configure the `flush` attribute.
 <15> Set this value to 'true' if you want to clear the persistence context immediately after each flush operation.
 The attribute's value is applied only if the `flush` attribute is set to `true` or if the `flush-size` attribute is set to a value greater than `0`.
 <16> If set to `true`, the payload of the message is used as a source for parameters.

src/reference/antora/modules/ROOT/pages/jpa/outbound-gateways.adoc

@@ -317,8 +317,8 @@ All other attributes are disallowed if you use `id-expression`.
 Optional.
 <2> A boolean flag indicating whether the select operation is expected to return a single result or a `List` of results.
 If this flag is set to `true`, a single entity is sent as the payload of the message.
-If multiple entities are returned, an exception is thrown.
-If `false`, the `List` of entities is sent as the payload of the message.
+If multiple entities are returned, an exception thrown.
+If `false`, the `List` of entities sent as the payload of the message.
 It defaults to `false`.
 Optional.
 <3> This non-zero, non-negative integer value tells the adapter not to select more than the specified number of rows on execution of the select operation.