Markup fixes.

        * gdk-pixbuf/tmpl/creating.sgml,
        gdk-pixbuf/tmpl/gdk-pixbuf-xlib-from-drawables.sgml,
        gdk-pixbuf/tmpl/gdk-pixbuf-xlib-init.sgml,
        gdk-pixbuf/tmpl/gdk-pixbuf-xlib-rendering.sgml,
        gdk-pixbuf/tmpl/refcounting.sgml: Markup fixes.

        * gtk/building.sgml, gtk/resources.sgml: Markup fixes.

        * gtk/gtk.types: Remove gtk_text_layout_get_type(). (???)

        * gdk/tmpl/general.sgml: Use <envar>, not <envvar>.

        * gdk-pixbuf-io.c, gdk-pixbuf-animation.c, gdk-pixbuf-data.c,
        gdk-pixbuf-loader.c, gdk-pixbuf-scale.c, gdk-pixbuf-util.c,
        gdk-pixdata.c: Markup fixes.

1 files changed, 17 insertions, 14 deletions

diff --git a/docs/reference/gtk/resources.sgml b/docs/reference/gtk/resources.sgml
index 5a6410c1f7..bd49b948df 100644
--- a/docs/reference/gtk/resources.sgml
+++ b/docs/reference/gtk/resources.sgml
@@ -17,9 +17,10 @@ Getting help with GTK+
 
 <para>
 If you encounter a bug, misfeature, or missing feature in GTK+, please
-file a bug report on http://bugzilla.gnome.org. We'd also appreciate
-reports of incomplete or misleading information in the GTK+
-documentation; file those against the "docs" component of the "gtk+"
+file a bug report on 
+<ulink url="http://bugzilla.gnome.org">http://bugzilla.gnome.org</ulink>. 
+We'd also appreciate reports of incomplete or misleading information in 
+the GTK+ documentation; file those against the "docs" component of the "gtk+"
 product in Bugzilla.
 </para>
 
@@ -32,7 +33,7 @@ discussed, we'll add a note to that effect in the report.
 
 <para>
 The bug tracker should definitely be used for feature requests, it's
-not only for bugs. We track all GTK+ development in bugzilla, so it's
+not only for bugs. We track all GTK+ development in Bugzilla, so it's
 the way to be sure the GTK+ developers won't forget about an issue.
 </para>
 
@@ -44,17 +45,17 @@ the way to be sure the GTK+ developers won't forget about an issue.
 <para>
 If you develop a bugfix or enhancement for GTK+, please file that in
 Bugzilla as well. Bugzilla allows you to attach files; please attach a
-patch generated by the "diff" utility, using the "-u" option to make
-the patch more readable. All patches must be offered under the terms
-of the GNU LGPL license, so be sure you are authorized to give us the
-patch under those terms.
+patch generated by the <command>diff</command> utility, using the 
+<option>-u</option> option to make the patch more readable. All patches 
+must be offered under the terms of the GNU LGPL license, so be sure you 
+are authorized to give us the patch under those terms.
 </para>
 
 <para>
 If you want to discuss your patch before or after developing it, mail 
-gtk-devel-list@gnome.org. But be sure to file the Bugzilla report as
-well; if the patch is only on the list and not in Bugzilla, it's
-likely to slip through the cracks.
+<ulink url="mail:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink>. 
+But be sure to file the Bugzilla report as well; if the patch is only on the 
+list and not in Bugzilla, it's likely to slip through the cracks.
 </para>
 
 </refsect1>
@@ -66,7 +67,8 @@ likely to slip through the cracks.
 There are several mailing lists dedicated to GTK+ and related
 libraries. Discussion of GLib, Pango, and ATK in addition to GTK+
 proper is welcome on these lists. You can subscribe or view the
-archives of these lists on http://mail.gnome.org.
+archives of these lists on 
+<ulink url="http://mail.gnome.org">http://mail.gnome.org</ulink>.
 </para>
 
 <para>
@@ -113,8 +115,9 @@ all on topic.
 <varlistentry>
 <term>gtk-doc-list@gnome.org</term>
 <listitem><para>
-gtk-doc-list is for discussion of the gtk-doc documentation system
-(used to document GTK+), and for work on the GTK+ documentation.
+gtk-doc-list is for discussion of the <application>gtk-doc</application> 
+documentation system (used to document GTK+), and for work on the GTK+ 
+documentation.
 </para></listitem>
 </varlistentry>