7 files changed, 14 insertions, 14 deletions
diff --git a/doc/kommander/extending.docbook b/doc/kommander/extending.docbook
index 1adfdc25..473b8ec5 100644
--- a/doc/kommander/extending.docbook
+++ b/doc/kommander/extending.docbook
@@ -346,12 +346,12 @@ mykomplugin.cpp, compiling and installing your plugin would involve
 something similar to the following commands:
 </para>
 <screen>
-libtool --mode=compile g++ -$KDEDIR/include -IQTDIR/include \
+libtool --mode=compile g++ -$TDEDIR/include -IQTDIR/include \
    -I. -fPIC -c komlineedit.cpp
-libtool --mode=compile g++ -$KDEDIR/include -IQTDIR/include \
+libtool --mode=compile g++ -$TDEDIR/include -IQTDIR/include \
    -I. -fPIC -c mykomplugin.cpp
 
-libtool --mode=link g++ -shared -L$KDEDIR/lib -ltdeui -lkommanderwidget \
+libtool --mode=link g++ -shared -L$TDEDIR/lib -ltdeui -lkommanderwidget \
    -lkommanderplugin komlineedit.cppkomlineedit.o mykomplugin.o 
    -o libmykomplugin.so
 </screen>
@@ -359,7 +359,7 @@ libtool --mode=link g++ -shared -L$KDEDIR/lib -ltdeui -lkommanderwidget \
 If you want to install new plugin system-wide, root, use:
 </para>
 <screen>
-su -c "cp libmykomplugin.so $KDEDIR/lib"
+su -c "cp libmykomplugin.so $TDEDIR/lib"
 </screen>
 <note><para>If you use the KDevelop project generator, you will not need to do the above, but instead adapt the Makefile.am to link against extra libraries. By default, it will link to &Qt; and &kde; libraries and generate all the needed object files. Just run <command>make</command> to build, and <command>su -c make install</command> to install.</para></note>
 </sect2>
diff --git a/doc/kommander/translating.docbook b/doc/kommander/translating.docbook
index 15d7def2..629b22ea 100644
--- a/doc/kommander/translating.docbook
+++ b/doc/kommander/translating.docbook
@@ -34,7 +34,7 @@ Here is a short description about the needed steps to make a dialog translatable
 
 <listitem><para>How to extract the messages and create the .po file?</para>
 <para>
-    Use the <command>kmdr2po</command> script to extract the strings. The script is inside the <emphasis>working</emphasis> directory of the source release tarball and should be installed to <command>$KDEDIR/share/apps/kommander/translating</command> as well.
+    Use the <command>kmdr2po</command> script to extract the strings. The script is inside the <emphasis>working</emphasis> directory of the source release tarball and should be installed to <command>$TDEDIR/share/apps/kommander/translating</command> as well.
 </para>
 <para>
 Just run:
@@ -52,7 +52,7 @@ An appropriate &lt;your-kommander-dialog.po> file will be created.
 
 <listitem><para>How to install the translation?</para>
 <para>Put the compiled *.mo file either to</para>
-<para><command>$KDEDIR/share/locale/&lt;your language>/LC_MESSAGES/</command> (will be available globally for all users)</para>
+<para><command>$TDEDIR/share/locale/&lt;your language>/LC_MESSAGES/</command> (will be available globally for all users)</para>
 <para>or to </para>
 <para><command>$HOME/.kde/share/locale/&lt;your language>/LC_MESSAGES/</command> (will be available only for the current user)</para> 
 <para>directory.</para>
diff --git a/doc/kommander/tutorials.docbook b/doc/kommander/tutorials.docbook
index 0f6fd954..00f44d87 100644
--- a/doc/kommander/tutorials.docbook
+++ b/doc/kommander/tutorials.docbook
@@ -316,7 +316,7 @@ Shows how to use Table widget
 These examples reflect the most recent development state of &kommander;. In its current state &kommander; has few limitations for developing small to medium applications. It certainly is not suitable for building a KWord clone, but for a simple editor, database frontend, GUI for commandline programs or any application in the spirit of Unix/Linux small applications it is a good choice. The examples presented here are intended to show the potential as well as how to work around limitations. There are some useful tricks included in these if you want to do a more capable small application with &kommander;. Remember &kommander; is not intended to do everything, but to do most things. For this concession you should be able to build something in &kommander; faster than other alternatives ad add GUI to scripting languages not otherwise supported in KDE.
 </para>
 <note><para>
-The examples are installed to <command>$KDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
+The examples are installed to <command>$TDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
 </para>
 </note>
 
diff --git a/doc/quanta/config-quanta.docbook b/doc/quanta/config-quanta.docbook
index 0b332330..3ba20ea0 100644
--- a/doc/quanta/config-quanta.docbook
+++ b/doc/quanta/config-quanta.docbook
@@ -113,7 +113,7 @@ The place to define abbreviations (some kind of templates), that can be expanded
   <itemizedlist>
   <listitem><para><guilabel>Name:</guilabel> the user visible name</para></listitem>
   <listitem><para><guilabel>Output window:</guilabel> plugins can appear in a tab of the editor area or in a separate toolview at the bottom</para></listitem>
