You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ja...@apache.org on 2023/02/07 07:33:01 UTC
[camel-quarkus] 15/18: Fix various documentation typos
This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch 2.13.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
commit 8c76bec471816c4b5d86b754b226609abb136271
Author: James Netherton <ja...@gmail.com>
AuthorDate: Thu Feb 2 14:27:09 2023 +0000
Fix various documentation typos
---
docs/modules/ROOT/pages/contributor-guide/release-guide.adoc | 2 +-
docs/modules/ROOT/pages/migration-guide/2.11.0.adoc | 2 +-
docs/modules/ROOT/pages/reference/extensions/leveldb.adoc | 4 ++--
docs/modules/ROOT/pages/user-guide/configuration.adoc | 2 +-
docs/modules/ROOT/pages/user-guide/defining-camel-routes.adoc | 2 +-
docs/modules/ROOT/pages/user-guide/native-mode.adoc | 2 +-
extensions/leveldb/runtime/src/main/doc/limitations.adoc | 4 ++--
7 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
index 55c59a77d0..e9114a18dc 100644
--- a/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
+++ b/docs/modules/ROOT/pages/contributor-guide/release-guide.adoc
@@ -82,7 +82,7 @@ $ cd tooling/perf-regression
$ java -jar target/quarkus-app/quarkus-run.jar -an 2.9.0 2.10.0
----
-After approximatively 1 hour, it should generate a report like below:
+After approximately 1 hour, it should generate a report like below:
[source,shell]
----
diff --git a/docs/modules/ROOT/pages/migration-guide/2.11.0.adoc b/docs/modules/ROOT/pages/migration-guide/2.11.0.adoc
index 6c247cfdd1..d07ddc69ac 100644
--- a/docs/modules/ROOT/pages/migration-guide/2.11.0.adoc
+++ b/docs/modules/ROOT/pages/migration-guide/2.11.0.adoc
@@ -4,6 +4,6 @@ The following guide outlines how to adapt your code to changes that were made in
== Changes to Quartz clustering support
-In previous releases the Camel Quarkus Quartz documention listed various means of configuring Quartz for clustering. This has now been simplified
+In previous releases the Camel Quarkus Quartz documentation listed various means of configuring Quartz for clustering. This has now been simplified
to a single set of instructions that leverages Quarkus Quartz. If you are using one of the previous methods of clustering, it is advised to update your
application to the new method documented in the xref:reference/extensions/quartz.adoc[Quartz extension guide].
diff --git a/docs/modules/ROOT/pages/reference/extensions/leveldb.adoc b/docs/modules/ROOT/pages/reference/extensions/leveldb.adoc
index 7ffb4e4fd7..cb419311b6 100644
--- a/docs/modules/ROOT/pages/reference/extensions/leveldb.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/leveldb.adoc
@@ -51,14 +51,14 @@ In native mode the extension uses a port of LevelDB written in Java (https://git
which is within 10% of the performance of the C++ original. Please upvote https://github.com/apache/camel-quarkus/issues/1911[this issue]
if you do not like the present state.
-Serialization is https://github.com/oracle/graal/issues/460[not supported] on GraalVM. Extension has to use serializationization based
+Serialization is https://github.com/oracle/graal/issues/460[not supported] on GraalVM. Extension has to use serialization based
on Jackson. Aggregation repository in native has to be constructed in one of the following ways:
* Use class `QuarkusLevelDBAggregationRepository` instead of `LevelDBAggregationRepository`.
* Configure jackson serializer on `LevelDBAggregationRepository` by calling `repo.setSerializer(new JacksonLevelDBSerializer());`
Jackson serializer has limitation towards binary content. If payload object contains binary data (does not concern payloads which are completely binary), Jackson serialization and deserialization won't work correctly.
-To avoid this, define your own jackson serializer/deserealizer via `Module` and provide it to the aggragation repository
+To avoid this, define your own jackson serializer/deserializer via `Module` and provide it to the aggregation repository
(you can use for example the constructor of `QuarkusLevelDBAggregationRepository`).
diff --git a/docs/modules/ROOT/pages/user-guide/configuration.adoc b/docs/modules/ROOT/pages/user-guide/configuration.adoc
index 48e02b33f4..e5c2b9fbef 100644
--- a/docs/modules/ROOT/pages/user-guide/configuration.adoc
+++ b/docs/modules/ROOT/pages/user-guide/configuration.adoc
@@ -117,7 +117,7 @@ public class Configurations {
In addition to support configuring Camel through properties, `camel-quarkus-core` allows you to use conventions to configure the Camel behavior.
For example, if there is a single `ExchangeFormatter` instance in the CDI container, then it will automatically wire that bean to the `LogComponent`.
-Component options for which this is supported are maked as _Autowired_ on their documentation pages
+Component options for which this is supported are marked as _Autowired_ on their documentation pages
- see e.g. the `exchangeFormatter` option on the xref:{cq-camel-components}::log-component.adoc#_component_option_exchangeFormatter[Log component] page.
You can pass `autowiredEnabled=false` to disable it.
diff --git a/docs/modules/ROOT/pages/user-guide/defining-camel-routes.adoc b/docs/modules/ROOT/pages/user-guide/defining-camel-routes.adoc
index fc5b912228..8a16ee8791 100644
--- a/docs/modules/ROOT/pages/user-guide/defining-camel-routes.adoc
+++ b/docs/modules/ROOT/pages/user-guide/defining-camel-routes.adoc
@@ -6,7 +6,7 @@ Camel Quarkus supports several domain specific languages (DSLs) to define Camel
Extending `org.apache.camel.builder.RouteBuilder` and using the fluent builder methods available there
is the most common way of defining Camel Routes.
-Here is an example from the https://github.com/apache/camel-quarkus-examples/tree/main/timer-log[timer-log] quicksstart:
+Here is an example from the https://github.com/apache/camel-quarkus-examples/tree/main/timer-log[timer-log] quickstart:
[source,java]
----
diff --git a/docs/modules/ROOT/pages/user-guide/native-mode.adoc b/docs/modules/ROOT/pages/user-guide/native-mode.adoc
index 0d0f50795d..4c0bda1a19 100644
--- a/docs/modules/ROOT/pages/user-guide/native-mode.adoc
+++ b/docs/modules/ROOT/pages/user-guide/native-mode.adoc
@@ -22,7 +22,7 @@ See also https://quarkus.io/guides/all-config#quarkus-core_quarkus.native.add-al
== Locale
By default, only the building JVM default locale is included in the native image.
-Quarkus provides a way to set the locale via `application.properties`, so that you do not need to rely on `LANG` and `LC_*` environement variables:
+Quarkus provides a way to set the locale via `application.properties`, so that you do not need to rely on `LANG` and `LC_*` environment variables:
[source,properties]
----
diff --git a/extensions/leveldb/runtime/src/main/doc/limitations.adoc b/extensions/leveldb/runtime/src/main/doc/limitations.adoc
index 9b74c9980a..2c29c2b025 100644
--- a/extensions/leveldb/runtime/src/main/doc/limitations.adoc
+++ b/extensions/leveldb/runtime/src/main/doc/limitations.adoc
@@ -2,13 +2,13 @@ In native mode the extension uses a port of LevelDB written in Java (https://git
which is within 10% of the performance of the C++ original. Please upvote https://github.com/apache/camel-quarkus/issues/1911[this issue]
if you do not like the present state.
-Serialization is https://github.com/oracle/graal/issues/460[not supported] on GraalVM. Extension has to use serializationization based
+Serialization is https://github.com/oracle/graal/issues/460[not supported] on GraalVM. Extension has to use serialization based
on Jackson. Aggregation repository in native has to be constructed in one of the following ways:
* Use class `QuarkusLevelDBAggregationRepository` instead of `LevelDBAggregationRepository`.
* Configure jackson serializer on `LevelDBAggregationRepository` by calling `repo.setSerializer(new JacksonLevelDBSerializer());`
Jackson serializer has limitation towards binary content. If payload object contains binary data (does not concern payloads which are completely binary), Jackson serialization and deserialization won't work correctly.
-To avoid this, define your own jackson serializer/deserealizer via `Module` and provide it to the aggragation repository
+To avoid this, define your own jackson serializer/deserializer via `Module` and provide it to the aggregation repository
(you can use for example the constructor of `QuarkusLevelDBAggregationRepository`).