[camel-website] 02/02: fix: multi 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-website.git

commit df5e6729c441096d9178100cc918ee12a3e9fd8a
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Tue Sep 6 16:34:19 2022 +0200

    fix: multi link
---
 content/blog/2022/09/camel-k-release-1-10/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2022/09/camel-k-release-1-10/index.md b/content/blog/2022/09/camel-k-release-1-10/index.md
index 5ff97aaa..a0ac078e 100644
--- a/content/blog/2022/09/camel-k-release-1-10/index.md
+++ b/content/blog/2022/09/camel-k-release-1-10/index.md
@@ -59,7 +59,7 @@ While doing some stress tests, we've noticed that there were a high number of un
 
 ## Multi operator handling and multi tenancy model
 
-Another big effort that required some heavy refactoring. Before version 1.10, there was no way to have more than one operator running at the same time. We had provided some development to partially allow [multiple operators](camel-k/1.10.x/installation/advanced/multi.html). Within this release, we're freeing the Camel K operator to be bound to a namespace, letting the Integrations (and the rest of CRDs) to declare which is the operator in charge of reconciling.
+Another big effort that required some heavy refactoring. Before version 1.10, there was no way to have more than one operator running at the same time. We had provided some development to partially allow [multiple operators](/camel-k/1.10.x/installation/advanced/multi.html). Within this release, we're freeing the Camel K operator to be bound to a namespace, letting the Integrations (and the rest of CRDs) to declare which is the operator in charge of reconciling.
 
 The new model translates into more liberty from the user which can define a "self service" tenancy model. You can have several Camel K operators running, each of them managing its own set of resources. The nice thing is that we have worked to maintain full compatibility with what we used to have. So, if you don't need this new advanced feature, the application will behave exactly as it was.