Branding cleanup: KDE -> TDE.

1 files changed, 8 insertions, 8 deletions

diff --git a/kopete/INSTALL b/kopete/INSTALL
index a8f262e7..8c75ea29 100644
--- a/kopete/INSTALL
+++ b/kopete/INSTALL
@@ -188,18 +188,18 @@ Finding Plugins
 If you don't see any "plugins" listed in the Configure Plugins...
 dialog, or the list of messaging protocols in the Add Account Wizard
 is empty after installing, Kopete you may have installed it in a
-directory where KDE doesn't look for additional resources like plugins.
+directory where TDE doesn't look for additional resources like plugins.
 
 It's also possible that you've just been too impatient :)
 
 Kopete installs several .desktop files that have to be processed by a
-KDE application called 'kbuildsycoca'. If you run Kopete directly
+TDE application called 'kbuildsycoca'. If you run Kopete directly
 after installing it this process might still be running and Kopete
 doesn't see the new plugins yet. Try running 'kbuildsycoca' from a
 console and restart Kopete when it finishes. If that doesn't help,
 please read on.
 
-KDE applications by default look in all directories listed in the
+TDE applications by default look in all directories listed in the
 /etc/kderc file, the $TDEDIRS environment variable, in $TDEDIR if
 this variable doesn't exist, and ultimately in the directory where
 tdelibs is installed. Unless you take special precautions applications
@@ -213,7 +213,7 @@ if it doesn't exist yet):
     prefixes=/the/prefix/I/used/for/kopete
 
 If you don't have write access to /etc/kderc, or if you want to use more
-parallel builds of KDE and/or Kopete you need to rely on the environment
+parallel builds of TDE and/or Kopete you need to rely on the environment
 variables instead.
 
 If $TDEDIRS currently points to /opt/trinity and you installed Kopete
@@ -223,17 +223,17 @@ and for all users, like /etc/profile. The name of the preferred version
 varies from system to system.
 
 As a last resort you can simply install Kopete in the same directory as
-where your KDE resides by adding a flag to configure like
+where your TDE resides by adding a flag to configure like
 
     ./configure --prefix=/opt/trinity
 
-if KDE is installed in /opt/trinity. The downside is that you'll probably
+if TDE is installed in /opt/trinity. The downside is that you'll probably
 end up installing Kopete into directories used by your distribution,
 instead of a separate path for your own packages like the /usr/local/
 tree. Whether or not your package manager has problems with that and
 whether or not you'll accept those problems should they occur is of
 course up to you to decide, but we strongly recommend to not install
 source-compiled packages like Kopete in directories that are managed
-by a package manager and only use the KDE prefix if you compiled all
-of KDE from source yourself.
+by a package manager and only use the TDE prefix if you compiled all
+of TDE from source yourself.