CAMEL-16861: Update docs

Author: davsclaus

docs/user-manual/modules/ROOT/pages/getting-started.adoc

@@ -13,7 +13,6 @@ And some more alternative methods:
 - Using Maven Archetypes
 - Cloning an existing example to modify
 
-
 == Using online Project generators
 
 You can use https://start.spring.io/[Spring Boot Initializer] which is the Spring Boot
@@ -36,7 +35,7 @@ Once JBang is installed, you should be able to make sure it works by calling the
 [source,bash]
 ----
 $ jbang version
-0.132.1
+0.137.0
 ----
 
 After this then install Camel into JBang as follows:
@@ -51,8 +50,8 @@ Then you can check that Camel is installed and working by executing:
 [source,bash]
 ----
 $ camel version
-JBang version: 0.132.1
-Camel JBang version: 4.16.0
+JBang version: 0.137.0
+Camel JBang version: 4.18.0
 ----
 
 *Step 2*
@@ -96,6 +95,7 @@ Make sure to check out the xref:camel-jbang.adoc[Camel JBang] documentation, for
 of the Camel CLI. You will also find information how you can _export_ what you have built
 with the Camel CLI into a vanilla Camel Spring Boot or Camel Quarkus project.
 
+
 == Alternative ways of getting started with Camel
 
 === Adding Camel to an existing project
@@ -118,6 +118,8 @@ Among others the following are open source and provide support for official Apac
 - https://github.com/apache/camel-karavan[Apache Camel Karavan] - Has an https://karavan.space/[online UI designer] that runs in a web browser.
 - https://kaoto.io/[Kaoto] - Has also an https://kaotoio.github.io/kaoto/[online UI designer] that runs in a web browser.
 
+Both Camel Karavan and Kaoto can be installed as Visual Studio plugins directly in this IDE.
+
 === Using Maven Archetypes
 
 Apache Camel comes with a set of xref:camel-maven-archetypes.adoc[Camel Maven Archetypes],
@@ -128,3 +130,8 @@ you can use to create a new Camel project.
 There are tons of Camel examples hosted on GitHub that you can clone and modify,
 such as https://github.com/apache/camel-spring-boot-examples[Camel Spring Boot examples].
 
+== See Also
+
+To get familiar and learn the basic concepts of Apache Camel, then its recommend to check out xref:architecture.adoc[Architecture]
+and follow the links from that page.
+

docs/user-manual/modules/ROOT/pages/graceful-shutdown.adoc

@@ -1,9 +1,9 @@
 = Graceful Shutdown
 
 Camel supports a pluggable shutdown strategy using
-`org.apache.camel.spi.ShutdownStrategy`. Its responsible for shutting
+`org.apache.camel.spi.ShutdownStrategy`. It's responsible for shutting
 down routes in a graceful manner. The other resources will still be
-handled by xref:camelcontext.adoc[CamelContext] to shutdown. This leaves
+handled by xref:camelcontext.adoc[CamelContext] to shut down. This leaves
 the problem at hand with properly shutting down all the routes reliably
 to the `ShutdownStrategy`.
 
@@ -13,12 +13,11 @@ doing that.
 
 == Default Shutdown Strategy
 
-The default strategy (`DefaultShutdownStrategy`) will gracefully shutdown routes:
+The default strategy (`DefaultShutdownStrategy`) will gracefully shut down routes:
 
 * in the reverse order they were started
-* let pending and current in flight exchanges run to completion before
-shutting down
-* using a timeout of 45 seconds which then forces a _hard_ shutdown
+* let pending and current in flight exchanges run to completion before shutting down
+* using a timeout of 45 seconds (can be configured) which then forces a _hard_ shutdown
 
 The settings are configurable, so you can change the timeout, and
 whether in case of timeout to force a _hard_ shutdown or ignore.
@@ -40,24 +39,40 @@ When shutting down the strategy will output to log the progress:
 ---------------------------------
 
 Notice how the strategy waits while there are inflight exchanges still being
