diff --git a/docs/modules/ROOT/pages/concepts/overview.adoc b/docs/modules/ROOT/pages/concepts/overview.adoc
index 9235230cee..7dadbc2c05 100644
--- a/docs/modules/ROOT/pages/concepts/overview.adoc
+++ b/docs/modules/ROOT/pages/concepts/overview.adoc
@@ -6,7 +6,9 @@ Camel K is a https://kubernetes.io/docs/concepts/extend-kubernetes/operator/[Kub
 
 A Camel workload is generally represented by a route expressed in any Camel DSL. This is wrapped into one or more custom resource which will manage the lifecycle of the application on the cloud.
 
-image::concepts/integrations.png[Camel workload lifecycle, width=1024]
+
+image::concepts/integrations.png[Camel workload lifecycle, width=640]
+
 
 The user is responsible to create a single IntegrationPlatform which contains the configuration required to drive the build and publishing process. Then the user creates any Integration custom resource, which is mainly a container for the Camel route and other optional Kubernetes fine tunings.
 
@@ -24,7 +26,9 @@ The user is responsible to create a single IntegrationPlatform which contains th
 
 The user can use an alternative approach using the Pipe (Connector) abstraction. With Pipe, he can provide a declarative connector-style approach, connecting an **Event Source** to an **Event Sink**. The source and sink can be any Kubernetes object reference that the operator can transform. The operator will be in charge to transform such a Pipe into an Integration and start the build and deployment process as described above.
 
-image::concepts/pipes.png[Camel connector lifecycle, width=1024]
+
+image::concepts/pipes.png[Camel connector lifecycle, width=640]
+
 
 **Pipe**: it is used to create the connector binding an event source to an event sink.
 
diff --git a/docs/modules/ROOT/pages/installation/installation.adoc b/docs/modules/ROOT/pages/installation/installation.adoc
index 3fc5c41b10..ca9e33d78a 100644
--- a/docs/modules/ROOT/pages/installation/installation.adoc
+++ b/docs/modules/ROOT/pages/installation/installation.adoc
@@ -89,14 +89,14 @@ NOTE: a local minikube registry can be enabled via `minikube addons enable regis
 kubectl apply -f itp.yaml -n camel-k
 ```
 
-Wait now for the`IntegrationPlatform` to turn into ready state:
+Wait now for the IntegrationPlatform to turn into ready state:
 
 ```
 $ kubectl wait --for jsonpath='{.status.phase}'=Ready IntegrationPlatform camel-k -n camel-k --timeout 30s
 integrationplatform.camel.apache.org/camel-k condition met
 ```
 
-Your operator is now ready to run some Camel `Integration`.
+Your operator is now ready to run some Camel Integration.
 
 NOTE: a production ready xref:installation/registry/registry.adoc[container registry configuration] may require other parameters and secret management.