This is an automated email from the ASF dual-hosted git repository.
acosentino 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 a7a69540cfa docs: fix typos (#12681)
a7a69540cfa is described below
commit a7a69540cfaeacdf38787b6f0bd06f54a93c2d95
Author: GoodDaisy <90915921+goodda...@users.noreply.github.com>
AuthorDate: Mon Jan 8 13:34:42 2024 +0800
docs: fix typos (#12681)
---
components/camel-bindy/src/main/docs/bindy-dataformat.adoc | 4 ++--
components/camel-quickfix/src/main/docs/quickfix-component.adoc | 2 +-
.../src/main/docs/robotframework-component.adoc | 6 +++---
components/camel-thrift/src/main/docs/thrift-component.adoc | 2 +-
components/camel-xj/src/main/docs/xj-component.adoc | 4 ++--
5 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
index c76350d526f..59a7c191dd8 100644
--- a/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
+++ b/components/camel-bindy/src/main/docs/bindy-dataformat.adoc
@@ -896,7 +896,7 @@ public static class Order {
*case 3 : Field padding*
-Sometimes, the default padding defined for record cannnot be applied to
+Sometimes, the default padding defined for record cannot be applied to
the field as we have a number format where we would like to pad with
'0' instead of ' '. In this case, you can use in the model the attribute
`paddingChar` on `@DataField` to set this value.
@@ -1140,7 +1140,7 @@ public class OrderFooter {
It is common to integrate with systems that provide fixed-length records
containing more information than needed for the target use case. It is
useful in this situation to skip the declaration and parsing of those
-fields that we do not need. To accomodate this, Bindy will skip forward
+fields that we do not need. To accommodate this, Bindy will skip forward
to the next mapped field within a record if the `pos` value of the next
declared field is beyond the cursor position of the last parsed field.
Using absolute `pos` locations for the fields of interest (instead of
diff --git a/components/camel-quickfix/src/main/docs/quickfix-component.adoc
b/components/camel-quickfix/src/main/docs/quickfix-component.adoc
index f2828a966ba..e9ed1d633db 100644
--- a/components/camel-quickfix/src/main/docs/quickfix-component.adoc
+++ b/components/camel-quickfix/src/main/docs/quickfix-component.adoc
@@ -420,7 +420,7 @@ more details about FIX sequence number management.
Several examples are included in the QuickFIX/J component source code
(test subdirectories). One of these examples implements a trival trade
-excecution simulation. The example defines an application component that
+execution simulation. The example defines an application component that
uses the URI scheme "trade-executor".
The following route receives messages for the trade executor session and
diff --git
a/components/camel-robotframework/src/main/docs/robotframework-component.adoc
b/components/camel-robotframework/src/main/docs/robotframework-component.adoc
index 4630c39f3fb..8ffa91731de 100644
---
a/components/camel-robotframework/src/main/docs/robotframework-component.adoc
+++
b/components/camel-robotframework/src/main/docs/robotframework-component.adoc
@@ -2,7 +2,7 @@
:doctitle: Robot Framework
:shortname: robotframework
:artifactid: camel-robotframework
-:description: Pass camel exchanges to acceptence test written in Robot DSL.
+:description: Pass camel exchanges to acceptance test written in Robot DSL.
:since: 3.0
:supportlevel: Stable
:tabs-sync-option:
@@ -15,12 +15,12 @@
*{component-header}*
The *robotframework:* component allows for processing camel exchanges
-in acceptence test suites which are already implemented with its own DSL.
+in acceptance test suites which are already implemented with its own DSL.
The depending keyword libraries that can be used inside test suites
implemented in Robot DSL, could have been implemented either via
Java or Pyhton.
-This component will let you execute business logic of acceptence test cases
+This component will let you execute business logic of acceptance test cases
in Robot language on which you can pass parameters to feed data via power
of Camel Routes, however there is no reverse binding of parameters back where
you can pass values back into Camel exchange. Therefore, for that reason,
diff --git a/components/camel-thrift/src/main/docs/thrift-component.adoc
b/components/camel-thrift/src/main/docs/thrift-component.adoc
index cf2a155b316..a7b34e28c0a 100644
--- a/components/camel-thrift/src/main/docs/thrift-component.adoc
+++ b/components/camel-thrift/src/main/docs/thrift-component.adoc
@@ -58,7 +58,7 @@ include::partial$component-endpoint-headers.adoc[]
== Thrift method parameters mapping
Parameters in the called procedure must be passed as a list of objects inside
the message body. The primitives are converted from the objects on the fly.
-In order to correctly find the corresponding method, all types must be
transmitted regardless of the values. Please see an exmaple below, how to pass
+In order to correctly find the corresponding method, all types must be
transmitted regardless of the values. Please see an example below, how to pass
different parameters to the method with the Camel body
[source,java]
-------------------------------------------------------------------------------
diff --git a/components/camel-xj/src/main/docs/xj-component.adoc
b/components/camel-xj/src/main/docs/xj-component.adoc
index 89f1a68e139..7f63e495666 100644
--- a/components/camel-xj/src/main/docs/xj-component.adoc
+++ b/components/camel-xj/src/main/docs/xj-component.adoc
@@ -246,7 +246,7 @@ will result in
----
You may have noted that the input xml and output json is very similar to the
examples above when converting from json to xml
-altough nothing special is done here. We only transformed an arbitrary XML
document to json.
+although nothing special is done here. We only transformed an arbitrary XML
document to json.
XJ uses the following rules by default:
* The XML root element can be named somehow, it will always end in a json root
object declaration '{}'
@@ -354,7 +354,7 @@ and get the following output:
}
----
-Note, this transformation resulted in exactly the same json document as we
used as input to the json2xml convertion.
+Note, this transformation resulted in exactly the same json document as we
used as input to the json2xml conversion.
What did the stylesheet do? We just gave some hints to XJ on how to write the
json document. The following XML
document is that what is passed to XJ after xsl transformation:
