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 dcb17ac19f96 Fix misspellings in the user manual (#29648)
dcb17ac19f96 is described below
commit dcb17ac19f96038a83dc848e4e2b4ee55d8e2410
Author: dhairya05 <[email protected]>
AuthorDate: Thu Nov 12 02:18:23 2026 +0530
Fix misspellings in the user manual (#29648)
Co-authored-by: Guillaume Nodet - AI Bot <[email protected]>
---
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc | 2 +-
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_4.adoc | 2 +-
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_5.adoc | 2 +-
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_6.adoc | 2 +-
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc | 4 ++--
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_9.adoc | 10 +++++-----
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc | 2 +-
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_6.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/consumertemplate.adoc | 2 +-
.../modules/ROOT/pages/improving-the-documentation.adoc | 2 +-
.../modules/ROOT/pages/property-placeholder-functions.adoc | 2 +-
docs/user-manual/modules/ROOT/pages/release-guide.adoc | 4 ++--
docs/user-manual/modules/ROOT/pages/rest-dsl-binding.adoc | 2 +-
13 files changed, 19 insertions(+), 19 deletions(-)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
index 49f38122482f..61993a9a423a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
@@ -96,7 +96,7 @@ Both of the options are false by default. So, you'll need to
set both to true if
=== camel-huawei
-All Huawei Cloud components use AK/SK as security keys to authenticate against
the hauwei cloud backend services. Initally AK was mapped to authenticationKey
in the endpoint class. To be in-line with Huawei Cloud's naming conventions, we
have renamed this option from `authenticationKey` to `accessKey` for all
components. This is a breaking change for users who are already using huawei
cloud components until version 3.11.x.
+All Huawei Cloud components use AK/SK as security keys to authenticate against
the huawei cloud backend services. Initially AK was mapped to authenticationKey
in the endpoint class. To be in-line with Huawei Cloud's naming conventions, we
have renamed this option from `authenticationKey` to `accessKey` for all
components. This is a breaking change for users who are already using huawei
cloud components until version 3.11.x.
=== camel-spring-cloud-*-starter
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_4.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_4.adoc
index d26ef3f31fbe..ddd7b54d9b18 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_4.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_4.adoc
@@ -100,7 +100,7 @@ This actuator was becoming problematic to maintain during
Spring Boot upgrades d
`HttpRegistryProvider` is added and used in `DefaultHttpRegistry` instead of
`CamelServlet`.
These changes had effects on camel-atmosphere-websocket and camel-servlet and
also camel-resteasy.
-Users of these components where they would have custom implemetations on
`DefaultHttpRegistry` and using `CamelServlet` class should take this change
into account.
+Users of these components where they would have custom implementations on
`DefaultHttpRegistry` and using `CamelServlet` class should take this change
into account.
=== camel-sql
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_5.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_5.adoc
index c3e16e9b958c..225ea0b5a935 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_5.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_5.adoc
@@ -29,7 +29,7 @@ Load-balancing policy has changed. There are no existing load
balancing policies
To customize load balancing policy, please use the parameter
`loadBalancingPolicyClass` and provide own implementation
of load balancing policy.
-Session impelentation class has changed from
`com.datastax.driver.core.Session` to
+Session implementation class has changed from
`com.datastax.driver.core.Session` to
`com.datastax.oss.driver.api.core.CqlSession` (see
https://docs.datastax.com/en/developer/java-driver/4.3/upgrade_guide/#session[upgrade
guide]).
This could have direct impact on the type of parameter `beanRef` if you are
using `Provided Session reference`.
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_6.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_6.adoc
index 142a3d6a869f..f8dc7a3a91f9 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_6.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_6.adoc
@@ -65,7 +65,7 @@ The components affected are:
=== Languages
-All the out of the box supported languages (simple, bean, groovy, jsonpath,
xpath etc.) have been optmized to be _singleton_
+All the out of the box supported languages (simple, bean, groovy, jsonpath,
xpath etc.) have been optimized to be _singleton_
which improves performance for concurrent processing that uses those languages
that would be resolved on each use.
Now the languages are resolved once during startup or first usage.
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
index c9884b255546..0f245c17bb76 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
@@ -43,7 +43,7 @@ The `onCompletion` EIP has been fixed. It could trigger
multiple completions for
=== Transactions and Multicast, Splitter, or Recipient List EIPs
-When using `transacted` in Camel routes with Multicast, Splitter, or Recipient
List EIPs, the exection strackframe
+When using `transacted` in Camel routes with Multicast, Splitter, or Recipient
List EIPs, the execution stackframe
could grown deep and this could cause a stack overflow exception. This has
been fixed by refactoring the EIP into a special
transacted mode and the existing reactive mode.
@@ -134,7 +134,7 @@ As consequence of the refactor:
The remote and embedded endpoints provide support the same capabilities, as
example queries were only possible on a remote cache and now they are supported
on both remote and local/embedded caches.
The configuration options for the endpoint are now specific to the context
which remove the possibility to mix unrelated properties.
-Some classes have been relocated (such as indempotent and aggregation
repositories) have been moved from
`org.apache.camel.component.infinispan.processor.*` to
`org.apache.camel.component.infinispan.embedded` or
`org.apache.camel.component.infinispan.remote`:
+Some classes have been relocated (such as idempotent and aggregation
repositories) have been moved from
`org.apache.camel.component.infinispan.processor.*` to
`org.apache.camel.component.infinispan.embedded` or
`org.apache.camel.component.infinispan.remote`:
-
`org.apache.camel.component.infinispan.embedded.InfinispanEmbeddedAggregationRepository`
-
`org.apache.camel.component.infinispan.embedded.InfinispanEmbeddedIdempotentRepository`
-
`org.apache.camel.component.infinispan.remote.InfinispanRemoteAggregationRepository`
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_9.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_9.adoc
index 72b03ad21991..c81a519a0374 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_9.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_9.adoc
@@ -22,12 +22,12 @@ when the consumer is done with the exchange.
The default implementations in `DefaultConsumer` has adapted this API and 3rd
party components can continue as is, by using
the older APIs. For these 3rd party components to support recycling exchanges,
then they must be updated to use this new API.
-A new `org.apache.camel.spi.ResourceLoader` has been introduced as part of
https://issues.apache.org/jira/browse/CAMEL-16285[CAMEL-16285] which provide a
way to support additional schemas to resolve resources. As a consequece:
+A new `org.apache.camel.spi.ResourceLoader` has been introduced as part of
https://issues.apache.org/jira/browse/CAMEL-16285[CAMEL-16285] which provide a
way to support additional schemas to resolve resources. As a consequence:
-- `org.apache.camel.support.ResourceHelper` has been updated to use such
mechanism instead fo the old one.
+- `org.apache.camel.support.ResourceHelper` has been updated to use such
mechanism instead of the old one.
- it is not more possible to provide support for additional schemas using the
URL protocol handler mechanism but instead, custom schemas can be added by
implementing `org.apache.camel.spi.ResourceResolver` and either bind an
instance to the Camel Registry (using `resource-loader-` as a prefix) or using
the Service Factory mechanism (under the path
`META-INF/services/org/apache/camel/resource-resolver/`)
-As example, assuming you want to provide a support for the schema `foo`, then
you either have to binbd your instance to the Camel Registry with
`resource-loader-foo` as a key, or create a factory finder file with path
`META-INF/services/org/apache/camel/resource-resolver/foo`
+As example, assuming you want to provide a support for the schema `foo`, then
you either have to bind your instance to the Camel Registry with
`resource-loader-foo` as a key, or create a factory finder file with path
`META-INF/services/org/apache/camel/resource-resolver/foo`
The method for retrieving a resource URL provided by the
`org.apache.camel.support.ResourceHelper` class, i.e.
`resolveMandatoryResourceAsUrl` ad ` resolveResourceAsUr` have been amended to
accept a `CamelContext` instance instead of a `ClassResolver`.
=== Exchange properties
@@ -155,8 +155,8 @@ The camel-jclouds feature for Camel on Karaf has been
removed.
=== camel-kafka
-The camel-kafka consumer has been improved to be more roboust and have more
confirations how to deal with exceptions while polling from Kafka Brokers.
-In case of any exception thrown, then previously the consumer will re-connect
and therefore try again. This leads to Kafka broker would reasign the partions,
+The camel-kafka consumer has been improved to be more robust and have more
configurations how to deal with exceptions while polling from Kafka Brokers.
+In case of any exception thrown, then previously the consumer will re-connect
and therefore try again. This leads to Kafka broker would reassign the
partitions,
but it may assign back the same consumer again, or another standby consumer.
The new behavior is to only retry certain kind of exceptions which Kafka has
marked as retryable. Any other exceptions is now
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
index 86b2cb080fe0..5e553c1416d4 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
@@ -341,7 +341,7 @@ You can find more information on CAMEL-21680.
=== camel-file
The `camel-file` consumer has been optimized when filtering file names using
name matching only,
-to avoid creating an `GenericFile` object that represent the file. This is
unnessasary if the file
+to avoid creating an `GenericFile` object that represent the file. This is
unnecessary if the file
is to be excluded due the filtering.
This optimization has changed APIs in the `camel-file` component to let
methods that accept
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_6.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_6.adoc
index 788f999065a8..7511a30feea3 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_6.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_6.adoc
@@ -129,7 +129,7 @@ instead of `org.apache.camel.Consumer`.
=== camel-platform-http-vertx
-The id used for multipart file upload attachments on `AttachmentMessage` has
changed from being the name of the uploaded file, to the value specifed on the
`name` field of the `Content-Disposition` header sent in the request body.
+The id used for multipart file upload attachments on `AttachmentMessage` has
changed from being the name of the uploaded file, to the value specified on the
`name` field of the `Content-Disposition` header sent in the request body.
=== camel-google-sheets
diff --git a/docs/user-manual/modules/ROOT/pages/consumertemplate.adoc
b/docs/user-manual/modules/ROOT/pages/consumertemplate.adoc
index 57334d6e925a..ec75a8ff55d3 100644
--- a/docs/user-manual/modules/ROOT/pages/consumertemplate.adoc
+++ b/docs/user-manual/modules/ROOT/pages/consumertemplate.adoc
@@ -15,7 +15,7 @@ easily as shown:
----
ConsumerTemplate template = exchange.getContext().createConsumerTemplate();
-// recieve from default endpoint
+// receive from default endpoint
Object body = template.receiveBody();
// receive from a specific queue
diff --git
a/docs/user-manual/modules/ROOT/pages/improving-the-documentation.adoc
b/docs/user-manual/modules/ROOT/pages/improving-the-documentation.adoc
index 7e7d2f516cda..116a84ee47a0 100644
--- a/docs/user-manual/modules/ROOT/pages/improving-the-documentation.adoc
+++ b/docs/user-manual/modules/ROOT/pages/improving-the-documentation.adoc
@@ -198,7 +198,7 @@ For a general explanation of Antora xref syntax see
https://docs.antora.org/anto
Due to the logical structure of the Camel documentation, xrefs will have a
very limited choice of structure.
IMPORTANT: A bit of confusion is possible here between Antora components and
Camel components.
-Generally an Antora component corresponds more or less to a Camel subproject,
and never to a camel commponent.
+Generally an Antora component corresponds more or less to a Camel subproject,
and never to a camel component.
All the camel components are documented in an Antora component named
`components`.
In this section the word `component` means an Antora component.
diff --git
a/docs/user-manual/modules/ROOT/pages/property-placeholder-functions.adoc
b/docs/user-manual/modules/ROOT/pages/property-placeholder-functions.adoc
index d34abd37c256..ad64bf34752a 100644
--- a/docs/user-manual/modules/ROOT/pages/property-placeholder-functions.adoc
+++ b/docs/user-manual/modules/ROOT/pages/property-placeholder-functions.adoc
@@ -632,7 +632,7 @@ YAML::
=== Using configmap or secrets in local-mode
-During development, you may want to run in _local mode_ where you do not need
acces to a Kubernetes cluster, to lookup the configmap.
+During development, you may want to run in _local mode_ where you do not need
access to a Kubernetes cluster, to lookup the configmap.
In the local mode, then Camel will lookup the configmap _keys_ from local
properties, eg:
For example the example above with the Postgres kamelet, that was configured
using a secret:
diff --git a/docs/user-manual/modules/ROOT/pages/release-guide.adoc
b/docs/user-manual/modules/ROOT/pages/release-guide.adoc
index 1b9e554fd5e8..65d1837c6d6a 100644
--- a/docs/user-manual/modules/ROOT/pages/release-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/release-guide.adoc
@@ -3,7 +3,7 @@
This guide covers how to create and announce a Camel release. Instructions on
updating the website to include the new documentation version are
xref:release-guide-website.adoc[here].
[[ReleaseGuide-Prequisites]]
-== Prequisites
+== Prerequisites
To prepare or perform a release, you *must be* at least an Apache Camel
committer.
@@ -57,7 +57,7 @@ Check that all the keys are listed. Just check that the
latest entry you've adde
=== Sync GPG keys
-Everytime there is a change in the source GPG keys on the main project you
need to synchronize with the dist Camel project, in order to correctly provide
the KEYS file to the expected location. You need to use `svn` tool and
authenticate with your Apache credentials. Once it's done you can proceed like
the following:
+Every time there is a change in the source GPG keys on the main project you
need to synchronize with the dist Camel project, in order to correctly provide
the KEYS file to the expected location. You need to use `svn` tool and
authenticate with your Apache credentials. Once it's done you can proceed like
the following:
[source,bash]
----
diff --git a/docs/user-manual/modules/ROOT/pages/rest-dsl-binding.adoc
b/docs/user-manual/modules/ROOT/pages/rest-dsl-binding.adoc
index f797eb9c6211..79ae86890503 100644
--- a/docs/user-manual/modules/ROOT/pages/rest-dsl-binding.adoc
+++ b/docs/user-manual/modules/ROOT/pages/rest-dsl-binding.adoc
@@ -388,7 +388,7 @@ The Rest DSL supports the following options:
| *xmlDataFormat*|| String| Sets a custom XML data format to be used.
Important: This option is only for setting a custom name of the data format,
not to refer to an existing data format instance.
|===
-For example, to configure the requst buffer on the jetty component on port
9091, then we can do as follows:
+For example, to configure the request buffer on the jetty component on port
9091, then we can do as follows:
[tabs]
====
