[camel] branch main updated: Update route-configuration.adoc (#5919)

[da...@apache.org]

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 ddf3761  Update route-configuration.adoc (#5919)
ddf3761 is described below

commit ddf3761acb07115ce0f1f48c04d99097ed587d1b
Author: klease <38...@users.noreply.github.com>
AuthorDate: Wed Aug 4 06:12:09 2021 +0200

    Update route-configuration.adoc (#5919)
    
    Minor edits for grammar; clarify wildcard use in ids.
---
 .../modules/ROOT/pages/route-configuration.adoc    | 26 +++++++++++-----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/route-configuration.adoc b/docs/user-manual/modules/ROOT/pages/route-configuration.adoc
index f0c5acb..49de5e0 100644
--- a/docs/user-manual/modules/ROOT/pages/route-configuration.adoc
+++ b/docs/user-manual/modules/ROOT/pages/route-configuration.adoc
@@ -9,7 +9,7 @@ to copy the same configuration to a set of routes or rely on global error handli
 Now you can configure a number of route configurations, and then specify on each route
 which configuration to use (you can use match by ids, wildcards, and regular expression).
 
-The route configuration is supported by all DSL's, so useable by: Java, XML, Groovy, XML, Kotlin and so forth.
+The route configuration is supported by all DSL's, so useable by: Java, XML, Groovy, Kotlin and so forth.
 
 In the route configuration you can setup common strategies for:
 
@@ -21,7 +21,7 @@ In the route configuration you can setup common strategies for:
 == Route Configuration Builder in Java DSL
 
 With Java DSL you can use `RouteConfigurationBuilder` to specify the configuration as shown below.
-The builder is similar to `RouteBuilder` so its familiar how to use.
+The builder is similar to `RouteBuilder` so it's use is familiar.
 
 [source,java]
 ----
@@ -37,7 +37,7 @@ public class MyJavaErrorHandler extends RouteConfigurationBuilder {
 ----
 
 NOTE: The `RouteConfigurationBuilder` uses `configuration` as the method where the configuration is coded.
-This is on purpose to not use the `configure` method which the regular Java DSL `RouteBuilder`
+This is on purpose not to use the `configure` method which the regular Java DSL `RouteBuilder`
 uses for coding Camel routes.
 
 In the example above, then there is only one route configuration which has been assigned the ID _javaError_.
@@ -85,7 +85,7 @@ The route configurations supports matching by:
 - match by wildcard
 - match by regular expression.
 
-Wildcards is match that the text before the * is matched against the given configuration and if it also starts with the same characters its a match. For instance you can do:
+Wildcards are text ending with a *; they are matched when the configuration ID starts with the specified text followed by any characters. For instance you can do:
 
 [source,java]
 ----
@@ -118,7 +118,7 @@ context.addRoutes(new MyJavaRouteBuilder());
 ----
 
 If you use Spring Boot, then your Camel routes and route configurations can be auto-discovered
-by the spring boot component scanning. This requires to add `@Component` annotation to the class.
+by the spring boot component scanning. This requires adding the `@Component` annotation to the class.
 
 See the example https://github.com/apache/camel-spring-boot-examples/tree/main/routes-configuration[camel-example-spring-boot-routes-configuration].
 
@@ -126,7 +126,7 @@ See the example https://github.com/apache/camel-spring-boot-examples/tree/main/r
 === Route configuration with Endpoint DSL
 
 The xref:Endpoint-dsl.adoc[Endpoint DSL] can also be used for route configurations.
-This requires to add `camel-endpointdsl` to the classpath, and then use
+This requires adding `camel-endpointdsl` to the classpath, and then using
 `org.apache.camel.builder.endpoint.EndpointRouteConfigurationBuilder`,
 which offers the _type safe_ DSL for Camel endpoints.
 
@@ -134,8 +134,8 @@ which offers the _type safe_ DSL for Camel endpoints.
 == Default route configurations
 
 Route configurations are either given an explicit unique ID, or the configuration is _nameless_.
-A _nameless_ configuration is used as default/fallback configuration, for routes which has *NOT*
-been explicit assigned route configurations.
+A _nameless_ configuration is used as default/fallback configuration, for routes which have *NOT*
+been explicitly assigned route configurations.
 
 Suppose you have one _nameless_ configuration and another named _javaError_:
 
@@ -155,7 +155,7 @@ public class MyJavaErrorHandler extends RouteConfigurationBuilder {
 }
 ----
 
-And the follow two routes:
+And the following two routes:
 
 [source,java]
 ----
@@ -167,10 +167,10 @@ And the follow two routes:
         .to("jms:beer");
 ----
 
-In the example above, then the _cheese_ route has no route configurations assigned, so the route
+In the example above, the _cheese_ route has no route configurations assigned, so the route
 will use the default configuration, which in case of an exception will log a warning.
 
-The _beer_ route on the other hand have route configuration _retryError_ assigned, and this
+The _beer_ route on the other hand has route configuration _retryError_ assigned, and this
 configuration will in case of an exception retry again up till 5 times and then if still an error
 then fail and rollback.
 
@@ -250,7 +250,7 @@ In this example the route is assigned the _yamlError_ route configuration by the
 
 == Mixing DSLs
 
-Routes and route configuration is not requires to use the same language. For example you can code
+Routes and route configuration are not required to use the same language. For example you can code
 route configurations in Java, and then use XML DSL for the routes, and they would work together.
 
 == Packaging route configurations in reusable JARs
@@ -262,7 +262,7 @@ This allows for example to use a _common practice_ among your Camel applications
 
 == Logging Summary
 
-If you set `startup-summary-level=verbose` then Camel will log on for each route which route configurations they have been assigned.
+If you set `startup-summary-level=verbose` then Camel will log for each route which route configurations they have been assigned.
 
 This option can be configured via Java API and also in `application.properties` for Camel on Spring Boot, Quarkus, and Camel standalone via `camel-main`