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

[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 876bfb05e fix(doc): link
876bfb05e is described below

commit 876bfb05e06df2daef40fbed34b0dca12e99d021
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Fri Jul 14 11:28:16 2023 +0200

    fix(doc): link
---
 docs/modules/ROOT/pages/running/runtime-version.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/running/runtime-version.adoc b/docs/modules/ROOT/pages/running/runtime-version.adoc
index 71f7f5542..09e9120e1 100644
--- a/docs/modules/ROOT/pages/running/runtime-version.adoc
+++ b/docs/modules/ROOT/pages/running/runtime-version.adoc
@@ -12,4 +12,4 @@ Having the ability to choose the runtime, gives you the ability to specify which
 
 == Pin a runtime version
 
-By default each Camel K version uses a specific runtime version, ie, Camel K 2.0 uses Camel K Runtime 2.16.0. Using the trait will let you pin to a well defined version, avoiding to unintentionally upgrade the runtime of the integrations running when you perform an operator upgrade. See more info in the xref:contributing/upgrade.adoc##maintain-runtime-integrations[Camel K upgrade documentation].
\ No newline at end of file
+By default each Camel K version uses a specific runtime version, ie, Camel K 2.0 uses Camel K Runtime 2.16.0. Using the trait will let you pin to a well defined version, avoiding to unintentionally upgrade the runtime of the integrations running when you perform an operator upgrade. See more info in the xref:contributing/upgrade.adoc#maintain-runtime-integrations[Camel K upgrade documentation].