From 5142216f0927a5c3b673d5df38b57add2bb1b8ff Mon Sep 17 00:00:00 2001 From: Walter Medvedeo Date: Wed, 22 May 2024 08:55:12 +0200 Subject: [PATCH] Update serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc Co-authored-by: Ricardo Zanini <1538000+ricardozanini@users.noreply.github.com> --- .../modules/ROOT/pages/cloud/operator/using-persistence.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc index 3d35e494d..df4293481 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc @@ -16,7 +16,7 @@ That configuration must be provided by using the <<_configuring_the_persistence_ The `SonataFlowPlatform` CR facilitates the configuration of the persistence with namespace scope. It means that it will be automatically applied to all the workflows deployed in that namespace. This can be useful to reduce the amount resources to configure, for example, in cases where the workflows deployed in that namespace belongs to the same application, etc. -That decision is left to each particular use case, however, it's important to know, that this configuration can be overridden by any workflow in that namespace by using the <<_configuring_the_persistence_using_the_sonataflow_cr, SonataFlow CR>>. +That decision is left to each particular use case, however, it's important to know, that this configuration can be overridden by any workflow in that namespace by using the <<_configuring_the_persistence_using_the_sonataflow_cr, `SonataFlow` CR>>. [NOTE] ====