summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFred Morcos <fm+gnome@fredmorcos.com>2022-01-03 10:27:51 +0000
committerFred Morcos <fm+gnome@fredmorcos.com>2022-01-03 10:27:51 +0000
commit31714e5c1d9e85b22c067e902e1a6d57c3d7f17f (patch)
tree97f9947ccd67c50a11c892f561be2cd97996d468
parent48b83d3e97619d579649bbc74aacb898a39e34ee (diff)
downloadgtk+-31714e5c1d9e85b22c067e902e1a6d57c3d7f17f.tar.gz
Minor doc fix
-rw-r--r--gdk/gdkcursor.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/gdk/gdkcursor.c b/gdk/gdkcursor.c
index e3aea8e653..ccb7e39b77 100644
--- a/gdk/gdkcursor.c
+++ b/gdk/gdkcursor.c
@@ -47,8 +47,7 @@
* Cursors by themselves are not very interesting: they must be bound to a
* window for users to see them. This is done with [method@Gdk.Surface.set_cursor]
* or [method@Gdk.Surface.set_device_cursor]. Applications will typically
- * use higher-level GTK functions such as [method@Gtk.Widget.set_cursor]`
- * instead.
+ * use higher-level GTK functions such as [method@Gtk.Widget.set_cursor] instead.
*
* Cursors are not bound to a given [class@Gdk.Display], so they can be shared.
* However, the appearance of cursors may vary when used on different