typos

Author: jayachristina

documentation/modules/ROOT/nav.adoc

@@ -1,7 +1,6 @@
 * xref:index.adoc[{counter:module}. Home page]
 ** xref:index.adoc#use-cases[{module}.{counter:submodule1} Use cases]
-** xref:index.adoc#_the_story_behind_this_solution_pattern[{module}.{counter:submodule1} The story behind this solution pattern]
-** xref:index-pattern#_the_solution[{module}.{counter:submodule1} The solution]
+** xref:index.adoc#_the_solution[{module}.{counter:submodule1} The solution]
 
 * xref:02-architecture.adoc[{counter:module}. Architecture]
 ** xref:02-architecture.adoc#tech_stack[{module}.{counter:submodule2}. Technology stack]

documentation/modules/ROOT/pages/02-architecture.adoc

@@ -5,7 +5,7 @@
 
 = Architecture 
 
-The solution pattern leverages preconfigured, ready-to-use Quarkus and Springboot templates.
+The solution pattern leverages preconfigured, ready-to-use Quarkus and Spring Boot templates.
 Those templates contains placeholders where code and configration just need to be copy-pasted from the legacy application.
 
 
@@ -55,13 +55,13 @@ In general, the following migration strategy should be considered:
 
 * *Runtime*
 
-** If you are already on Fuse 7 springboot, migrate toward springboot
+** If you are already on Fuse 7 Spring Boot, migrate toward Spring Boot
 ** In any other cases, you could target Quarkus
 
 * *Target*
 
 Probably, the target should remain a "standard" container application, ready for Serverless but not mandatorily a Function. +
-Thus, the demos will showcase several migrations to "plain" springboot or quarkus applications, and there will be one extra demo to showcase a migration from that result to Camel K.  
+Thus, the demos will showcase several migrations to "plain" Spring Boot or quarkus applications, and there will be one extra demo to showcase a migration from that result to Camel K.  
 
 
 [#more_tech]

documentation/modules/ROOT/pages/03-demo.adoc

@@ -12,7 +12,7 @@
 
 You can see a migration based on the templates in action here.
 
-* https://drive.google.com/file/d/11CBxNI_2QI77uFeD7Dxqf32uDnAt9cKX/view?usp=drive_link[Migration toward Camel for Springboot and Camel extension for Quarkus^]
+* https://drive.google.com/file/d/11CBxNI_2QI77uFeD7Dxqf32uDnAt9cKX/view?usp=drive_link[Migration toward Camel for Spring Boot and Camel extension for Quarkus^]
 * https://drive.google.com/file/d/1DqTrlydgvJiKTe7y6oxuvY8K-SAve9xc/view?usp=drive_link[Running the migrated application on Openshift^]
 * https://drive.google.com/file/d/11CBxNI_2QI77uFeD7Dxqf32uDnAt9cKX/view?usp=drive_link[Running the migrated application as a Camel K serverless function^]
 
@@ -29,7 +29,7 @@ image:repo-branch.png[width=60%]
 * The "templates" directory itself contains multiple subdirectories. +
 * The breakdown is done on a per-component and per-runtime basis. +
 
-So, there is a subdirectory for each of the most used Camel components (REST API, SOAP, JMS...) further divided per runtime (Quarkus and Springboot).  
+So, there is a subdirectory for each of the most used Camel components (REST API, SOAP, JMS...) further divided per runtime (Quarkus and Spring Boot).  
 
 
 image:repo-templates.png[] 

documentation/modules/ROOT/pages/index.adoc

@@ -23,7 +23,7 @@ Contributors: _Michael Thirion (Red Hat)_
 Common use cases that can be address with this solution are:
 
 - Migrate Fuse 6.x (Blueprint XML, Spring XML or Java) applications to the Red Hat Build of Camel, targeting either Springoot 3, Quarkus or the Camel K Serverless runtime.
-- Migrate Fuse 7 (Karaf or Springboot) applications to the Red Hat Build of Camel, targeting either Springboot 3, Quarkus or the Camel K Serverless runtime.
+- Migrate Fuse 7 (Karaf or Spring Boot) applications to the Red Hat Build of Camel, targeting either Spring Boot 3, Quarkus or the Camel K Serverless runtime.
 - Start writing Camel 3.x or 4.x applications right away with no effort