1 files changed, 8 insertions, 10 deletions
diff --git a/doc/chalk/developers-plugins.docbook b/doc/chalk/developers-plugins.docbook
index 2e592be1..ebd5f664 100644
--- a/doc/chalk/developers-plugins.docbook
+++ b/doc/chalk/developers-plugins.docbook
@@ -33,10 +33,8 @@ the combination of a unique untranslated string (used when saving, for
 instance) and a translated string for GUI purposes.
 </para><para>
 A word on compatibility: &chalk; is still in development. From &chalk; 1.5 to
-1.6 not many API changes are expected, but there may be some. From &chalk; 1.6
-to 2.0 we will move from &Qt;3 to &Qt;4, from &tde;3 to &tde;4, from
-<command>automake</command> to <command>cmake</command>: many changes are to
-be expected. If you develop a plugin for &chalk; and choose to do so in
+1.6 not many API changes are expected, but there may be some.
+If you develop a plugin for &chalk; and choose to do so in
 &chalk;’s subversion repository, chances are excellent that we’ll help you
 porting. These changes may also render parts of this document out of date.
 Always check with the latest API documentation or the header files installed
@@ -143,7 +141,7 @@ import/export filter could be a PDF filter. Filters are loaded by the
 <title>Creating plugins</title>
 
 <para>
-Plugins are written in C++ and can use all of &tde; and &Qt; and the &chalk;
+Plugins are written in C++ and can use all of &tde; and &TQt; and the &chalk;
 developer API. Only viewplugins should use the &koffice; API. Don’t worry:
 &chalk;’s API’s are quite clear and rather extensively documented (for free
 software) and coding your first filter is really easy.
@@ -763,7 +761,7 @@ an option widget:
 </para>
 
 <itemizedlist>
-<listitem><para>Use &Qt; Designer to create a widget base, and subclass it for
+<listitem><para>Use &TQt; Designer to create a widget base, and subclass it for
 your filter</para></listitem>
 <listitem><para>Use one of the simple widgets that show a number of sliders
 for lists of integers, doubles or bools. These are useful if, like the above
@@ -773,7 +771,7 @@ bools. See the API dox for <classname>KisMultiIntegerFilterWidget</classname>,
 <classname>KisMultiBoolFilterWidget</classname>.</para></listitem>
 <listitem><para>Hand-code a widget. This is not recommended, and if you do so
 and want your filter to become part of &chalk;’s official release, then I’ll ask
-you to replate your hand-coded widget with a &Qt; Designer
+you to replate your hand-coded widget with a &TQt; Designer
 widget.</para></listitem>
 </itemizedlist>
 
@@ -871,7 +869,7 @@ non-painting tasks and shape painting tasks.
 A tool has an option widget, just like filters. Currently, the option widgets
 are shown in a tab in a dock window. We may change that to a strip under the
 main menu (which then replaces the toolbar) for &chalk; 2.0, but for now,
-design your option widget to fit in a tab. As always, it’s best to use &Qt;
+design your option widget to fit in a tab. As always, it’s best to use &TQt;
 Designer for the design of the option widget.
 </para><para>
 A good example of a tool is the star tool:
@@ -927,9 +925,9 @@ The following methods (<methodname>buttonPress</methodname>,
 <methodname>move</methodname> and <methodname>buttonRelease</methodname>) are
 called by &chalk; when the input device (mouse, stylus, eraser etc.) is
 pressed down, moved or released. Note that you also get move events if the
-mouse button isn’t pressed. The events are not the regular &Qt; events, but
+mouse button isn’t pressed. The events are not the regular &TQt; events, but
 synthetic &chalk; events because we make use of low-level trickery to get
-enough events to draw a smooth line. By default, toolkits like &Qt; (and GTK)
+enough events to draw a smooth line. By default, toolkits like &TQt; (and GTK)
 drop events if they are too busy to handle them, and we want them all.
 </para>