You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by or...@apache.org on 2024/02/19 17:56:02 UTC

(camel) branch main updated (a55c79bb059 -> 7274d3dd975)

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

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


    from a55c79bb059 CAMEL-20410: documentation fixes for camel-dynamic-router
     new 1b13bfe4e36 CAMEL-20410: documentation fixes for camel-paho
     new d24ce585e6b CAMEL-20410: documentation fixes for camel-paho-mqtt5
     new b70262fe40c CAMEL-20410: documentation fixes for camel-rocketmq
     new fc050d156a3 CAMEL-20410: documentation fixes for camel-jasypt
     new 5adc2c53e60 CAMEL-20410: documentation fixes for camel-ironmq
     new b4e5b8769c1 CAMEL-20410: documentation fixes for camel-irc
     new e20800562b5 CAMEL-20410: documentation fixes for camel-jolt
     new 7274d3dd975 CAMEL-20410: documentation fixes for camel-weather

The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../camel-irc/src/main/docs/irc-component.adoc     | 19 +++++++--------
 .../src/main/docs/ironmq-component.adoc            |  9 ++++----
 components/camel-jasypt/src/main/docs/jasypt.adoc  | 27 +++++++++++-----------
 .../camel-jolt/src/main/docs/jolt-component.adoc   | 12 +++++-----
 .../src/main/docs/paho-mqtt5-component.adoc        | 18 +++++++--------
 .../camel-paho/src/main/docs/paho-component.adoc   | 22 ++++++++----------
 .../src/main/docs/rocketmq-component.adoc          |  3 ++-
 .../src/main/docs/weather-component.adoc           |  6 ++---
 8 files changed, 59 insertions(+), 57 deletions(-)


(camel) 06/08: CAMEL-20410: documentation fixes for camel-irc

Posted by 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

commit b4e5b8769c11aacddef8cb1697196ec210ecb78d
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 17:10:33 2024 +0100

    CAMEL-20410: documentation fixes for camel-irc
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 components/camel-irc/src/main/docs/irc-component.adoc | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/components/camel-irc/src/main/docs/irc-component.adoc b/components/camel-irc/src/main/docs/irc-component.adoc
index 48e0301e66f..2a14a08908c 100644
--- a/components/camel-irc/src/main/docs/irc-component.adoc
+++ b/components/camel-irc/src/main/docs/irc-component.adoc
@@ -53,8 +53,9 @@ include::partial$component-endpoint-headers.adoc[]
 
 The IRC component supports SSL/TLS configuration
 through the xref:manual::camel-configuration-utilities.adoc[Camel JSSE
-Configuration Utility].  This utility greatly decreases the amount of
-component specific code you need to write and is configurable at the
+Configuration Utility].
+This utility greatly decreases the amount of
+component-specific code you need to write and is configurable at the
 endpoint and component levels.  The following examples demonstrate how
 to use the utility with the IRC component.
 
@@ -121,23 +122,23 @@ ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTr
 
 == Using keys
 
-Some irc rooms requires you to provide a key to be able to join that
+Some IRC rooms require you to provide a key to be able to join that
 channel. The key is just a secret word.
 
-For example we join 3 channels where as only channel 1 and 3 uses a key.
+For example, we join three channels whereas only channel 1 and 3 use a key.
 
 [source,java]
 -----------------------------------------------------------------------------
 irc:nick@irc.server.org?channels=#chan1,#chan2,#chan3&keys=chan1Key,,chan3key
 -----------------------------------------------------------------------------
 
-== Getting a list of users of the channel
+== Getting a list of channel users
 
 Using the `namesOnJoin` option one can invoke the IRC-`NAMES` command after the component has joined a channel. 
-The server will reply with `irc.num = 353`. So in order to process the result the property `onReply` has to be `true`.
-Furthermore one has to filter the `onReply` exchanges in order to get the names.
+The server will reply with `irc.num = 353`. So to process the result the property `onReply` has to be `true`.
+Furthermore, one has to filter the `onReply` exchanges to get the names.
 
-For example we want to get all exchanges that contain the usernames of the channel:
+For example, we want to get all exchanges that contain the usernames of the channel:
 
 [source,java]
 -----------------------------------------------------------------------------
@@ -148,7 +149,7 @@ from("ircs:nick@myserver:1234/#mychannelname?namesOnJoin=true&onReply=true")
 			.to("mock:result").stop();
 -----------------------------------------------------------------------------
 
-== Sending to different channel or a person
+== Sending to a different channel or a person
 
 If you need to send messages to a different channel (or a person) which is not defined on IRC endpoint, you can specify a different destination in a message header.
 


