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
commit a0e31ada337977775eb2458f1571f4d7af327911 Author: Claus Ibsen <[email protected]> AuthorDate: Thu Aug 19 13:08:31 2021 +0200 Polish and cleanup documentation --- docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc b/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc index b54fdd1..abf48a5 100644 --- a/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc +++ b/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc @@ -4,7 +4,7 @@ Camel provides pluggable class resolvers allowing third party platforms and containers to provide their own resolvers in case the default ones would not fit. -When running Camel on platforms such as Spring Boot, Quarkus, or OSGi on Apache Karaf, +When running Camel on platforms such as Spring Boot, Quarkus, or Apache Karaf, then Camel uses platform specific resolvers to support classloading in these runtimes. == Configuration of a custom class resolver @@ -12,7 +12,7 @@ then Camel uses platform specific resolvers to support classloading in these run To instruct Camel to use your own custom class resolver, you set the resolver on the `CamelContext` using the appropriate setters; or register a custom resolver in the xref:registry.adoc[Registry] then Camel -will automatic detect this during startup. +will automatically detect this during startup. === SPI providers
