docs: update managed events slug conflict behavior

event-types/managed-events.mdx

@@ -27,7 +27,12 @@ Think of the managed-event you created as a team admin as an event template, tha
 
 Whenever you make changes to locked fields, every team member will also get the same change on their regular event type created upon this managed event-type. Note that unlocked fields will not have any effect on already created event types for assigned members, only for new assign members.
 
-Take into consideration that whenever you try to assign a managed event-type to a team member that already has an event-type with the same slug, you will be getting a pop-up message to confirm you want to proceed to delete the existing conflicting event-type from the team member and notify them about this so the managed-event type can be created in its place. Like so:
+If you enable the **Assign all team members** toggle on a managed event type, a warning dialog appears to let you know that any team member — including future members — who has a personal event type with the same slug will have their booking link automatically replaced by the managed event type. Team members are notified via email when this happens.
 
+When you assign a managed event type to a team member who already has an event type with the same slug, a confirmation dialog appears. If you proceed, the team member's personal event type is **hidden and renamed** rather than deleted. This means:
 
-For which, team members notified will be getting the following email notification.
+- The personal event type and its existing bookings are preserved.
+- The booking link (`/slug`) now points to the new managed event type.
+- The team member can still find their original event type (now hidden) on their event types page.
+
+Team members affected by this change receive an email notification letting them know their booking link has been replaced and where to find their original event type.