(camel) 01/08: CAMEL-20410: documentation fixes for camel-paho

Posted by 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

commit 1b13bfe4e36105b5061645b016bc3484f25e0903
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 16:54:50 2024 +0100

    CAMEL-20410: documentation fixes for camel-paho
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 .../camel-paho/src/main/docs/paho-component.adoc   | 22 ++++++++++------------
 1 file changed, 10 insertions(+), 12 deletions(-)

diff --git a/components/camel-paho/src/main/docs/paho-component.adoc b/components/camel-paho/src/main/docs/paho-component.adoc
index 08671f238e5..e0efda9ea26 100644
--- a/components/camel-paho/src/main/docs/paho-component.adoc
+++ b/components/camel-paho/src/main/docs/paho-component.adoc
@@ -14,9 +14,9 @@
 
 *{component-header}*
 
-Paho component provides connector for the MQTT messaging protocol using
-the https://eclipse.org/paho/[Eclipse Paho] library. Paho is one of the
-most popular MQTT libraries, so if you would like to integrate it with
+Paho component provides a connector for the https://en.wikipedia.org/wiki/MQTT[MQTT] messaging protocol using
+the https://eclipse.org/paho/[Eclipse Paho] library.
+Paho is one of the most popular MQTT libraries, so if you would like to integrate it with
 your Java project - Camel Paho connector is a way to go.
 
 Maven users will need to add the following dependency to their `pom.xml`
@@ -39,7 +39,7 @@ for this component:
 paho:topic[?options]
 ----
 
-Where *topic* is the name of the topic.
+Where `topic` is the name of the topic.
 
 
 // component-configure options: START
@@ -61,7 +61,7 @@ include::partial$component-endpoint-headers.adoc[]
 
 == Default payload type
 
-By default, Camel Paho component operates on the binary payloads
+By default, the Camel Paho component operates on the binary payloads
 extracted out of (or put into) the MQTT message:
 
 [source,java]
@@ -74,10 +74,8 @@ byte[] payload = "message".getBytes();
 producerTemplate.sendBody("paho:topic", payload);
 ----
 
-But of course Camel build-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):
+Of course, Camel build-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):
 
 [source,java]
 ----
@@ -92,7 +90,7 @@ producerTemplate.sendBody("paho:topic", payload);
 
 == Samples
 
-For example the following snippet reads messages from the MQTT broker
+For example, the following snippet reads messages from the MQTT broker
 installed on the same host as the Camel router:
 
 [source,java]
@@ -101,7 +99,7 @@ from("paho:some/queue")
     .to("mock:test");
 ----
 
-While the snippet below sends message to the MQTT broker:
+While the snippet below sends a message to the MQTT broker:
 
 [source,java]
 ----
@@ -109,7 +107,7 @@ from("direct:test")
     .to("paho:some/target/queue");
 ----
 
-For example this is how to read messages from the remote MQTT broker: 
+For example, this is how to read messages from the remote MQTT broker:
 
 [source,java]
 ----


(camel) 05/08: CAMEL-20410: documentation fixes for camel-ironmq

Posted by 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

commit 5adc2c53e60f865015e482dfeaf73d3218691574
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 17:07:50 2024 +0100

    CAMEL-20410: documentation fixes for camel-ironmq
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 components/camel-ironmq/src/main/docs/ironmq-component.adoc | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/components/camel-ironmq/src/main/docs/ironmq-component.adoc b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
index 42fb5031fe5..78775896f4a 100644
--- a/components/camel-ironmq/src/main/docs/ironmq-component.adoc
+++ b/components/camel-ironmq/src/main/docs/ironmq-component.adoc
@@ -20,7 +20,7 @@ The component uses the
 https://github.com/iron-io/iron_mq_java[IronMQ java client]
 library.
 
-To run it requires a IronMQ account, and a project id and token.
+To run it requires an IronMQ account and a project id and token.
 
 Maven users will need to add the following dependency to their `pom.xml`
 for this component:
@@ -40,7 +40,7 @@ for this component:
 -----------------------------
  ironmq:queueName[?options]
 -----------------------------
-Where **queueName** identifies the IronMQ queue you want to publish or consume messages from.
+Where `queueName` identifies the IronMQ queue you want to publish or consume messages from.
 
 
 // component-configure options: START
@@ -61,11 +61,12 @@ include::partial$component-endpoint-headers.adoc[]
 
 == Message Body
 
