[camel-k] branch main updated: fix(doc): broken links

[pc...@apache.org]

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

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


The following commit(s) were added to refs/heads/main by this push:
     new 4c81cd1  fix(doc): broken links
4c81cd1 is described below

commit 4c81cd125ade437effbadb3e1dc43f6b71602c1a
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu Nov 25 09:45:52 2021 +0100

    fix(doc): broken links
---
 docs/modules/ROOT/nav.adoc                             |  2 +-
 docs/modules/ROOT/pages/installation/installation.adoc | 18 +++++++++---------
 docs/modules/ROOT/pages/installation/registry/gcr.adoc |  2 +-
 .../ROOT/pages/installation/registry/registry.adoc     |  2 +-
 4 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
index 172642a..5bc1a65 100644
--- a/docs/modules/ROOT/nav.adoc
+++ b/docs/modules/ROOT/nav.adoc
@@ -17,7 +17,7 @@
 *** xref:installation/registry/k3s.adoc[K3s]
 ** Advanced
 *** xref:installation/advanced/resources.adoc[Resource management]
-*** xref:architecture/advanced/multi.adoc[Multiple Operators]
+*** xref:installation/advanced/multi.adoc[Multiple Operators]
 * Command Line Interface
 ** xref:cli/cli.adoc[Kamel CLI]
 ** xref:cli/modeline.adoc[Modeline]
diff --git a/docs/modules/ROOT/pages/installation/installation.adoc b/docs/modules/ROOT/pages/installation/installation.adoc
index e033ed5..672e023 100644
--- a/docs/modules/ROOT/pages/installation/installation.adoc
+++ b/docs/modules/ROOT/pages/installation/installation.adoc
@@ -10,17 +10,17 @@ To use it, you need to be connected to a cloud environment or to a local cluster
 Camel K installation is usually straightforward, but for certain cluster types you need to apply specific configuration settings
 before installing it. Customized instructions are needed for the following cluster types:
 
-- xref:installation/minikube.adoc[Minikube]
-- xref:installation/crc.adoc[Red Hat CodeReady Containers (CRC)]
-- xref:installation/gke.adoc[Google Kubernetes Engine (GKE)]
-- xref:installation/openshift.adoc[OpenShift]
-- xref:installation/iks.adoc[IBM Kubernetes Services (IKS)]
-- xref:installation/k3s.adoc[K3s]
-- xref:installation/kind.adoc[Kind]
+- xref:installation/platform/minikube.adoc[Minikube]
+- xref:installation/platform/crc.adoc[Red Hat CodeReady Containers (CRC)]
+- xref:installation/platform/gke.adoc[Google Kubernetes Engine (GKE)]
+- xref:installation/platform/openshift.adoc[OpenShift]
+- xref:installation/platform/iks.adoc[IBM Kubernetes Services (IKS)]
+- xref:installation/platform/k3s.adoc[K3s]
+- xref:installation/platform/kind.adoc[Kind]
 
 Other cluster types (such as OpenShift clusters) should *not need* prior configuration.
 
-NOTE: Minishift is no longer supported since Camel K 1.5.0. You can use xref:installation/crc.adoc[CRC] for a local OpenShift cluster.
+NOTE: Minishift is no longer supported since Camel K 1.5.0. You can use xref:installation/platform/crc.adoc[CRC] for a local OpenShift cluster.
 
 [[procedure]]
 == Procedure
@@ -31,7 +31,7 @@ Look into the https://github.com/apache/camel-k/releases[release page] for the l
 Download and uncompress the archive. It contains a small binary file named `kamel` that you should put into your system path.
 For example, if you're using Linux, you can put `kamel` in `/usr/bin`.
 
-Once you have put the "kamel" CLI in the path, log into your cluster using the standard "oc" (OpenShift) or "kubectl" (Kubernetes) client tool and execute the following command to install Camel K:
+Once you have put the `kamel` CLI in the path, log into your cluster using the standard `oc` (OpenShift) or `kubectl` (Kubernetes) client tool and execute the following command to install Camel K:
 
 [source]
 ----
diff --git a/docs/modules/ROOT/pages/installation/registry/gcr.adoc b/docs/modules/ROOT/pages/installation/registry/gcr.adoc
index 5c6f289..bc6cdfb 100644
--- a/docs/modules/ROOT/pages/installation/registry/gcr.adoc
+++ b/docs/modules/ROOT/pages/installation/registry/gcr.adoc
@@ -1,7 +1,7 @@
 [[configuring-registry-gcr]]
 = Configuring a Gcr.io Registry
 
-You can use gcr.io as registry to host Camel K images. Usually, users may want to use gcr.io in combination with xref:installation/gke.adoc[Google GKE].
+You can use gcr.io as registry to host Camel K images. Usually, users may want to use gcr.io in combination with xref:installation/platform/gke.adoc[Google GKE].
 
 In order to push images to `gcr.io`, you need to provide a valid key to Camel K.
 The best way to obtain a valid key is from the Google web console:
diff --git a/docs/modules/ROOT/pages/installation/registry/registry.adoc b/docs/modules/ROOT/pages/installation/registry/registry.adoc
index 482c9e2..3482c90 100644
--- a/docs/modules/ROOT/pages/installation/registry/registry.adoc
+++ b/docs/modules/ROOT/pages/installation/registry/registry.adoc
@@ -7,7 +7,7 @@ A **default registry** is present in all the following supported installations:
 
 * **OpenShift**: all OpenShift installations (including 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.
-* **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
+* **Minikube**: Minikube comes with a "registry addon" that can be enabled upon installation (see xref:installation/platform/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`).
 
 Other platforms do not provide a default container registry and need to be configured accordingly.