diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md
index 3be916a141f..c694a378e2c 100644
--- a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md
+++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md
@@ -6,14 +6,16 @@ weight: 50
 
 ## Introduction
 
-An **End Event** in workflows defines where a workflow process ends. When the workflow execution reaches this element, the process is completed and no further actions are taken.
+An **End** event in workflows defines where a workflow process ends. When the workflow execution reaches this element, the process is completed and no further actions are taken.
 
-A workflow can have multiple end events, as shown in the example below:
+A workflow can have multiple end events. In Studio Pro 11.6 and below, it is required to terminate a workflow with a single end event at the end of the main flow.
 
-{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png" alt="End Event Example" width="400" >}}
+Starting from Studio Pro 11.6, workflows can terminate through multiple end events. This means that activities with multiple outgoing paths, such as user tasks or decisions, can direct each path to its own **End** event and the workflow can complete at any of the end events. See an example below:
 
-In this example, there is a decision element where the workflow can take two different paths based on a condition. Each path leads to a different end event, either of which ends the process. In addition, an interrupting boundary event is attached to one of the user tasks, which also leads to its own end event. In all of these cases, only one path will be taken, and the process ends when it reaches the corresponding end event.
+{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png" alt="End Event Example" max-width=30% >}}
+
+In the example above, there is a decision element where the workflow can take two different paths based on a condition. Each path leads to its own end event, either of which can end the process. Out of the two paths, only one path will be taken, and the process ends when it reaches the corresponding end event.
 
 ## Properties
 
-The **End Event** does not have any configurable properties.
+The **End** event does not have any configurable properties.
diff --git a/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png b/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png
index 2d9d316861d..f49f4b0a9b5 100644
Binary files a/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png and b/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png differ