[camel-website] 03/11: Update content/blog/2022/03/camel-k-roadmap-2022/index.md

[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 ad301ea73b3672bc8a7b0c5465a07f7507898b7f
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Tue Mar 1 15:11:42 2022 +0100

    Update content/blog/2022/03/camel-k-roadmap-2022/index.md
    
    Co-authored-by: Aurélien Pupier <ap...@redhat.com>
---
 content/blog/2022/03/camel-k-roadmap-2022/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2022/03/camel-k-roadmap-2022/index.md b/content/blog/2022/03/camel-k-roadmap-2022/index.md
index aa2ac6d..6280e74 100644
--- a/content/blog/2022/03/camel-k-roadmap-2022/index.md
+++ b/content/blog/2022/03/camel-k-roadmap-2022/index.md
@@ -92,7 +92,7 @@ Integration building process needs to be tweaked in order to guarantee scalabili
 Other efforts that will let Camel K be more mature are related to features around the runtime.
 
 * Improve route DSL parsing ([#1266](https://github.com/apache/camel-k/issues/1266))
-* Surface Camel health checks into integration status ([#2886](https://github.com/apache/camel-k/issues/2886)
+* Surface Camel health checks into integration status ([#2886](https://github.com/apache/camel-k/issues/2886))
 * Business vs. technical errors
 
 Route parsing has a great margin of improvement in order to automatically discover components, capabilities, dependencies, etc, and in general to be more reliable. Also, exposing more meaningful ways to query the healthy status of an Integration will let users speed up their troubleshooting (this part is almost completed in the latest releases).