diff --git a/gtk/deprecated/gtkactiongroup.c b/gtk/deprecated/gtkactiongroup.c
index 01c2d53370..69f2c5c762 100644
--- a/gtk/deprecated/gtkactiongroup.c
+++ b/gtk/deprecated/gtkactiongroup.c
@@ -43,7 +43,7 @@
  * actions that act on that document (eg. save, cut/copy/paste, etc). Each
  * window's menus would be constructed from a combination of two action
  * groups.
- * </para>
+ *
  * <para id="Action-Accel">
  * Accelerators are handled by the GTK+ accelerator map. All actions are
  * assigned an accelerator path (which normally has the form
@@ -52,6 +52,7 @@
  * and toolitems take on this accelerator path. The GTK+ accelerator map
  * code makes sure that the correct shortcut is displayed next to the menu
  * item.
+ * </para>
  *
  * <refsect2 id="GtkActionGroup-BUILDER-UI">
  * <title>GtkActionGroup as GtkBuildable</title>
diff --git a/gtk/gtkmain.c b/gtk/gtkmain.c
index eba38ccf4e..5bc853fd77 100644
--- a/gtk/gtkmain.c
+++ b/gtk/gtkmain.c
@@ -52,7 +52,7 @@
  * example, when an Open button is clicked you might display a
  * #GtkFileChooserDialog. After a callback finishes, GTK+ will return to the
  * main loop and await more user input.
- * </para>
+ *
  * <example>
  * <title>Typical <function>main()</function> function for a GTK+ application</title>
  * <programlisting>
@@ -82,7 +82,7 @@
  * }
  * </programlisting>
  * </example>
- * <para>
+ *
  * It's OK to use the GLib main loop directly instead of gtk_main(), though it
  * involves slightly more typing. See #GMainLoop in the GLib documentation.
  */