-Should be either a String or a array of Strings. In the latter case the batch of strings will be sent to IronMQ as one request, creating one message pr. element in the array.
+It should be either a String or an array of Strings.
+In the latter case, the batch of strings will be sent to IronMQ as one request, creating one message per element in the array.
 
 == Consumer example
 
-Consume 50 messages pr. poll from the queue 'testqueue' on aws eu, and save the messages to files.
+Consume 50 messages per poll from the queue `testqueue` on aws eu, and save the messages to files.
 
 [source,java]
 --------------------------------------------------


(camel) 03/08: CAMEL-20410: documentation fixes for camel-rocketmq

Posted by 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

commit b70262fe40c4e8f083b50382fd3dc203537d0f1a
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 16:59:49 2024 +0100

    CAMEL-20410: documentation fixes for camel-rocketmq
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 components/camel-rocketmq/src/main/docs/rocketmq-component.adoc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/components/camel-rocketmq/src/main/docs/rocketmq-component.adoc b/components/camel-rocketmq/src/main/docs/rocketmq-component.adoc
index b7ff3b9bb4b..836d6a56cc9 100644
--- a/components/camel-rocketmq/src/main/docs/rocketmq-component.adoc
+++ b/components/camel-rocketmq/src/main/docs/rocketmq-component.adoc
@@ -66,7 +66,8 @@ include::partial$component-endpoint-headers.adoc[]
 
 == InOut Pattern
 
-InOut Pattern based on Message Key. When the producer sending the message, a messageKey will be generated and append to the message's key.
+InOut Pattern based on Message Key.
+When the producer sends the message, a messageKey will be generated and append to the message's key.
 
 After the message sent, a consumer will listen to the topic configured by the parameter `ReplyToTopic`.
 


(camel) 02/08: CAMEL-20410: documentation fixes for camel-paho-mqtt5

Posted by 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

commit d24ce585e6b63b274125437eab3757a54960a4b0
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 16:58:04 2024 +0100

    CAMEL-20410: documentation fixes for camel-paho-mqtt5
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 .../src/main/docs/paho-mqtt5-component.adoc            | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

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 061dc2a61f1..8e74398b3b7 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
@@ -14,9 +14,9 @@
 
 *{component-header}*
 
-Paho MQTT5 component provides connector for the MQTT messaging protocol using
-the https://eclipse.org/paho/[Eclipse Paho] library with MQTT v5. Paho is one of the
-most popular MQTT libraries, so if you would like to integrate it with
+Paho MQTT5 component provides connector for the https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html[MQTT messaging protocol version 5.0]
+using the https://eclipse.org/paho/[Eclipse Paho] library.
+Paho is one of the most popular MQTT libraries, so if you would like to integrate it with
 your Java project - Camel Paho connector is a way to go.
 
 Maven users will need to add the following dependency to their `pom.xml`
@@ -38,7 +38,7 @@ for this component:
 paho-mqtt5:topic[?options]
 ----
 
-Where *topic* is the name of the topic.
+Where `topic` is the name of the topic.
 
 
 // component-configure options: START
@@ -60,7 +60,7 @@ include::partial$component-endpoint-headers.adoc[]
 
 == Default payload type
 
-By default, Camel Paho component operates on the binary payloads
+By default, the Camel Paho component operates on the binary payloads
 extracted out of (or put into) the MQTT message:
 
 [source,java]
@@ -73,7 +73,7 @@ byte[] payload = "message".getBytes();
 producerTemplate.sendBody("paho-mqtt5:topic", payload);
 ----
 
-But of course Camel build-in xref:manual::type-converter.adoc[type conversion
+Of course, Camel build-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):
@@ -91,7 +91,7 @@ producerTemplate.sendBody("paho-mqtt5:topic", payload);
 
 == Samples
 
-For example the following snippet reads messages from the MQTT broker
+For example, the following snippet reads messages from the MQTT broker
 installed on the same host as the Camel router:
 
 [source,java]
@@ -100,7 +100,7 @@ from("paho-mqtt5:some/queue")
     .to("mock:test");
 ----
 
-While the snippet below sends message to the MQTT broker:
+While the snippet below sends a message to the MQTT broker:
 
 [source,java]
 ----
@@ -108,7 +108,7 @@ from("direct:test")
     .to("paho-mqtt5:some/target/queue");
 ----
 
-For example this is how to read messages from the remote MQTT broker: 
+For example, this is how to read messages from the remote MQTT broker:
 
 [source,java]
 ----


(camel) 07/08: CAMEL-20410: documentation fixes for camel-jolt

