[gtk/main-cleanup: 3/7] docs: Remove more mentions of gtk_main_do_event

[Matthias Clasen <matthiasc src gnome org>]

commit c1970009ffa67bd3a93b126cf9fe195e4c2ecae9
Author: Matthias Clasen <mclasen redhat com>
Date:   Sun Feb 9 10:45:33 2020 -0500

    docs: Remove more mentions of gtk_main_do_event

 gtk/gtkmain.c | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)
---
diff --git a/gtk/gtkmain.c b/gtk/gtkmain.c
index d8c1d35beb..0056c896a1 100644
--- a/gtk/gtkmain.c
+++ b/gtk/gtkmain.c
@@ -2702,16 +2702,10 @@ gtk_propagate_event_internal (GtkWidget *widget,
  * if the event remains unhandled. This function will emit the event
  * through all the hierarchy of @widget through all propagation phases.
  *
- * Events received by GTK from GDK normally begin in gtk_main_do_event().
+ * Events received by GTK from GDK normally begin at a #GtkRoot widget.
  * Depending on the type of event, existence of modal dialogs, grabs, etc.,
  * the event may be propagated; if so, this function is used.
  *
- * gtk_propagate_event() calls gtk_widget_event() on each widget it
- * decides to send the event to. So gtk_widget_event() is the lowest-level
- * function; it simply emits the #GtkWidget::event and possibly an
- * event-specific signal on a widget. gtk_propagate_event() is a bit
- * higher-level, and gtk_main_do_event() is the highest level.
- *
  * All that said, you most likely don’t want to use any of these
  * functions; synthesizing events is rarely needed. There are almost
  * certainly better ways to achieve your goals. For example, use