[camel-k] branch main updated: fix(doc): correct xref path

[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 63cecc2ba fix(doc): correct xref path
63cecc2ba is described below

commit 63cecc2ba6290f1aa9b9626e664764db5f4cceab
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Wed Jun 28 11:33:22 2023 +0200

    fix(doc): correct xref path
---
 docs/modules/ROOT/pages/installation/advanced/maven.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/installation/advanced/maven.adoc b/docs/modules/ROOT/pages/installation/advanced/maven.adoc
index 4cdf74883..334e1b2e3 100644
--- a/docs/modules/ROOT/pages/installation/advanced/maven.adoc
+++ b/docs/modules/ROOT/pages/installation/advanced/maven.adoc
@@ -7,7 +7,7 @@ Camel K builds are performed by Maven. For this reason it may requires certain M
 
 The first best practice we suggest is to provide a https://maven.apache.org/repository-management.html[Maven Repository Manager] that acts as an intermediary between the cluster and the various artifacts repositories that may be required by Camel K.
 
-If your company has already one available in the cluster, you should use it. If not, we suggest you to take the opportunity and xref:maven-proxy.adoc[run a Maven proxy beside your Camel K operator]. There are many benefits by introducing a proxy, above all the reduction in the time required to download dependencies (which are cached in the proxy) and inherently the egress bandwidth cost saving.
+If your company has already one available in the cluster, you should use it. If not, we suggest you to take the opportunity and xref:installation/advanced/maven-proxy.adoc[run a Maven proxy beside your Camel K operator]. There are many benefits by introducing a proxy, above all the reduction in the time required to download dependencies (which are cached in the proxy) and inherently the egress bandwidth cost saving.
 
 You can create a `settings.xml` file as illustred below: