Markup fixes

[~andy/gtk] / docs / reference / gtk / tmpl / gtksignal.sgml

diff --git a/docs/reference/gtk/tmpl/gtksignal.sgml b/docs/reference/gtk/tmpl/gtksignal.sgml
index b5787dbe131a7820c486f529079321823c5d1319..67ecd70b0883c99edbc5e65159c5f7f9f1b94d1e 100644 (file)
--- a/docs/reference/gtk/tmpl/gtksignal.sgml
+++ b/docs/reference/gtk/tmpl/gtksignal.sgml
@@ -8,7 +8,7 @@ Object methods and callbacks.
 <para>
 The GTK+ signal system merely proxies the GLib signal system now. For future 
 usage, direct use of the <link linkend="gobject-Signals">GSignal</link> API is recommended, this avoids significant 
-performance hits where #GtkArg structures have to be converted into #GValue<!>s.
+performance hits where #GtkArg structures have to be converted into #GValue<!-- -->s.
 </para>
 
 <refsect2>
@@ -17,7 +17,7 @@ performance hits where #GtkArg structures have to be converted into #GValue<!>s.
 Signals are a way to get notification when something happens
 and to customize object behavior according to the
 user's needs.
-Every <WordAsWord>signal</WordAsWord> is uniquely identified by a name,
+Every <wordasword>signal</wordasword> is uniquely identified by a name,
 "class_name::signal_name", where signal_name might be something like
 "clicked" and class_name might be "GtkButton".  Note that some other class
 may also define a "clicked" callback, so long as it doesn't derive from
@@ -58,7 +58,7 @@ corresponding to that attachment.
 </para>
 <para>
 Functions that want to notify the user of certain actions,
-<Emphasis>emit</Emphasis> signals.
+<emphasis>emit</emphasis> signals.
 </para>
 </refsect2>
 <refsect2>
@@ -450,7 +450,7 @@ as parameter to your function:
 <programlisting>
 static void button_clicked_int (GtkButton* button, gpointer func_data)
 {
-       g_print ("button pressed: %%d\n", GPOINTER_TO_INT (func_data));
+       g_print ("button pressed: &percent;d\n", GPOINTER_TO_INT (func_data));
 }
 
 /* By calling this function, you will make the g_print above