From 076427e511ede6487bac122d886852aaf62c5d0e Mon Sep 17 00:00:00 2001
From: Daniele Martinoli <86618610+dmartinol@users.noreply.github.com>
Date: Fri, 8 Mar 2024 11:36:59 +0100
Subject: [PATCH] updating managed props suffix

---
 .../ROOT/pages/cloud/operator/configuring-workflows.adoc        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflows.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflows.adoc
index 8e25a416c..b0f8e3694 100644
--- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflows.adoc
+++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflows.adoc
@@ -11,7 +11,7 @@ This document describes how to configure a Workflow service with the {operator_n
 When the operator deploys the Workflow service, it also creates two `ConfigMap`s to store the runtime properties:
 
 * The user properties are defined in a `ConfigMap` named after the `SonataFlow` object with the suffix `-props`. For example, if your Workflow name is `greeting`, then the `ConfigMap` name is `greeting-props`.
-* The xref:#managed-props[Managed Properties] are defined in a `ConfigMap` named after the `SonataFlow` object with the suffix `-managed-props`. For example, if your Workflow name is `greeting`, then the `ConfigMap` name is `greeting-props`.
+* The xref:#managed-props[Managed Properties] are defined in a `ConfigMap` named after the `SonataFlow` object with the suffix `-managed-props`. For example, if your Workflow name is `greeting`, then the `ConfigMap` name is `greeting-managed-props`.
 
 [IMPORTANT]
 ====