Branding cleanup: KDE -> TDE.

3 files changed, 7 insertions, 7 deletions

diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index 54dd8a8b..35602c78 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -184,7 +184,7 @@ are able to interact with the file manager via drag'n drop, offer session manage
 features offered by the KDE libraries are used.  Both, the Qt toolkit and the KDE libraries, are implemented
 in the C++ programming language; therefore applications that make use of these libraries are also mostly 
 written in C++. In the following chapter, we'll make a short trip through the libraries to see what already
-is provided and how Qt and KDE applications are created in general. 
+is provided and how Qt and TDE applications are created in general. 
 </para>
 <para>
 Both, the Qt toolkit and the KDE libraries, are implemented in the C++ programming language; 
@@ -522,7 +522,7 @@ and the <ulink url="doc.trolltech.com">Qt online reference</ulink>.
 <sect2 id="c2s3s1">
 <title>The KDE 3.x libraries</title>
 <para>
-The main KDE libraries you'll be using for creating your own KDE applications are:
+The main KDE libraries you'll be using for creating your own TDE applications are:
 <itemizedlist>
 <listitem><para>
 the tdecore library, containing all classes that are non-visible elements to provide application functionality
@@ -939,7 +939,7 @@ Let's have a look at the constructor and see how this instance is called
 </para>
 <para>
 Notice that <classname>KScribble</classname> inherits the <classname>KMainWindow</classname> class - a 
-commonly used base class for KDE applications.  We initialize a class called <classname>KScribbleView</classname>
+commonly used base class for TDE applications.  We initialize a class called <classname>KScribbleView</classname>
 as our central widget, create a <classname>KStatusBar</classname> via the <methodname>statusBar()</methodname>
 method (line 16), and connect some signals and slots together.
 </para>
diff --git a/languages/cpp/doc/kde2book.toc b/languages/cpp/doc/kde2book.toc
index e10972d4..aa087e84 100644
--- a/languages/cpp/doc/kde2book.toc
+++ b/languages/cpp/doc/kde2book.toc
@@ -1368,9 +1368,9 @@
 <entry name="KDevelop IDE, gdb debugger, options" url="ch18lev1sec6.html"/>
 <entry name="KDevelop IDE, gdb debugger, running" url="ch18lev1sec6.html"/>
 <entry name="KDevelop IDE, gdb debugger" url="ch18lev1sec6.html"/>
-<entry name="KDevelop IDE, KDE applications, creating, Application Wizard" url="ch18lev1sec2.html"/>
-<entry name="KDevelop IDE, KDE applications, creating, project editing" url="ch18lev1sec2.html"/>
-<entry name="KDevelop IDE, KDE applications, creating, templates" url="ch18lev1sec2.html"/>
+<entry name="KDevelop IDE, TDE applications, creating, Application Wizard" url="ch18lev1sec2.html"/>
+<entry name="KDevelop IDE, TDE applications, creating, project editing" url="ch18lev1sec2.html"/>
+<entry name="KDevelop IDE, TDE applications, creating, templates" url="ch18lev1sec2.html"/>
 <entry name="KDevelop IDE, software development, documentation" url="ch18.html"/>
 <entry name="KDevelop IDE, software development, languages" url="ch18.html"/>
 <entry name="KDevelop IDE, software development, packages" url="ch18.html"/>
diff --git a/parts/scripting/README b/parts/scripting/README
index 566feaa9..6f0a89ed 100644
--- a/parts/scripting/README
+++ b/parts/scripting/README
@@ -1,6 +1,6 @@
 KScript In KDevelop
 
-KScriptInterface allows us to have a generic way to add scripting languages to KDE applications.  KScriptInterface is not really a scripting language per say, but an interface so that applications can embed scripting languages without explicitly linking to them.  This allows all runtime linkage to the different interpreters.  Currently the most effective way for scripts to communicate with applications is via DCOP.  KScriptInterface script engines provide some convinences methods to access the dcop interfaces of the embedding application.  
+KScriptInterface allows us to have a generic way to add scripting languages to TDE applications.  KScriptInterface is not really a scripting language per say, but an interface so that applications can embed scripting languages without explicitly linking to them.  This allows all runtime linkage to the different interpreters.  Currently the most effective way for scripts to communicate with applications is via DCOP.  KScriptInterface script engines provide some convinences methods to access the dcop interfaces of the embedding application.  
 
 In KDevelop we have the ability to use scripts written for Kate, since the KateText interface is fully exported to DCOP.  By default KDevelop will import Kate scripts.  Users can also add other search paths for loading scripts.