From 7927a69c5ba163222820c580f9152ae7883c16cc Mon Sep 17 00:00:00 2001
From: Walter Medvedeo <wmedvedeo@gmail.com>
Date: Tue, 5 Nov 2024 19:14:44 +0100
Subject: [PATCH] Update
 serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc

Co-authored-by: Kalyani Desai <43639538+kaldesai@users.noreply.github.com>
---
 .../modules/ROOT/pages/cloud/operator/supporting-services.adoc  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc
index 5503eb718..327a4b76d 100644
--- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc
+++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc
@@ -247,7 +247,7 @@ In a regular {product_name} installation, the preferred method is to use a <<pla
 [#data-index-eventing-system-configuration]
 === Data Index Eventing system configuration
 
-To configure a service scoped eventing system for the Data Index, you must use the field `spec.services.dataIndex.source.ref` in the `SonataFlowPlatform` CR to refer a specific Knative Eventing Broker.
+To configure a service-scoped eventing system for the Data Index, you must use the field `spec.services.dataIndex.source.ref` in the `SonataFlowPlatform` CR to refer to a specific Knative Eventing Broker.
 
 This information signals the {operator_name} to automatically link the Data Index to `consume` the {product_name} system events from that Broker.