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 844aaa246082 Fix misspellings in the documentation of 13 components
(#29642)
844aaa246082 is described below
commit 844aaa2460829244a76968acc8f0beef427137f8
Author: dhairya05 <[email protected]>
AuthorDate: Thu Nov 12 12:03:22 2026 +0530
Fix misspellings in the documentation of 13 components (#29642)
* camel-bindy: fix four misspellings in the dataformat documentation
process/unavailable in CsvRecord.allowEmptyStream and formatter in
KeyValuePairField.pattern come from the annotation Javadoc, which
UpdateReadmeMojo renders into the annotation options tables, so the
Javadoc and both rendered copies are corrected together. optionaly
is prose outside the generated blocks.
* camel-coap: fix Renegotation and Maxium in the component documentation
* camel-crypto: fix cyphertext and suppling in the dataformat documentation
* camel-disruptor: fix bouded in the disruptor-vm documentation
* camel-google: fix calender in the summary page
* camel-grok: fix plugable in the dataformat documentation
* camel-hazelcast: fix availble in the pncounter documentation
* camel-jactl: fix commends in the language documentation
The list item describes // and /* */ comments, not commands.
* camel-kafka: fix aggregrate in the component documentation
* camel-paho: fix build-in in the component documentation
* camel-paho-mqtt5: fix build-in in the component documentation
* camel-xchange: fix commited in the component documentation
* camel-zip-deflater: fix comressed in the gzipDeflater documentation
* Update components/camel-crypto/src/main/docs/crypto-dataformat.adoc
Co-authored-by: Guillaume Nodet - AI Bot <[email protected]>
* camel-crypto, camel-hazelcast: re-sync the catalog copies and fix "does
replicates"
The decyption fix was applied to the component page only, leaving the
camel-catalog copy out of sync, which the uncommitted-changes check would
have caught. Both copies are now byte-identical to their source page.
---------
Co-authored-by: Guillaume Nodet - AI Bot <[email protected]>
---
.../resources/org/apache/camel/catalog/docs/bindy-dataformat.adoc | 6 +++---
.../resources/org/apache/camel/catalog/docs/coap-component.adoc | 4 ++--
.../resources/org/apache/camel/catalog/docs/crypto-dataformat.adoc | 6 +++---
.../org/apache/camel/catalog/docs/disruptor-vm-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/grok-dataformat.adoc | 2 +-
.../org/apache/camel/catalog/docs/gzipDeflater-dataformat.adoc | 2 +-
.../apache/camel/catalog/docs/hazelcast-pncounter-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/jactl-language.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/kafka-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/paho-component.adoc | 2 +-
.../org/apache/camel/catalog/docs/paho-mqtt5-component.adoc | 2 +-
.../resources/org/apache/camel/catalog/docs/xchange-component.adoc | 2 +-
components/camel-bindy/src/main/docs/bindy-dataformat.adoc | 6 +++---
.../org/apache/camel/dataformat/bindy/annotation/CsvRecord.java | 2 +-
.../apache/camel/dataformat/bindy/annotation/KeyValuePairField.java | 2 +-
components/camel-coap/src/main/docs/coap-component.adoc | 4 ++--
components/camel-crypto/src/main/docs/crypto-dataformat.adoc | 6 +++---
.../camel-disruptor/src/main/docs/disruptor-vm-component.adoc | 2 +-
components/camel-google/src/main/docs/google-summary.adoc | 2 +-
components/camel-grok/src/main/docs/grok-dataformat.adoc | 2 +-
.../src/main/docs/hazelcast-pncounter-component.adoc | 2 +-
components/camel-jactl/src/main/docs/jactl-language.adoc | 2 +-
components/camel-kafka/src/main/docs/kafka-component.adoc | 2 +-
components/camel-paho-mqtt5/src/main/docs/paho-mqtt5-component.adoc | 2 +-
components/camel-paho/src/main/docs/paho-component.adoc | 2 +-
components/camel-xchange/src/main/docs/xchange-component.adoc | 2 +-
.../camel-zip-deflater/src/main/docs/gzipDeflater-dataformat.adoc | 2 +-
27 files changed, 37 insertions(+), 37 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bindy-dataformat.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bindy-dataformat.adoc
index b3ca81ea0030..76bfc268bdcf 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bindy-dataformat.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/bindy-dataformat.adoc
@@ -105,7 +105,7 @@ character supported is tab (\t). No other whitespace
characters (spaces) are not
interpreted as a regular expression. If you want to use a sign which has a
special meaning in regular
expressions, e.g., the '\|' sign, then you have to mask it, like '\|'
-| allowEmptyStream | boolean | | false | The allowEmptyStream parameter will
allow to prcoess the unavaiable stream for CSV file.
+| allowEmptyStream | boolean | | false | The allowEmptyStream parameter will
allow to process the unavailable stream for CSV file.
| autospanLine | boolean | | false a| Last record spans rest of line
(optional) - if enabled then the last column is auto spanned to end of line, for
example if it is a comment, etc this allows the line to contain all
characters, also the delimiter char.
@@ -1313,7 +1313,7 @@ Header classes
The KeyValuePairField annotation defines the property of a key value
pair field. Each KeyValuePairField is identified by a tag (= key) and
-its value associated, a type (string, int, date, ...), optionaly a
+its value associated, a type (string, int, date, ...), optionally a
pattern and if the field is required.
[width="100%",cols="15%s,15%,60%",options="header",]
@@ -1342,7 +1342,7 @@ to @Message.continueParseOnFailure.
| name | String | | | name of the field (optional)
-| pattern | String | | | pattern that the formater will use to transform the
data (optional)
+| pattern | String | | | pattern that the formatter will use to transform
the data (optional)
| position | int | | 0 a| Position of the field in the message generated -
must be used when the position of the key/tag in the FIX message
must be different
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/coap-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/coap-component.adoc
index 1362c3f1beee..947b3ed06e44 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/coap-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/coap-component.adoc
@@ -464,7 +464,7 @@ DTLS.RETRANSMISSION_TIMEOUT_SCALE=2.0
DTLS.ROLE=BOTH
# Use minimal version of RFC5746 to indicate secure renegotiation on
# initial handshake.
-# Renegotation handshakes are always rejected by Californium.
+# Renegotiation handshakes are always rejected by Californium.
# [NONE, WANTED, NEEDED].
# Default: WANTED
DTLS.SECURE_RENEGOTIATION_MODE=WANTED
@@ -567,7 +567,7 @@ TCP.WORKER_THREADS=0
# Maximum number of pending outgoing messages.
# Default: 2147483647
UDP.CONNECTOR_OUT_CAPACITY=2147483647
-# Maxium size of UDP datagram.
+# Maximum size of UDP datagram.
# Default: 2048
UDP.DATAGRAM_SIZE=2048
# Number of UDP receiver threads.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/crypto-dataformat.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/crypto-dataformat.adoc
index 76ca4feeb9ce..49fcde59a1b6 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/crypto-dataformat.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/crypto-dataformat.adoc
@@ -13,9 +13,9 @@ The Crypto Data Format integrates the Java
Cryptographic Extension into Camel, allowing simple and flexible
encryption and decryption of messages using Camel's familiar marshall
and unmarshal formatting mechanism. It assumes marshaling to mean
-encryption to cyphertext and unmarshalling to mean decryption back to
+encryption to ciphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
-(shared-key) encryption and decyption.
+(shared-key) encryption and decryption.
== CryptoDataFormat Options
@@ -140,7 +140,7 @@ from("direct:init-vector")
.to("mock:unencrypted");
----
-or with spring, suppling a reference to a byte[]
+or with spring, supplying a reference to a byte[]
[source,xml]
----
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-vm-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-vm-component.adoc
index a0f0e341f3ee..b9a7036d30b1 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-vm-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/disruptor-vm-component.adoc
@@ -39,7 +39,7 @@ behavior and options of the SEDA component as much as
possible.
The main differences between them are the following:
* The buffer used is always bounded in size (default 1024 exchanges).
-* As the buffer is always bouded, the default behaviour for the
+* As the buffer is always bounded, the default behaviour for the
Disruptor is to block while the buffer is full instead of throwing an
exception. This default behavior may be configured on the component
(see options).
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/grok-dataformat.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/grok-dataformat.adoc
index cdf2d3441c01..e947cd3516f1 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/grok-dataformat.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/grok-dataformat.adoc
@@ -129,7 +129,7 @@ All
https://github.com/thekrakken/java-grok/tree/master/src/main/resources/patte
=== Custom patterns
-Camel Grok DataFormat supports plugable patterns, which are auto loaded from
Camel Registry.
+Camel Grok DataFormat supports pluggable patterns, which are auto loaded from
Camel Registry.
You can register patterns with Java DSL and Spring DSL:
._Java-only: registering a custom Grok pattern_
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/gzipDeflater-dataformat.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/gzipDeflater-dataformat.adoc
index 741a2bf4c8df..eb598942e8ae 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/gzipDeflater-dataformat.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/gzipDeflater-dataformat.adoc
@@ -16,7 +16,7 @@ headers are provided. This format is produced by popular
`gzip`/`gunzip`
tool. Messages marshalled using GZip compression can be unmarshalled
using GZip decompression just prior to being consumed at the endpoint.
The compression capability is quite useful when you deal with large XML
-and text-based payloads or when you read messages previously comressed
+and text-based payloads or when you read messages previously compressed
using `gzip` tool.
[NOTE]
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hazelcast-pncounter-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hazelcast-pncounter-component.adoc
index 36c9aee9ca69..e136493a4f4a 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hazelcast-pncounter-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hazelcast-pncounter-component.adoc
@@ -17,7 +17,7 @@
The http://www.hazelcast.com/[Hazelcast] PN Counter component is one of Camel
Hazelcast Components which allows you to access a Hazelcast PN Counter (CRDT
counter).
A PN Counter is a Conflict-free Replicated Data Type (CRDT) that provides a
distributed counter with eventual consistency guarantees.
-This component is not a direct replacement for the hazelcast-atomicvalue
component that is availble in Camel 2.7 -> 4.19, but it does replicates most of
the functionality (get / increment / decrement / getAndAdd / destroy) apart
from the compare method.
+This component is not a direct replacement for the hazelcast-atomicvalue
component that is available in Camel 2.7 -> 4.19, but it does replicate most of
the functionality (get / increment / decrement / getAndAdd / destroy) apart
from the compare method.
// component options: START
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jactl-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jactl-language.adoc
index 6e25278ea4aa..8f46ba98e2d6 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jactl-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jactl-language.adoc
@@ -216,7 +216,7 @@ language can often be run without change in the other.
For example, here are some of the things that are the same:
-* `//` and `/* */` style commends.
+* `//` and `/* */` style comments.
* Semicolons are optional unless there are multiple statements on the same
line.
* Closures: `{ x,y -> x + y}`, the implicit `it` variable, and trailing
closure-call syntax `list.map{ it * 2 }`.
* `def` for dynamic types
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
index 064e887b2542..853775f99ac5 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/kafka-component.adoc
@@ -1471,7 +1471,7 @@ TIP: In XML and YAML, register the
`GroupedExchangeAggregationStrategy` as a bea
The reason for this is related to how the producer handles the two different
cases:
-* with the `aggregrate` it should process the messages in a "batch-sized
chunk" semi-asynchronously (that is, send all messages in the batch and then
wait for their acknowledgements)
+* with the `aggregate` it should process the messages in a "batch-sized chunk"
semi-asynchronously (that is, send all messages in the batch and then wait for
their acknowledgements)
* without that, it sends synchronously, eventually blocking on the record
metadata fetch per exchange.
NOTE: the downside of this approach is an increased number of in-flight
exchanges and the potential risks (even though small and rare) associated with
that.
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-component.adoc
index 539c73f8843f..32ae1985ecf8 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-component.adoc
@@ -65,7 +65,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho:topic", payload);
----
-Of course, Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you.
+Of course, Camel built-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you.
In the example below Camel automatically converts binary payload into `String`
(and conversely):
._Java-only: automatic type conversion of payloads_
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-mqtt5-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-mqtt5-component.adoc
index 4ebe6c0cc4d2..58119b329ad5 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-mqtt5-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/paho-mqtt5-component.adoc
@@ -63,7 +63,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho-mqtt5:topic", payload);
----
-Of course, Camel build-in xref:manual::type-converter.adoc[type conversion
+Of course, Camel built-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into `String`
(and conversely):
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xchange-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xchange-component.adoc
index 19447778ad20..95a2622989e9 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xchange-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/xchange-component.adoc
@@ -58,7 +58,7 @@ For Binance, for example, this would be:
`~/.ssh/binance-secret.keys`
----
##
-# This file MUST NEVER be commited to source control.
+# This file MUST NEVER be committed to source control.
# It is therefore added to .gitignore.
#
apiKey = GuRW0*********
diff --git a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
index b3ca81ea0030..76bfc268bdcf 100644
--- a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
+++ b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
@@ -105,7 +105,7 @@ character supported is tab (\t). No other whitespace
characters (spaces) are not
interpreted as a regular expression. If you want to use a sign which has a
special meaning in regular
expressions, e.g., the '\|' sign, then you have to mask it, like '\|'
-| allowEmptyStream | boolean | | false | The allowEmptyStream parameter will
allow to prcoess the unavaiable stream for CSV file.
+| allowEmptyStream | boolean | | false | The allowEmptyStream parameter will
allow to process the unavailable stream for CSV file.
| autospanLine | boolean | | false a| Last record spans rest of line
(optional) - if enabled then the last column is auto spanned to end of line, for
example if it is a comment, etc this allows the line to contain all
characters, also the delimiter char.
@@ -1313,7 +1313,7 @@ Header classes
The KeyValuePairField annotation defines the property of a key value
pair field. Each KeyValuePairField is identified by a tag (= key) and
-its value associated, a type (string, int, date, ...), optionaly a
+its value associated, a type (string, int, date, ...), optionally a
pattern and if the field is required.
[width="100%",cols="15%s,15%,60%",options="header",]
@@ -1342,7 +1342,7 @@ to @Message.continueParseOnFailure.
| name | String | | | name of the field (optional)
-| pattern | String | | | pattern that the formater will use to transform the
data (optional)
+| pattern | String | | | pattern that the formatter will use to transform
the data (optional)
| position | int | | 0 a| Position of the field in the message generated -
must be used when the position of the key/tag in the FIX message
must be different
diff --git
a/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/CsvRecord.java
b/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/CsvRecord.java
index e2012370a7d2..93b0263fedcc 100644
---
a/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/CsvRecord.java
+++
b/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/CsvRecord.java
@@ -105,7 +105,7 @@ public @interface CsvRecord {
boolean autospanLine() default false;
/**
- * The allowEmptyStream parameter will allow to prcoess the unavaiable
stream for CSV file.
+ * The allowEmptyStream parameter will allow to process the unavailable
stream for CSV file.
*/
boolean allowEmptyStream() default false;
diff --git
a/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/KeyValuePairField.java
b/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/KeyValuePairField.java
index e289c62296ed..3840ffe217fa 100644
---
a/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/KeyValuePairField.java
+++
b/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/annotation/KeyValuePairField.java
@@ -48,7 +48,7 @@ public @interface KeyValuePairField {
String name() default "";
/**
- * pattern that the formater will use to transform the data (optional)
+ * pattern that the formatter will use to transform the data (optional)
*
* @return String
*/
diff --git a/components/camel-coap/src/main/docs/coap-component.adoc
b/components/camel-coap/src/main/docs/coap-component.adoc
index 1362c3f1beee..947b3ed06e44 100644
--- a/components/camel-coap/src/main/docs/coap-component.adoc
+++ b/components/camel-coap/src/main/docs/coap-component.adoc
@@ -464,7 +464,7 @@ DTLS.RETRANSMISSION_TIMEOUT_SCALE=2.0
DTLS.ROLE=BOTH
# Use minimal version of RFC5746 to indicate secure renegotiation on
# initial handshake.
-# Renegotation handshakes are always rejected by Californium.
+# Renegotiation handshakes are always rejected by Californium.
# [NONE, WANTED, NEEDED].
# Default: WANTED
DTLS.SECURE_RENEGOTIATION_MODE=WANTED
@@ -567,7 +567,7 @@ TCP.WORKER_THREADS=0
# Maximum number of pending outgoing messages.
# Default: 2147483647
UDP.CONNECTOR_OUT_CAPACITY=2147483647
-# Maxium size of UDP datagram.
+# Maximum size of UDP datagram.
# Default: 2048
UDP.DATAGRAM_SIZE=2048
# Number of UDP receiver threads.
diff --git a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
index 76ca4feeb9ce..49fcde59a1b6 100644
--- a/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
+++ b/components/camel-crypto/src/main/docs/crypto-dataformat.adoc
@@ -13,9 +13,9 @@ The Crypto Data Format integrates the Java
Cryptographic Extension into Camel, allowing simple and flexible
encryption and decryption of messages using Camel's familiar marshall
and unmarshal formatting mechanism. It assumes marshaling to mean
-encryption to cyphertext and unmarshalling to mean decryption back to
+encryption to ciphertext and unmarshalling to mean decryption back to
the original plaintext. This data format implements only symmetric
-(shared-key) encryption and decyption.
+(shared-key) encryption and decryption.
== CryptoDataFormat Options
@@ -140,7 +140,7 @@ from("direct:init-vector")
.to("mock:unencrypted");
----
-or with spring, suppling a reference to a byte[]
+or with spring, supplying a reference to a byte[]
[source,xml]
----
diff --git
a/components/camel-disruptor/src/main/docs/disruptor-vm-component.adoc
b/components/camel-disruptor/src/main/docs/disruptor-vm-component.adoc
index a0f0e341f3ee..b9a7036d30b1 100644
--- a/components/camel-disruptor/src/main/docs/disruptor-vm-component.adoc
+++ b/components/camel-disruptor/src/main/docs/disruptor-vm-component.adoc
@@ -39,7 +39,7 @@ behavior and options of the SEDA component as much as
possible.
The main differences between them are the following:
* The buffer used is always bounded in size (default 1024 exchanges).
-* As the buffer is always bouded, the default behaviour for the
+* As the buffer is always bounded, the default behaviour for the
Disruptor is to block while the buffer is full instead of throwing an
exception. This default behavior may be configured on the component
(see options).
diff --git a/components/camel-google/src/main/docs/google-summary.adoc
b/components/camel-google/src/main/docs/google-summary.adoc
index 3541aa5314da..70028d0ec425 100644
--- a/components/camel-google/src/main/docs/google-summary.adoc
+++ b/components/camel-google/src/main/docs/google-summary.adoc
@@ -4,7 +4,7 @@
The *google-* component allows you to work with the
https://gsuite.google.co.in/[G Suite].
-Google offers a great palette of different components like use of calender,
mail, sheets and
+Google offers a great palette of different components like use of calendar,
mail, sheets and
drive . The main reason to use Google is the G Suite features.
== {doctitle} components
diff --git a/components/camel-grok/src/main/docs/grok-dataformat.adoc
b/components/camel-grok/src/main/docs/grok-dataformat.adoc
index cdf2d3441c01..e947cd3516f1 100644
--- a/components/camel-grok/src/main/docs/grok-dataformat.adoc
+++ b/components/camel-grok/src/main/docs/grok-dataformat.adoc
@@ -129,7 +129,7 @@ All
https://github.com/thekrakken/java-grok/tree/master/src/main/resources/patte
=== Custom patterns
-Camel Grok DataFormat supports plugable patterns, which are auto loaded from
Camel Registry.
+Camel Grok DataFormat supports pluggable patterns, which are auto loaded from
Camel Registry.
You can register patterns with Java DSL and Spring DSL:
._Java-only: registering a custom Grok pattern_
diff --git
a/components/camel-hazelcast/src/main/docs/hazelcast-pncounter-component.adoc
b/components/camel-hazelcast/src/main/docs/hazelcast-pncounter-component.adoc
index 36c9aee9ca69..e136493a4f4a 100644
---
a/components/camel-hazelcast/src/main/docs/hazelcast-pncounter-component.adoc
+++
b/components/camel-hazelcast/src/main/docs/hazelcast-pncounter-component.adoc
@@ -17,7 +17,7 @@
The http://www.hazelcast.com/[Hazelcast] PN Counter component is one of Camel
Hazelcast Components which allows you to access a Hazelcast PN Counter (CRDT
counter).
A PN Counter is a Conflict-free Replicated Data Type (CRDT) that provides a
distributed counter with eventual consistency guarantees.
-This component is not a direct replacement for the hazelcast-atomicvalue
component that is availble in Camel 2.7 -> 4.19, but it does replicates most of
the functionality (get / increment / decrement / getAndAdd / destroy) apart
from the compare method.
+This component is not a direct replacement for the hazelcast-atomicvalue
component that is available in Camel 2.7 -> 4.19, but it does replicate most of
the functionality (get / increment / decrement / getAndAdd / destroy) apart
from the compare method.
// component options: START
diff --git a/components/camel-jactl/src/main/docs/jactl-language.adoc
b/components/camel-jactl/src/main/docs/jactl-language.adoc
index 6e25278ea4aa..8f46ba98e2d6 100644
--- a/components/camel-jactl/src/main/docs/jactl-language.adoc
+++ b/components/camel-jactl/src/main/docs/jactl-language.adoc
@@ -216,7 +216,7 @@ language can often be run without change in the other.
For example, here are some of the things that are the same:
-* `//` and `/* */` style commends.
+* `//` and `/* */` style comments.
* Semicolons are optional unless there are multiple statements on the same
line.
* Closures: `{ x,y -> x + y}`, the implicit `it` variable, and trailing
closure-call syntax `list.map{ it * 2 }`.
* `def` for dynamic types
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc
b/components/camel-kafka/src/main/docs/kafka-component.adoc
index 064e887b2542..853775f99ac5 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -1471,7 +1471,7 @@ TIP: In XML and YAML, register the
`GroupedExchangeAggregationStrategy` as a bea
The reason for this is related to how the producer handles the two different
cases:
-* with the `aggregrate` it should process the messages in a "batch-sized
chunk" semi-asynchronously (that is, send all messages in the batch and then
wait for their acknowledgements)
+* with the `aggregate` it should process the messages in a "batch-sized chunk"
semi-asynchronously (that is, send all messages in the batch and then wait for
their acknowledgements)
* without that, it sends synchronously, eventually blocking on the record
metadata fetch per exchange.
NOTE: the downside of this approach is an increased number of in-flight
exchanges and the potential risks (even though small and rare) associated with
that.
diff --git
a/components/camel-paho-mqtt5/src/main/docs/paho-mqtt5-component.adoc
b/components/camel-paho-mqtt5/src/main/docs/paho-mqtt5-component.adoc
index 4ebe6c0cc4d2..58119b329ad5 100644
--- a/components/camel-paho-mqtt5/src/main/docs/paho-mqtt5-component.adoc
+++ b/components/camel-paho-mqtt5/src/main/docs/paho-mqtt5-component.adoc
@@ -63,7 +63,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho-mqtt5:topic", payload);
----
-Of course, Camel build-in xref:manual::type-converter.adoc[type conversion
+Of course, Camel built-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you. In the
example below Camel automatically converts binary payload into `String`
(and conversely):
diff --git a/components/camel-paho/src/main/docs/paho-component.adoc
b/components/camel-paho/src/main/docs/paho-component.adoc
index 539c73f8843f..32ae1985ecf8 100644
--- a/components/camel-paho/src/main/docs/paho-component.adoc
+++ b/components/camel-paho/src/main/docs/paho-component.adoc
@@ -65,7 +65,7 @@ byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho:topic", payload);
----
-Of course, Camel build-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you.
+Of course, Camel built-in xref:manual::type-converter.adoc[type conversion
API] can perform the automatic data type transformations for you.
In the example below Camel automatically converts binary payload into `String`
(and conversely):
._Java-only: automatic type conversion of payloads_
diff --git a/components/camel-xchange/src/main/docs/xchange-component.adoc
b/components/camel-xchange/src/main/docs/xchange-component.adoc
index 19447778ad20..95a2622989e9 100644
--- a/components/camel-xchange/src/main/docs/xchange-component.adoc
+++ b/components/camel-xchange/src/main/docs/xchange-component.adoc
@@ -58,7 +58,7 @@ For Binance, for example, this would be:
`~/.ssh/binance-secret.keys`
----
##
-# This file MUST NEVER be commited to source control.
+# This file MUST NEVER be committed to source control.
# It is therefore added to .gitignore.
#
apiKey = GuRW0*********
diff --git
a/components/camel-zip-deflater/src/main/docs/gzipDeflater-dataformat.adoc
b/components/camel-zip-deflater/src/main/docs/gzipDeflater-dataformat.adoc
index 741a2bf4c8df..eb598942e8ae 100644
--- a/components/camel-zip-deflater/src/main/docs/gzipDeflater-dataformat.adoc
+++ b/components/camel-zip-deflater/src/main/docs/gzipDeflater-dataformat.adoc
@@ -16,7 +16,7 @@ headers are provided. This format is produced by popular
`gzip`/`gunzip`
tool. Messages marshalled using GZip compression can be unmarshalled
using GZip decompression just prior to being consumed at the endpoint.
The compression capability is quite useful when you deal with large XML
-and text-based payloads or when you read messages previously comressed
+and text-based payloads or when you read messages previously compressed
using `gzip` tool.
[NOTE]
