(camel) 07/12: CAMEL-21040: fixed grammar, typos and other issues in the CamelContext autoconfigure documentation

[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 73bde1b2064491ce47d51976d67c053e0fdd6df6
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Sep 4 08:09:08 2024 +0200

    CAMEL-21040: fixed grammar, typos and other issues in the CamelContext autoconfigure documentation
---
 .../ROOT/pages/camelcontext-autoconfigure.adoc     | 29 +++++++++++-----------
 1 file changed, 15 insertions(+), 14 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camelcontext-autoconfigure.adoc b/docs/user-manual/modules/ROOT/pages/camelcontext-autoconfigure.adoc
index fda3c23f943..f74835369c1 100644
--- a/docs/user-manual/modules/ROOT/pages/camelcontext-autoconfigure.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camelcontext-autoconfigure.adoc
@@ -3,44 +3,45 @@
 The xref:camelcontext.adoc[CamelContext] is autoconfigured when running Camel with either
 xref:components:others:main.adoc[Camel Main], Camel Spring Boot, Camel Quarkus, or Camel K.
 
-== Camel Auto Configuration
+== Camel Autoconfiguration
 
-Under these runtimes then the auto configuration is performed by shared code from the `camel-main` JAR
+Under these runtimes then the autoconfiguration is performed by shared code from the `camel-main` JAR
 to ensure the configuration is similar on these runtimes.
 
-The auto configuration is executed in several steps:
+The autoconfiguration is executed in several steps:
 
 1. Configure `CamelContext` (and more such as components) from xref:components::properties-component.adoc[properties] from external sources like `application.properties|yaml`
-2. Configure optional services that has been registering in the xref:registry.adoc[Registry]
+2. Configure optional services that have been registered in the xref:registry.adoc[Registry]
 
-=== Auto configuration of Properties
+=== Autoconfiguration of Properties
 
-This is used for configuring the standard set of options (more than 100 options) which is listed in the _Camel Main Options_ table at xref:components:others:main.adoc[Camel Main].
+This is used for configuring the standard set of more than 100 options which are listed in the _Camel Main Options_ table at xref:components:others:main.adoc[Camel Main].
 
-NOTE: When using Camel on Spring Boot then these options are prefixed with `camel.springboot`, and not `camel.main`.
+NOTE: When using Camel on Spring Boot, then these options are prefixed with `camel.springboot`, and not `camel.main`.
 
-=== Auto configuration of Optional Services
+=== Autoconfiguration of Optional Services
 
 After configuring the standard options, then Camel will look in the xref:registry.adoc[Registry] for custom
-services to be used. For example to plugin a custom `UnitOfWorkFactory`.
+services to be used.
+For example, to plug in a custom `UnitOfWorkFactory`.
 
 The services can be anything that can be plugged into Camel (typically services that implement an SPI interface `org.apache.camel.spi`).
 
-The following SPI services, can only a single instance (singleton) be in the xref:registry.adoc[Registry].
+The following SPI services can only a single instance (singleton) be in the xref:registry.adoc[Registry].
 
 [width="100%",cols="2m,8",options="header",]
 |=======================================================================
 |SPI |Description
 | AsyncProcessorAwaitManager | To use a custom async processor await manager
 | BacklogTracer | To use a custom backlog tracer
-| ClassResolver | To use a custom class resolver (only needed if you run Camel on a special application server to deal with classloading)
+| ClassResolver | To use a custom class resolver. This is only necessary if you run Camel on a special application server to deal with classloading.
 | Debugger | To use a custom xref:debugger.adoc[debugger]
 | EventFactory | To use a custom event notifier factory
 | ExchangeFactory | To use a custom xref:exchange-pooling.adoc[exchange factory]
 | ExecutorServiceManager | To use a custom xref:threading-model.adoc[thread pool manager]
-| FactoryFinderResolver | To use a custom factory finder resolver (only needed if you run Camel on a special application server to deal with classloading)
+| FactoryFinderResolver | To use a custom factory finder resolver. This is only necessary if you run Camel on a special application server to deal with classloading.
 | HealthCheckRegistry | To use a custom xref:health-check.adoc[health check registry]
-| InflightRepository | To use a custom inflight repository
+| InflightRepository | To use a custom in flight repository
 | ManagementObjectNameStrategy | To use a custom JMX MBean object naming
 | ManagementStrategy | To use a custom JMX management strategy
 | MessageHistoryFactory | To use a custom factory for xref:components:eips:message-history.adoc[message history]
@@ -58,7 +59,7 @@ The following SPI services, can only a single instance (singleton) be in the xre
 | UuidGenerator | To use a custom xref:uuidgenerator.adoc[uuid generator]
 |=======================================================================
 
-For the following SPI services, there can be multiple (1..n) implementations in the xref:registry.adoc[Registry].
+For the following SPI services, there can be multiple (one or more) implementations in the xref:registry.adoc[Registry].
 
 [width="100%",cols="2m,8",options="header",]
 |=======================================================================