summaryrefslogtreecommitdiff
path: root/gdk/gdkdisplaymanager.c
diff options
context:
space:
mode:
authorEvan Nemerson <evan@nemerson.com>2014-05-16 20:12:51 -0700
committerEvan Nemerson <evan@nemerson.com>2014-05-19 11:47:59 -0700
commit701adf81b6bbc621f65f784f4f5decd2723e3a16 (patch)
treebf1a8a1cbb810a0703501d781b139e340f34eeb1 /gdk/gdkdisplaymanager.c
parentca790195863df95712d62696fc86dbacaf100a8e (diff)
downloadgtk+-701adf81b6bbc621f65f784f4f5decd2723e3a16.tar.gz
gdk: assorted introspection and documentation fixes
https://bugzilla.gnome.org/show_bug.cgi?id=729983
Diffstat (limited to 'gdk/gdkdisplaymanager.c')
-rw-r--r--gdk/gdkdisplaymanager.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/gdk/gdkdisplaymanager.c b/gdk/gdkdisplaymanager.c
index 85fb8eefdf..c6813d02bc 100644
--- a/gdk/gdkdisplaymanager.c
+++ b/gdk/gdkdisplaymanager.c
@@ -69,13 +69,13 @@
* notification when displays appear or disappear or the default display
* changes.
*
- * You can use gdk_display_manager_get() to obtain the GdkDisplayManager
+ * You can use gdk_display_manager_get() to obtain the #GdkDisplayManager
* singleton, but that should be rarely necessary. Typically, initializing
* GTK+ opens a display that you can work with without ever accessing the
- * GdkDisplayManager.
+ * #GdkDisplayManager.
*
* The GDK library can be built with support for multiple backends.
- * The GdkDisplayManager object determines which backend is used
+ * The #GdkDisplayManager object determines which backend is used
* at runtime.
*
* When writing backend-specific code that is supposed to work with