Update content/docs/2.15/operate/events.md

Co-authored-by: Tom Kerkhove <[email protected]>
Signed-off-by: SpiritZhou <[email protected]>

content/docs/2.15/operate/events.md

@@ -81,7 +81,7 @@ In general, an event emitted by KEDA would fundamentally come down to the follow
 
 ### Scopes: Namespace vs. Cluster
 
-Each `CloudEventSource` is defined in one namespace. For cases where you want to share a single sink among many namespaces, you can instead create a `ClusterCloudEventSource`. As a global object, this can be used from any namespace. 
+Each `CloudEventSource` is defined in one namespace and will only subscribe to events inside that namespace. If you want to subscribe to events in all namespaces, you can instead create a `ClusterCloudEventSource` resource.
 
 Defining a `ClusterCloudEventSource` works almost identically to a `CloudEventSource`, except there is no `metadata.namespace` value: