This is an automated email from the ASF dual-hosted git repository.
davsclaus 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 47161bd340c Fix typos in 4.x Migration guides (#13229)
47161bd340c is described below
commit 47161bd340cb83386891bbee088e39c28d05cf19
Author: Aurélien Pupier <apup...@redhat.com>
AuthorDate: Wed Feb 21 09:36:02 2024 +0100
Fix typos in 4.x Migration guides (#13229)
Signed-off-by: Aurélien Pupier <apup...@redhat.com>
---
docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc | 6 +++---
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_4.adoc | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
index 8ef7de53067..90c0612c8a4 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
@@ -452,14 +452,14 @@ from("optaplanner:myProblemName")
.to("...")
----
-You can pass the Optaplanner SolverManager in 2 ways:
+You can pass the OptaPlanner SolverManager in 2 ways:
- as #parameter
- as header
When running `camel-optaplanner` on Spring Boot or Quarkus, it is preferable
to use the Spring Boot or Quarkus way of creating the SolverManager.
-It is possible to migrate legacy Camel Optaplanner Routes, by putting the XML
config file, as show in the code below. Camel Optaplanner will handle creating
the SolverManager for those legacy Routes:
+It is possible to migrate legacy Camel OptaPlanner Routes, by putting the XML
config file, as show in the code below. Camel OptaPlanner will handle creating
the SolverManager for those legacy Routes:
[source,java]
----
@@ -528,7 +528,7 @@ If the route or consumer is suspended then http status 503
is now returned inste
=== camel-twitter
-The component was updated to use Twitter4j version 4.1.2, which
https://twitter4j.org/2022/10/21/264[has moved the packages] used by a few of
its classes. If accessing certain twitter-related data, such as the Twit
status, you need to update the packages used from `twitter4j.Status` to
`twitter4j.v1.Status`.
+The component was updated to use Twitter4j version 4.1.2, which
https://twitter4j.org/2022/10/21/264[has moved the packages] used by a few of
its classes. If accessing certain twitter-related data, such as the Tweet
status, you need to update the packages used from `twitter4j.Status` to
`twitter4j.v1.Status`.
== Upgrading Camel 4.0.1 to 4.0.2
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
index c14c7e5f5bc..f0f37c49a07 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_3.adoc
@@ -81,7 +81,7 @@ from("seda:c")
The scheduled consumers has been improved to mark the consumer as _ready_
sooner, when possible. Previously a consumer,
would mark as ready after the first poll was completed. For example, a FTP
consumer downloading a big file on first poll,
-could take soo long time, that the readiness check would timeout and fail
during startup of your Camel application.
+could take so long time, that the readiness check would timeout and fail
during startup of your Camel application.
The following components is now marking the consumer as ready sooner:
@@ -152,7 +152,7 @@ the behavior described in the documentation.
=== camel-yaml-dsl
-Using kebab-case in general has been deprecated, and you will se a WARN logs.
Please migrate to camelCase.
+Using kebab-case in general has been deprecated, and you will see a WARN logs.
Please migrate to camelCase.
The language for exchange property now only supports camelCase style, i.e.
`exchange-property` is now `exchangeProperty`.
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_4.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_4.adoc
index b11b5545d81..8c2abc95360 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_4.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_4.adoc
@@ -163,7 +163,7 @@ With the SHARED_KEY_CREDENTIAL mode the user could
explicitly set the sharedKey
With the AZURE_IDENTITY mode the user will be able to use the Default Azure
Credentials Chain.
With the AZURE_SAS mode the user could explicitly set the sasSignature or
sasCredential parameter.
With the CLIENT_SECRET mode the user could explicitly set clientId,
clientSecret and tenantId or specify a ClientSecretCredential instance.
-With the SERVICE_CLIENT_INSTANCE the user could explicity set a serviceClient
parameter by passing a DataLakeServiceClient instance.
+With the SERVICE_CLIENT_INSTANCE the user could explicitly set a serviceClient
parameter by passing a DataLakeServiceClient instance.
This is part of the effort explained in CAMEL-18590.
=== camel-azure-storage-queue
