[camel] branch main updated: Fix typo optimistick -> optimistic

[or...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new b65e64f5f0c Fix typo optimistick -> optimistic
b65e64f5f0c is described below

commit b65e64f5f0c24d4d4fd64c7b97a0f27bc7023bff
Author: Aurélien Pupier <ap...@redhat.com>
AuthorDate: Fri Apr 8 13:22:11 2022 +0200

    Fix typo optimistick -> optimistic
    
    Signed-off-by: Aurélien Pupier <ap...@redhat.com>
---
 components/camel-sql/src/main/docs/sql-component.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/components/camel-sql/src/main/docs/sql-component.adoc b/components/camel-sql/src/main/docs/sql-component.adoc
index 554a4f4c4a7..96266f293e0 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -642,7 +642,7 @@ multiple Camel applications shared the same database for the aggregation
 repository. If there is a race condition there JDBC driver will throw a
 vendor specific exception which the `JdbcAggregationRepository` can
 react upon. To know which caused exceptions from the JDBC driver is
-regarded as an optimistick locking error we need a mapper to do this.
+regarded as an optimistic locking error we need a mapper to do this.
 Therefore there is a
 `org.apache.camel.processor.aggregate.jdbc.JdbcOptimisticLockingExceptionMapper`
 allows you to implement your custom logic if needed. There is a default
@@ -662,7 +662,7 @@ configured.
 
 You can in addition add FQN classnames, and if any of the caused
 exception (or any nested) equals any of the FQN class names, then its an
-optimistick locking error.
+optimistic locking error.
 
 Here is an example, where we define 2 extra FQN class names from the
 JDBC vendor.