Code addings

serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflow-eventing-system.adoc

@@ -26,7 +26,7 @@ In a regular SonataFlow installation, the preferred method is to use the <<platf
 
 To configure a platform-scoped eventing system, you must use the field `spec.eventing.broker.ref` in the `SonataFlowPlatform` CR to refer to a Knative Eventing broker.
 
-This information signals the {operator_name} to automatically link every workflow deployed in that namespace, to `produce` and `consume` the events by using that Broker.
+This information signals the {operator_name} to automatically link every workflow deployed in that namespace, with the `preview` or `gitops` profile, to `produce` and `consume` the events by using that Broker.
 
 Additionally, the supporting services deployed in that namespace, that do not provide a custom eventing system configuration, will be linked to that broker.
 For more information about configuring the supporting services eventing system, xref:cloud/operator/supporting-services.adoc#configuring-supporting-services-eventing-system[see].

serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc

@@ -203,7 +203,7 @@ To configure a platform-scoped eventing system, you must use the field `spec.eve
 
 This information signals the {operator_name} to automatically link the supporting services to `produce` and `consume` the events by using that Broker.
 
-Additionally, workflows deployed in that namespace, that don't provide a custom eventing system configuration, will be linked to that Broker.
+Additionally, workflows deployed in that namespace, with the `preview` or `gitops` profile, that don't provide a custom eventing system configuration, will be linked to that Broker.
 For more information about configuring the workflow eventing system, xref:cloud/operator/configuring-workflow-eventing-system.adoc[see].
 
 The following `SonataFlowPlatform` CR fragment shows an example of such configuration: