[gtkmm-documentation] Fix capitalisation of Qt in tutorial

[David King <davidk src gnome org>]

commit 44f2f71220126561c6d65d43476f547b79c3f388
Author: David King <davidk openismus com>
Date:   Thu Apr 1 12:04:31 2010 +0200

    Fix capitalisation of Qt in tutorial
    
    * docs/tutorial/C/gtkmm-tutorial-in.xml: Qt, not QT.

 ChangeLog                             |    6 ++++++
 docs/tutorial/C/gtkmm-tutorial-in.xml |   10 +++++-----
 2 files changed, 11 insertions(+), 5 deletions(-)
---
diff --git a/ChangeLog b/ChangeLog
index 8abd6d8..0b5af14 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2010-04-01  David King  <davidk openismus com>
+
+	Fix capitalisation of Qt in tutorial
+
+	* docs/tutorial/C/gtkmm-tutorial-in.xml: Qt, not QT.
+
 2.20.0:
 
 2010-03-18  Murray Cumming  <murrayc murrayc com>
diff --git a/docs/tutorial/C/gtkmm-tutorial-in.xml b/docs/tutorial/C/gtkmm-tutorial-in.xml
index 4e45912..420974f 100644
--- a/docs/tutorial/C/gtkmm-tutorial-in.xml
+++ b/docs/tutorial/C/gtkmm-tutorial-in.xml
@@ -152,10 +152,10 @@ using &gtkmm; without purchasing licenses.
 </sect2>
 
 <sect2 id="gtkmm-vs-qt">
-<title>&gtkmm; compared to QT</title>
-<para>Trolltech's QT is the closest competition to &gtkmm;, so it deserves discussion.</para>
+<title>&gtkmm; compared to Qt</title>
+<para>Trolltech's Qt is the closest competition to &gtkmm;, so it deserves discussion.</para>
 
-<para>&gtkmm; developers tend to prefer &gtkmm; to QT because &gtkmm; does things in a more C++ way. QT originates from a time when C++ and the standard library were not standardised or well supported by compilers. It therefore duplicates a lot of stuff that is now in the standard library, such as containers and type information. Most significantly, Trolltech modified the C++ language to provide signals, so that QT classes cannot be used easily with non-QT classes. &gtkmm; was able to use standard C++ to provide signals without changing the C++ language. See the FAQ for more detailed differences.</para>
+<para>&gtkmm; developers tend to prefer &gtkmm; to Qt because &gtkmm; does things in a more C++ way. Qt originates from a time when C++ and the standard library were not standardised or well supported by compilers. It therefore duplicates a lot of stuff that is now in the standard library, such as containers and type information. Most significantly, Trolltech modified the C++ language to provide signals, so that Qt classes cannot be used easily with non-Qt classes. &gtkmm; was able to use standard C++ to provide signals without changing the C++ language. See the FAQ for more detailed differences.</para>
 </sect2>
 
 <sect2 id="gtkmm-is-a-wrapper">
@@ -8079,7 +8079,7 @@ This is a full working example that defines and uses custom signal.
 <appendix id="sec-signals-comparison">
 <title>Comparison with other signalling systems</title>
 <para>
-TODO: Rewrite this paragraph and talk about QT's moc.
+TODO: Rewrite this paragraph and talk about Qt's moc.
 (An aside: <application>GTK+</application> calls this scheme "signalling"; the
 sharp-eyed reader with GUI toolkit experience will note that this same design
 is often
@@ -8096,7 +8096,7 @@ play the role of listeners - sort of.  More on this later.)
 &gtkmm; signal handlers are strongly-typed, whereas
 <application>GTK+</application> C code allows you to connect a callback with
 the wrong number and type of arguments, leading to a segfault at runtime. And,
-unlike <application>QT</application>, &gtkmm; achieves this without modifying
+unlike <application>Qt</application>, &gtkmm; achieves this without modifying
 the C++ language.</para>
 <para>
 Re. Overriding signal handlers: You can do this in the straight-C world of GTK+ too; that's what GTK's