Update 02-architecture.adoc

Author: ibek

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

@@ -29,20 +29,20 @@ As a migration does not bring immediate new business value, it's important that
 * https://www.redhat.com/en/technologies/cloud-computing/openshift[Red Hat OpenShift]
 * Red Hat Application Foundation
 ** https://access.redhat.com/products/quarkus[Quarkus]
-** https://developers.redhat.com/products/redhat-build-of-camel/overview[Red Hat build of Camel]
+** https://developers.redhat.com/products/redhat-build-of-camel/overview[Red Hat build of Apache Camel]
 
 
 [#in_depth]
 == An in-depth look at the solution's architecture
 
-The Red Hat Build of Camel is an Cloud-native, multi-language and a multi-runtime integration stack.
+The Red Hat build of Apache Camel is an Cloud-native, multi-language and a multi-runtime integration stack.
 Camel-based integration logic can be written in XML or Java, and can behave as a Spring Boot, a Quarkus, or a Serverless artifact. 
 
 The present demo will take a legacy API developed in JBoss Fuse 6.2 on Karaf, in Blueprint XML.
 It's suggested that such an application targets the Quarkus runtime.
 The provided Quarkus template is 100% compatible with Camel K, so the resutling migrated application is immediately ready to be added to a serverless stack.
 
-The material can be used to migrate any Fuse 6 or 7 distribution to the Red Hat Build of Apache Camel.
+The material can be used to migrate any Fuse 6 or 7 distribution to the Red Hat build of Apache Camel.
 The demos will however focus on migrating a Fuse 6 application, and more concretely a Camel v2.17 one, in Blueprint XML format, running on Karaf 2. The XML format will be converted to the optimized IO XML one.
 This path has been chosen for the demonstration because it can be considered the hardest one. Applications running on Fuse 7, no matter which distribution, could use the same approach and will bnefit from a shortest migration effort.
 
@@ -78,4 +78,4 @@ The material here consists in ready to use templates that are already perfectly
 The templates are Maven artifacts, preconfigured with all required dependencies, and holding all the needed placeholders to migrate code and configuration in a timely fashion.  
 
 .Templates-based approach
-image:runtimes-1.png[] 
+image:runtimes-1.png[]