Posted by 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

commit e20800562b59a8c0a4caeb18f986f36e044f8860
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 17:13:14 2024 +0100

    CAMEL-20410: documentation fixes for camel-jolt
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 components/camel-jolt/src/main/docs/jolt-component.adoc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/components/camel-jolt/src/main/docs/jolt-component.adoc b/components/camel-jolt/src/main/docs/jolt-component.adoc
index bf4b259ac3e..b61708857ca 100644
--- a/components/camel-jolt/src/main/docs/jolt-component.adoc
+++ b/components/camel-jolt/src/main/docs/jolt-component.adoc
@@ -14,7 +14,7 @@
 
 *{component-header}*
 
-The Jolt component allows you to process a JSON messages using an
+The Jolt component allows you to process a JSON messages using a
 https://github.com/bazaarvoice/jolt[JOLT] specification. This can be
 ideal when doing JSON to JSON transformation.
 
@@ -38,9 +38,9 @@ their `pom.xml` for this component:
 jolt:specName[?options]
 -----------------------
 
-Where *specName* is the classpath-local URI of the specification to
+Where `specName` is the classpath-local URI of the specification to
 invoke; or the complete URL of the remote specification
-(eg: \file://folder/myfile.vm).
+(e.g.: `\file://folder/myfile.vm`).
 
 
 // component-configure options: START
@@ -61,7 +61,7 @@ include::partial$component-endpoint-headers.adoc[]
 
 == Samples
 
-For example you could use something like
+For example, you could use something like
 
 [source,java]
 --------------------------------------
@@ -69,7 +69,7 @@ from("activemq:My.Queue").
   to("jolt:com/acme/MyResponse.json");
 --------------------------------------
 
-And a file based resource:
+And a file-based resource:
 
 [source,java]
 ---------------------------------------------------------------
@@ -79,7 +79,7 @@ from("activemq:My.Queue").
 ---------------------------------------------------------------
 
 You can also specify what specification the component should use
-dynamically via a header, so for example:
+dynamically via a header, so, for example:
 
 [source,java]
 ---------------------------------------------------------------------


(camel) 08/08: CAMEL-20410: documentation fixes for camel-weather

Posted by 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

commit 7274d3dd9754be36d144d408938b66c362bc68ae
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 17:14:44 2024 +0100

    CAMEL-20410: documentation fixes for camel-weather
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 components/camel-weather/src/main/docs/weather-component.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/components/camel-weather/src/main/docs/weather-component.adoc b/components/camel-weather/src/main/docs/weather-component.adoc
index 2e215ab200d..2bb84605cf2 100644
--- a/components/camel-weather/src/main/docs/weather-component.adoc
+++ b/components/camel-weather/src/main/docs/weather-component.adoc
@@ -63,7 +63,7 @@ include::partial$component-endpoint-headers.adoc[]
 
 == Exchange data format
 
-Camel will deliver the body as a json formatted java.lang.String (see
+Camel will deliver the body as a json formatted `java.lang.String` (see
 the `mode` option above).
 
 == Samples
@@ -75,7 +75,7 @@ In this sample we find the 7-day weather forecast for Madrid, Spain:
 from("weather:foo?location=Madrid,Spain&period=7 days&appid=APIKEY&geolocationAccessKey=IPSTACK_ACCESS_KEY&geolocationRequestHostIP=LOCAL_IP").to("jms:queue:weather");
 ---------------------------------------------------------------------------------------------
 
-To just find the current weather for your current location you can use
+To just find the current weather for your current location, you can use
 this:
 
 [source,java]
@@ -83,7 +83,7 @@ this:
 from("weather:foo?appid=APIKEY&geolocationAccessKey=IPSTACK_ACCESS_KEY&geolocationRequestHostIP=LOCAL_IP").to("jms:queue:weather");
 ---------------------------------------------------------
 
-And to find the weather using the producer we do:
+And to find the weather using the producer, we do:
 
 [source,java]
 --------------------------------------------------------


(camel) 04/08: CAMEL-20410: documentation fixes for camel-jasypt

Posted by 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

commit fc050d156a3a4c7a7cdd9710bddaed007a1b86f8
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Mon Feb 19 17:04:42 2024 +0100

    CAMEL-20410: documentation fixes for camel-jasypt
    
    - Fixed samples
    - Fixed grammar and typos
    - Fixed punctuation
    - Added and/or fixed links
---
 components/camel-jasypt/src/main/docs/jasypt.adoc | 27 ++++++++++++-----------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/components/camel-jasypt/src/main/docs/jasypt.adoc b/components/camel-jasypt/src/main/docs/jasypt.adoc
index 4aeb2a19776..3165019294d 100644
--- a/components/camel-jasypt/src/main/docs/jasypt.adoc
+++ b/components/camel-jasypt/src/main/docs/jasypt.adoc
@@ -11,7 +11,7 @@
 
 *Since Camel {since}*
 
-http://www.jasypt.org/[Jasypt] is a simplified encryption library which
+http://www.jasypt.org/[Jasypt] is a simplified encryption library that
 makes encryption and decryption easy. Camel integrates with Jasypt to
 allow sensitive information in xref:ROOT:properties-component.adoc[Properties] files to
 be encrypted. By dropping *`camel-jasypt`* on the classpath those
@@ -68,7 +68,7 @@ Encrypted text: qaEEacuW7BUti8LcMgyjKw==
 ----------------------------------------
 
 This means the encrypted representation `qaEEacuW7BUti8LcMgyjKw==` can
-be decrypted back to `tiger` if you know the master password which was
+be decrypted back to `tiger` if you know the _master_ password which was
 `secret`. +
  If you run the tool again, then the encrypted value will return a
 different result. But decrypting the value will always return the
@@ -99,14 +99,15 @@ my.secret = ENC(qaEEacuW7BUti8LcMgyjKw==)
 
 == Protecting the master password
 
-The master password used by Jasypt must be provided,
+The _master_ password used by Jasypt must be provided,
 so that it's capable of decrypting the values. However, having this
-master password out in the open may not be an ideal solution. Therefore,
+_master_ password out in the open may not be an ideal solution. Therefore,
 you can provide it as a JVM system property or as an OS
 environment setting. If you decide to do so then the `password` option
-supports prefixes which dictates this. `sysenv:` means to lookup the OS
-system environment with the given key. `sys:` means to lookup a JVM
-system property.
+supports prefix that dictates this:
+
+* `sysenv:` means to look up the OS system environment with the given key.
+* `sys:` means to look up a JVM system property.
 
 For example, you could provide the password before you start the
 application
@@ -118,7 +119,7 @@ $ export CAMEL_ENCRYPTION_PASSWORD=secret
 
 Then start the application, such as running the start script.
 
-When the application is up and running you can unset the environment
+When the application is up and running, you can unset the environment
 
 [source,bash]
 ---------------------------------
@@ -147,7 +148,7 @@ Java::
 +
 On the Spring Boot and Quarkus runtimes, Camel Jasypt can be configured via configuration properties. Refer to their respective documentation pages for more information.
 +
-Else, in Java DSL you need to configure Jasypt as a `JasyptPropertiesParser` instance and set it on the xref:ROOT:properties-component.adoc[Properties] component as show below:
+Else, in Java DSL you need to configure Jasypt as a `JasyptPropertiesParser` instance and set it on the xref:ROOT:properties-component.adoc[Properties] component as shown below:
 +
 [source,java]
 ---------------------
@@ -156,10 +157,10 @@ JasyptPropertiesParser jasypt = new JasyptPropertiesParser();
 // set the master password (see above for how to do this in a secure way)
 jasypt.setPassword("secret");
 
-// create the properties component
+// create the properties' component
 PropertiesComponent pc = new PropertiesComponent();
 pc.setLocation("classpath:org/apache/camel/component/jasypt/secret.properties");
-// and use the jasypt properties parser so we can decrypt values
+// and use the jasypt properties parser, so we can decrypt values
 pc.setPropertiesParser(jasypt);
 // end enable nested placeholder support
 pc.setNestedPlaceholder(true);
@@ -192,7 +193,7 @@ XML (Spring)::
 +
 In Spring XML you need to configure the `JasyptPropertiesParser` which
 is shown below. Then the Camel xref:ROOT:properties-component.adoc[Properties]
-component is told to use `jasypt` as the properties parser, which means
+component is told to use `jasypt` as the property parser, which means
 Jasypt has its chance to decrypt values looked up in
 the properties file.
 +
@@ -224,7 +225,7 @@ Jasypt.
 <!-- define the jasypt properties parser with the given password to be used -->
 <bean id="jasypt" class="org.apache.camel.component.jasypt.JasyptPropertiesParser">
     <!-- password is mandatory, you can prefix it with sysenv: or sys: to indicate it should use
-         an OS environment or JVM system property value, so you dont have the master password defined here -->
+         an OS environment or JVM system property value, so you don't have the master password defined here -->
     <property name="password" value="secret"/>
 </bean>