-  <listitem><para><guilabel>Location:</guilabel> the path to the plugin, if it is not located in the standard locations, like <filename class="directory">$<envar>KDEDIR</envar>/lib</filename> .</para></listitem>
+  <listitem><para><guilabel>Location:</guilabel> the path to the plugin, if it is not located in the standard locations, like <filename class="directory">$<envar>TDEDIR</envar>/lib</filename> .</para></listitem>
   <listitem><para><guilabel>File name:</guilabel> the relative path and the filename to the plugin's libtool file, like <filename class="libraryfile">trinity/libcervisiapart.la</filename></para></listitem>  
   <listitem><para><guilabel>Input:</guilabel> the plugin will get this information on startup, so it can open the <guilabel>Current File</guilabel>, the folder of the current file (<guilabel>Current File Path</guilabel>) or the <guilabel>Project Folder</guilabel>.</para></listitem>  
   <listitem><para><guilabel>Read only part:</guilabel> check if the plugin refuses to load. Read-only KParts usually refuse to load without this option checked.</para></listitem>  
diff --git a/doc/quanta/extending-quanta.docbook b/doc/quanta/extending-quanta.docbook
index 6dd0629e..df92f408 100644
--- a/doc/quanta/extending-quanta.docbook
+++ b/doc/quanta/extending-quanta.docbook
@@ -1195,8 +1195,8 @@ First you have to enter the name of your script with the interpreter as well. Ex
 <para>
 Although you can use full paths, the recommended way is to use the <command>%scriptdir</command> variable in the command line, like <command>sh %scriptdir/myScript.sh</command>. This way &quantaplus; will try to locate your script in the following places:
 <itemizedlist>
-<listitem><para>global script folder: <filename><envar>$KDEDIR</envar>/share/apps/quanta/scripts</filename></para></listitem>
-<listitem><para>local script folder: <filename><envar>$KDEHOME</envar>/share/apps/quanta/scripts</filename></para></listitem>
+<listitem><para>global script folder: <filename><envar>$TDEDIR</envar>/share/apps/quanta/scripts</filename></para></listitem>
+<listitem><para>local script folder: <filename><envar>$TDEHOME</envar>/share/apps/quanta/scripts</filename></para></listitem>
 <listitem><para>your path: <envar>$PATH</envar></para></listitem>
 </itemizedlist>
 There are other special variables that you can use in the command line:
@@ -1700,7 +1700,7 @@ addslashes=function.addslashes.html
 Now you can just save your <filename>docrc</filename> file, save it in
 <filename class="directory">$<envar>HOME</envar>/.kde/share/apps/quanta/doc</filename>
 or <filename
-class="directory">$<envar>KDEDIR</envar>/share/apps/quanta/doc</filename>
+class="directory">$<envar>TDEDIR</envar>/share/apps/quanta/doc</filename>
 for local or global use respectively. Then create a folder (the one
 specified in your <filename>docrc</filename> file) in the same folder
 as your <filename>docrc</filename> file and copy your &HTML; pages in
@@ -1771,7 +1771,7 @@ After a resource was downloaded, but before it is installed, &quantaplus; verifi
   </para>
 <para>The entries are:</para>
 <itemizedlist>
-  <listitem><para><guilabel>Target directory name:</guilabel>the newly created &DTEP; will go under this name to the <filename><envar>$KDEHOME</envar>/share/apps/quanta/dtep</filename> folder.
+  <listitem><para><guilabel>Target directory name:</guilabel>the newly created &DTEP; will go under this name to the <filename><envar>$TDEHOME</envar>/share/apps/quanta/dtep</filename> folder.
   </para>
   </listitem>
   <listitem><para><guilabel>Name:</guilabel>the name (definition string) of the DTD</para></listitem>
diff --git a/doc/quanta/quanta-menus.docbook b/doc/quanta/quanta-menus.docbook
index 751f4591..66449f78 100644
--- a/doc/quanta/quanta-menus.docbook
+++ b/doc/quanta/quanta-menus.docbook
@@ -1397,7 +1397,7 @@ details.
 <listitem>
 <para>
 Loads a globally defined toolbar. These are kept in <filename
-class="directory">$<envar>KDEDIR</envar>/share/apps/quanta/toolbars</filename>
+class="directory">$<envar>TDEDIR</envar>/share/apps/quanta/toolbars</filename>
 by default.
 </para>
 </listitem>
diff --git a/doc/quanta/working-with-quanta.docbook b/doc/quanta/working-with-quanta.docbook
index 4a0ca0b1..54471778 100644
--- a/doc/quanta/working-with-quanta.docbook
+++ b/doc/quanta/working-with-quanta.docbook
@@ -330,7 +330,7 @@ track this so you will need to change links.
 <para>
 Template structure on the template tab is based on the files found in
 <filename class="directory">
-$<envar>KDEDIR</envar>/share/apps/quanta/templates</filename> and
+$<envar>TDEDIR</envar>/share/apps/quanta/templates</filename> and
 <filename class="directory">
 $<envar>HOME</envar>/.kde/share/apps/quanta/templates</filename>. Each of
 these folders is specified as one of four types of container as explained <link linkend="template-types-3-2">above</link>.