backport to 8.3

versioned_docs/version-8.3/components/modeler/bpmn/multi-instance/multi-instance.md

@@ -1,24 +1,23 @@
 ---
 id: multi-instance
 title: "Multi-instance"
-description: "A multi-instance activity is executed multiple times - once for each element of a given collection."
+description: "Learn about multi-instance activities like service tasks and receive tasks. These can be executed multiple times - once for each element of a given collection."
 ---
 
 A multi-instance activity is executed multiple times - once for each element of a given collection (like a _foreach_ loop in a programming language).
 
-The following activities can be marked as multi-instance:
-
-- [Service tasks](../service-tasks/service-tasks.md)
-- [Receive tasks](../receive-tasks/receive-tasks.md)
-- [Embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md)
-- [Call activities](../call-activities/call-activities.md)
+We support the multi-instance marker for all [supported activities](/components/modeler/bpmn/bpmn-coverage.md), such as service tasks, receive tasks, embedded subprocceses, and call activities. For example:
 
 ![multi-instance](assets/multi-instance-example.png)
 
 On the execution level, a multi-instance activity has two parts: a multi-instance body, and an inner activity. The multi-instance body is the container for all instances of the inner activity.
 
 When the activity is entered, the multi-instance body is activated and one instance for every element of the `inputCollection` is created (sequentially or in parallel). When all instances are completed, the body is completed and the activity is left.
 
+:::note
+Events with a `JobWorker` implementation, such as intermediate throw events, do not support this marker.
+:::
+
 ## Sequential vs. parallel
 
 A multi-instance activity is executed either sequentially or in parallel (default). In the BPMN, a sequential multi-instance activity is displayed with three horizontal lines at the bottom. A parallel multi-instance activity is represented by three vertical lines.

versioned_docs/version-8.4/components/modeler/bpmn/multi-instance/multi-instance.md

@@ -1,24 +1,23 @@
 ---
 id: multi-instance
 title: "Multi-instance"
-description: "A multi-instance activity is executed multiple times - once for each element of a given collection."
+description: "Learn about multi-instance activities like service tasks and receive tasks. These can be executed multiple times - once for each element of a given collection."
 ---
 
 A multi-instance activity is executed multiple times - once for each element of a given collection (like a _foreach_ loop in a programming language).
 
-The following activities can be marked as multi-instance:
-
-- [Service tasks](../service-tasks/service-tasks.md)
-- [Receive tasks](../receive-tasks/receive-tasks.md)
-- [Embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md)
-- [Call activities](../call-activities/call-activities.md)
+We support the multi-instance marker for all [supported activities](/components/modeler/bpmn/bpmn-coverage.md), such as service tasks, receive tasks, embedded subprocceses, and call activities. For example:
 
 ![multi-instance](assets/multi-instance-example.png)
 
 On the execution level, a multi-instance activity has two parts: a multi-instance body, and an inner activity. The multi-instance body is the container for all instances of the inner activity.
 
 When the activity is entered, the multi-instance body is activated and one instance for every element of the `inputCollection` is created (sequentially or in parallel). When all instances are completed, the body is completed and the activity is left.
 
+:::note
+Events with a `JobWorker` implementation, such as intermediate throw events, do not support this marker.
+:::
+
 ## Sequential vs. parallel
 
 A multi-instance activity is executed either sequentially or in parallel (default). In the BPMN, a sequential multi-instance activity is displayed with three horizontal lines at the bottom. A parallel multi-instance activity is represented by three vertical lines.

versioned_docs/version-8.5/components/modeler/bpmn/multi-instance/multi-instance.md

@@ -1,24 +1,23 @@
 ---
 id: multi-instance
 title: "Multi-instance"
-description: "A multi-instance activity is executed multiple times - once for each element of a given collection."
+description: "Learn about multi-instance activities like service tasks and receive tasks. These can be executed multiple times - once for each element of a given collection."
 ---
 
 A multi-instance activity is executed multiple times - once for each element of a given collection (like a _foreach_ loop in a programming language).
 
-The following activities can be marked as multi-instance:
-
-- [Service tasks](../service-tasks/service-tasks.md)
-- [Receive tasks](../receive-tasks/receive-tasks.md)
-- [Embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md)
-- [Call activities](../call-activities/call-activities.md)
+We support the multi-instance marker for all [supported activities](/components/modeler/bpmn/bpmn-coverage.md), such as service tasks, receive tasks, embedded subprocceses, and call activities. For example:
 
 ![multi-instance](assets/multi-instance-example.png)
 
 On the execution level, a multi-instance activity has two parts: a multi-instance body, and an inner activity. The multi-instance body is the container for all instances of the inner activity.
 
 When the activity is entered, the multi-instance body is activated and one instance for every element of the `inputCollection` is created (sequentially or in parallel). When all instances are completed, the body is completed and the activity is left.
 
+:::note
+Events with a `JobWorker` implementation, such as intermediate throw events, do not support this marker.
+:::
+
 ## Sequential vs. parallel
 
 A multi-instance activity is executed either sequentially or in parallel (default). In the BPMN, a sequential multi-instance activity is displayed with three horizontal lines at the bottom. A parallel multi-instance activity is represented by three vertical lines.