docs: Move the GDBusProxy SECTION

Move it to the struct docs.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Helps: #3037

gio/gdbusproxy.c

@@ -47,54 +47,56 @@
 #include "gmarshal-internal.h"
 
 /**
- * SECTION:gdbusproxy
+ * GDBusProxy:
- * @short_description: Client-side D-Bus interface proxy
- * @include: gio/gio.h
  *
- * #GDBusProxy is a base class used for proxies to access a D-Bus
+ * `GDBusProxy` is a base class used for proxies to access a D-Bus
- * interface on a remote object. A #GDBusProxy can be constructed for
+ * interface on a remote object. A `GDBusProxy` can be constructed for
  * both well-known and unique names.
  *
- * By default, #GDBusProxy will cache all properties (and listen to
+ * By default, `GDBusProxy` will cache all properties (and listen to
  * changes) of the remote object, and proxy all signals that get
  * emitted. This behaviour can be changed by passing suitable
- * #GDBusProxyFlags when the proxy is created. If the proxy is for a
+ * [flags@Gio.DBusProxyFlags] when the proxy is created. If the proxy is for a
  * well-known name, the property cache is flushed when the name owner
  * vanishes and reloaded when a name owner appears.
  *
- * The unique name owner of the proxy's name is tracked and can be read from
+ * The unique name owner of the proxy’s name is tracked and can be read from
- * #GDBusProxy:g-name-owner. Connect to the #GObject::notify signal to
+ * [property@Gio.DBusProxy:g-name-owner]. Connect to the
- * get notified of changes. Additionally, only signals and property
+ * [signal@GObject.Object::notify] signal to get notified of changes.
- * changes emitted from the current name owner are considered and
+ * Additionally, only signals and property changes emitted from the current name
- * calls are always sent to the current name owner. This avoids a
+ * owner are considered and calls are always sent to the current name owner.
- * number of race conditions when the name is lost by one owner and
+ * This avoids a number of race conditions when the name is lost by one owner
- * claimed by another. However, if no name owner currently exists,
+ * and claimed by another. However, if no name owner currently exists,
  * then calls will be sent to the well-known name which may result in
  * the message bus launching an owner (unless
- * %G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START is set).
+ * `G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START` is set).
  *
  * If the proxy is for a stateless D-Bus service, where the name owner may
- * be started and stopped between calls, the #GDBusProxy:g-name-owner tracking
+ * be started and stopped between calls, the
- * of #GDBusProxy will cause the proxy to drop signal and property changes from
+ * [property@Gio.DBusProxy:g-name-owner] tracking of `GDBusProxy` will cause the
- * the service after it has restarted for the first time. When interacting
+ * proxy to drop signal and property changes from the service after it has
- * with a stateless D-Bus service, do not use #GDBusProxy — use direct D-Bus
+ * restarted for the first time. When interacting with a stateless D-Bus
- * method calls and signal connections.
+ * service, do not use `GDBusProxy` — use direct D-Bus method calls and signal
+ * connections.
  *
- * The generic #GDBusProxy::g-properties-changed and
+ * The generic [signal@Gio.DBusProxy::g-properties-changed] and
- * #GDBusProxy::g-signal signals are not very convenient to work with.
+ * [signal@Gio.DBusProxy::g-signal] signals are not very convenient to work
- * Therefore, the recommended way of working with proxies is to subclass
+ * with. Therefore, the recommended way of working with proxies is to subclass
- * #GDBusProxy, and have more natural properties and signals in your derived
+ * `GDBusProxy`, and have more natural properties and signals in your derived
- * class. This [example][gdbus-example-gdbus-codegen] shows how this can
+ * class. This [example](migrating-gdbus.html#using-gdbus-codegen) shows how
- * easily be done using the [gdbus-codegen][gdbus-codegen] tool.
+ * this can easily be done using the [`gdbus-codegen`](gdbus-codegen.html) tool.
  *
- * A #GDBusProxy instance can be used from multiple threads but note
+ * A `GDBusProxy` instance can be used from multiple threads but note
- * that all signals (e.g. #GDBusProxy::g-signal, #GDBusProxy::g-properties-changed
+ * that all signals (e.g. [signal@Gio.DBusProxy::g-signal],
- * and #GObject::notify) are emitted in the
+ * [signal@Gio.DBusProxy::g-properties-changed] and
- * [thread-default main context][g-main-context-push-thread-default]
+ * [signal@GObject.Object::notify]) are emitted in the thread-default main
- * of the thread where the instance was constructed.
+ * context (see [method@GLib.MainContext.push_thread_default]) of the thread
+ * where the instance was constructed.
  *
  * An example using a proxy for a well-known name can be found in
- * [gdbus-example-watch-proxy.c](https://gitlab.gnome.org/GNOME/glib/-/blob/HEAD/gio/tests/gdbus-example-watch-proxy.c)
+ * [`gdbus-example-watch-proxy.c`](https://gitlab.gnome.org/GNOME/glib/-/blob/HEAD/gio/tests/gdbus-example-watch-proxy.c).
+ *
+ * Since: 2.26
  */
 
 /* lock protecting the mutable properties: name_owner, timeout_msec,

gio/gdbusproxy.h

@@ -42,14 +42,6 @@ G_BEGIN_DECLS
 typedef struct _GDBusProxyClass   GDBusProxyClass;
 typedef struct _GDBusProxyPrivate GDBusProxyPrivate;
 
-/**
- * GDBusProxy:
- *
- * The #GDBusProxy structure contains only private data and
- * should only be accessed using the provided API.
- *
- * Since: 2.26
- */
 struct _GDBusProxy
 {
   /*< private >*/