diff --git a/docs/reference/gtk/migrating-3to4.md b/docs/reference/gtk/migrating-3to4.md
index 9bc982962a..0ffe95a8b5 100644
--- a/docs/reference/gtk/migrating-3to4.md
+++ b/docs/reference/gtk/migrating-3to4.md
@@ -187,11 +187,22 @@ for this change.
 | ::grab-broken-event | - |
 
 Event signals which are not directly related to input have to be dealt with
-on a one-by-one basis. If you were using `::configure-event` and
-`::window-state-event` to save window state, you should use property
-notification for corresponding [class@Gtk.Window] properties, such as
-[property@Gtk.Window:default-width], [property@Gtk.Window:default-height],
-[property@Gtk.Window:maximized] or [property@Gtk.Window:fullscreened].
+on a one-by-one basis:
+
+ - If you were using `::configure-event` and `::window-state-event` to save
+   window state, you should use property notification for corresponding
+   [class@Gtk.Window] properties, such as [property@Gtk.Window:default-width],
+   [property@Gtk.Window:default-height], [property@Gtk.Window:maximized] or
+   [property@Gtk.Window:fullscreened].
+ - If you were using `::delete-event` to present a confirmation when using
+   the close button of a window, you should use the
+   [signal@Gtk.Window::close-request] signal.
+ - If you were using `::map-event` and `::unmap-event` to track a window
+   being mapped, you should use property notification for the
+   [property@Gdk.Surface:mapped] property instead.
+ - The `::damage-event` signal has no replacement, as the only consumer
+   of damage events were the offscreen GDK surfaces, which have no
+   replacement in GTK 4.x.
 
 ### Set a proper application ID