diff --git a/docs/reference/gobject/tut_gtype.xml b/docs/reference/gobject/tut_gtype.xml
index f6d529eb4..2acc26311 100644
--- a/docs/reference/gobject/tut_gtype.xml
+++ b/docs/reference/gobject/tut_gtype.xml
@@ -232,6 +232,10 @@ struct _GTypeValueTable
         There are a number of conventions users are expected to follow when creating new types
         which are to be exported in a header file:
         <itemizedlist>
+          <listitem><para>
+            Type names (including object names) must be at least three
+            characters long and start with ‘a–z’, ‘A–Z’ or ‘_’.
+          </para></listitem>
           <listitem><para>
             Use the <function>object_method</function> pattern for function names: to invoke
             the method named foo on an instance of object type bar, call 
diff --git a/gobject/gtype.c b/gobject/gtype.c
index 4e6f77d89..990002b3b 100644
--- a/gobject/gtype.c
+++ b/gobject/gtype.c
@@ -76,10 +76,10 @@
  * separately (typically by using #GArray or #GPtrArray) and put a pointer
  * to the buffer in the structure.
  *
- * A final word about type names: Such an identifier needs to be at least
- * three characters long. There is no upper length limit. The first character
- * needs to be a letter (a-z or A-Z) or an underscore '_'. Subsequent
- * characters can be letters, numbers or any of '-_+'.
+ * As mentioned in the [GType conventions][gtype-conventions], type names must
+ * be at least three characters long. There is no upper length limit. The first
+ * character must be a letter (a–z or A–Z) or an underscore (‘_’). Subsequent
+ * characters can be letters, numbers or any of ‘-_+’.
  */