[camel-k] 07/07: Fix #613: Fix doc formatting

[as...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

astefanutti pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git

commit 46fa770ffbdf6a14ea73b789d4f1078d5383aba7
Author: Nicola Ferraro <ni...@gmail.com>
AuthorDate: Wed Nov 27 15:43:53 2019 +0100

    Fix #613: Fix doc formatting
---
 docs/modules/ROOT/pages/installation/registry/registry.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/modules/ROOT/pages/installation/registry/registry.adoc b/docs/modules/ROOT/pages/installation/registry/registry.adoc
index 967dd4a..343656d 100644
--- a/docs/modules/ROOT/pages/installation/registry/registry.adoc
+++ b/docs/modules/ROOT/pages/installation/registry/registry.adoc
@@ -6,9 +6,9 @@ Every Camel K installation needs a container registry that that will be used to
 A **default registry** is present in all the following supported installations:
 
 * **OpenShift**: all OpenShift installations (including Minishift, CRC and real clusters) provide an internal container registry that is used for the S2I (source to image)
-					feature. Camel K is able to leverage that registry.
+  feature. Camel K is able to leverage that registry.
 * **Minikube**: Minikube comes with a "registry addon" that can be enabled upon installation (see xref:installation/minikube.adoc[install guide for Minikube ]). Camel K automatically detects the address of the registry and configures
-					it on the `IntegrationPlatform` when using the CLI (on `kamel install`).
+  it on the `IntegrationPlatform` when using the CLI (on `kamel install`).
 
 Other platforms do not provide a default container registry and need to be configured accordingly.