[camel-website] 10/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 51f3827b4282de51e5064d435b59b9baf150df4e
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Tue Mar 1 15:12:52 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 015af81..b4b0fcc 100644
--- a/content/blog/2022/03/camel-k-roadmap-2022/index.md
+++ b/content/blog/2022/03/camel-k-roadmap-2022/index.md
@@ -43,7 +43,7 @@ We have several installation process options in place. We may need to harmonize
 
 * Document the usage of Kustomize ([#2758](https://github.com/apache/camel-k/issues/2758))
 * Deprecate `kamel install` in favor of `kubectl apply -k` / `kustomize`
-* Move to descoped OLM model
+* Move to descoped Operator Lifecycle Manager [OLM](https://docs.openshift.com/container-platform/4.9/operators/understanding/olm/olm-understanding-olm.html) model
 
 There is some preliminary work introduced in release 1.7 around [Kustomize](https://github.com/apache/camel-k/releases/tag/v1.7.0). We may leverage that in order to identify a replacement for the kamel install. We should analyze how that will happen and the user experience around any new way we’ll propose to the community.
 Another thread we should follow is related to the proposal about descoped OLM. This part should be put in a wider context around the OLM project.