[camel] branch master updated: Fix some typos in the Apache Camel 3.x Upgrade Guide

[pa...@apache.org]

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

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new ed1146d  Fix some typos in the Apache Camel 3.x Upgrade Guide
ed1146d is described below

commit ed1146d18895b17e9d41742f48d545fb5b1b93a4
Author: Pascal Schumacher <pa...@gmx.net>
AuthorDate: Tue Mar 31 17:59:36 2020 +0200

    Fix some typos in the Apache Camel 3.x Upgrade Guide
---
 .../user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
index 8fe18fb..08ed256 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
@@ -35,7 +35,7 @@ https://issues.apache.org/jira/browse/CAMEL-13844
 The following `ServiceDiscovery` implementation has been removed: 
 
 * org.apache.camel.impl.cloud.CachingServiceDiscovery
-* org.apache.camel.impl.cloud.CachingServiceDiscoveryFactoyr
+* org.apache.camel.impl.cloud.CachingServiceDiscoveryFactory
 
 https://issues.apache.org/jira/browse/CAMEL-14813
 
@@ -919,7 +919,7 @@ After:
 
 === camel-avro
 
-The avro component and data format has been splitup into two JARs. The dataformat is in `camel-avro` JAR
+The avro component and data format has been split up into two JARs. The dataformat is in `camel-avro` JAR
 and the component in `camel-avro-rpc` JAR.
 
 === camel-infinispan
@@ -1000,7 +1000,7 @@ Endpoint endpoint = camelContext.getEndpoint("myCoolEndpoint");
 The context scope error handling has been modified a bit.  The processors in those `onException` and
 `onCompletion` are not shared between routes anymore.  This should have little effect in most cases.
 If there is a need to have a single set of processors involved (such as when using a loadbalancer or
-other stateful patterns), then an intermediary route needs to be used. The following exerpt:
+other stateful patterns), then an intermediary route needs to be used. The following excerpt:
 
 [source,java]
 ----
@@ -1027,10 +1027,10 @@ out of `camel-core-engine` into separate JAR named `camel-cluster`.
 === Configuring milli seconds
 
 Camel was using a type converter from `String` -> `long` that accepted
-a time pattern which allowed to configure long values such as `2s` for 2 seconds, eg `2000`.
+a time pattern which allowed to configure long values such as `2s` for 2 seconds, e.g. `2000`.
 And more complex such as `8h15m` for 8 hours and 15 minutes.
 
-However as this was implemented as part of `String` -> `long` type convertion
+However as this was implemented as part of `String` -> `long` type conversion
 which then adds a little bit of overhead during routing, when converting from String to plain numbers.
 
 To make Camel routing engine as fast as possible, then this has been removed.