[camel] branch main updated: Polished

[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 84d313feb1c Polished
84d313feb1c is described below

commit 84d313feb1c9c7966ae41b4dcc5d0fde40a6d278
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Wed Apr 26 09:41:48 2023 +0200

    Polished
---
 docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
index 270cc60e83b..ab47d1a2c58 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
@@ -253,10 +253,12 @@ Now the context-path is not in use, and the endpoint can be called with `http://
 NOTE: The `platform-http-starter` can also be used with Rest DSL.
 
 == camel-optaplanner
+
 The `camel-optaplanner` component has been change to use `SolverManager`. If you were using `SoverManager` in Camel 3, you don't need anymore the boolean useSolverManager in the Route.
 Deprecated `ProblemFactChange` has been replaced by `ProblemChange`.
 
-The new URI path is :
+The new URI path is:
+
 [source,java]
 ----
 from("optaplanner:myProblemName")
@@ -264,12 +266,14 @@ from("optaplanner:myProblemName")
 ----
 
 You can pass the Optaplanner SolverManager in 2 ways:
+
 - as #parameter
 - as header
 
-When running `camel-optaplanner` on Spring Boot or Quarkus, it is preferrable to use the Spring Boot or Quarkus way of creating the SolverManager.
+When running `camel-optaplanner` on Spring Boot or Quarkus, it is preferable to use the Spring Boot or Quarkus way of creating the SolverManager.
 
 It is possible to migrate legacy Camel Optaplanner Routes, by putting the XML config file, as show in the code below. Camel Optaplanner will handle creating the SolverManager for those legacy Routes:
+
 [source,java]
 ----
 from("optaplanner:myProblemName?configFile=PATH/TO/CONFIG.FILE.xml")