-processed before it shutdown the routes and after that Camel itself.
+processed before it shut down the routes and after that Camel itself.
 
 === Suppressing logging due to timeout not allowing all inflight messages to complete
 
 If a graceful shutdown could not shutdown cleanly within the given
 timeout period, then Camel performs a more aggressive shutdown (hard) by
 forcing routes and thread pools etc to shut down, and the routing
-engine will reject continue processing xref:exchange.adoc[Exchange]s. If
-this happens you may see WARN logs about xref:exchange.adoc[Exchange]s
+engine will reject continue processing xref:exchange.adoc[Exchange](s). If
+this happens you may see WARN logs about xref:exchange.adoc[Exchange](s)
 being rejected and other failures due the forced shutdown.
 
 If you do not want to see these logs, you can suppress this by setting
-the option suppressLoggingOnTimeout to true.
+the option `suppressLoggingOnTimeout` to true.
 
+
+[tabs]
+====
+
+Java::
++
 [source,java]
----------------------------------
+----
 context.getShutdownStrategy().setSuppressLoggingOnTimeout(true);
----------------------------------
+----
+
+Application Properties::
++
+Or in `application.properties`:
++
+[source,properties]
+----
+camel.main.shutdownSuppressLoggingOnTimeout = true
+----
+====
 
 Notice that suppression is _a best effort_ attempt and there may still be some
 logging from 3rd party libraries, which Camel cannot control.
@@ -66,7 +81,7 @@ logging from 3rd party libraries, which Camel cannot control.
 
 If a graceful shutdown could not shutdown cleanly within the given
 timeout period, then Camel performs a more aggressive shutdown by
-forcing routes and thread pools etc to shut down. When the timeout
+forcing routes and thread pools etc. to shut down. When the timeout
 happens, then Camel logs information about the current inflight
 exchanges, which shows from which route the exchange origins, and where
 it currently is being routed. For example the logging below, shows that
@@ -91,11 +106,26 @@ duration=2017]
 If you do not want to see these logs, you can turn this off by setting
 the option logInflightExchangesOnTimeout to false.
 
+[tabs]
+====
+
+Java::
++
 [source,java]
 ---------------------------------
 context.getShutdownStrategy().setLogInflightExchangesOnTimeout(false);
 ---------------------------------
 
+Application Properties::
++
+Or in `application.properties`:
++
+[source,properties]
+----
+camel.main.logInflightExchangesOnTimeout = false
+----
+====
+
 === JMX managed
 
 The `ShutdownStrategy` is JMX aware, so you can manage it from a
@@ -161,7 +191,7 @@ It is possible to stop (will do a gracefully shut down) an individual route usin
 camelContext.getRouteController().stopRoute(routeId);
 ----
 
-Routes can also be stopped via JMX.
+TIP: Routes can also be stopped via JMX or external tools such as https://hawt.io/[Hawtio].
 
 === Stopping and marking routes as failed due to an exception
 
@@ -180,7 +210,7 @@ NOTE: The Camel xref:health-check.adoc[Health Check] detect the route as failed
 If the route is manually stopped, then the route is not marked as failed,
 and the xref:health-check.adoc[Health Check] will report the status as UNKNOWN.
 
-Routes can also be stopped and failed via JMX.
+TIP: Routes can also be stopped and failed via JMX or external tools such as https://hawt.io/[Hawtio].
 
 == Implementing custom component or ShutdownStrategy
 
@@ -196,7 +226,7 @@ on the `CamelContext` using the `setShutdownStrategy` method.
 === ShutdownAware
 
 The interface `org.apache.camel.spi.ShutdownAware` is an optional
-interface consumers can implement to have fine grained control during
+interface consumers can implement to have fine-grained control during
 shutdown. The `ShutdownStrategy` must be able to deal with consumers
 which implement this interface. This interface was introduced to cater
 for in memory consumers such as xref:components::seda-component.adoc[SEDA] which potentially