Finish renaming tdevelop components

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox
index a5840885..5dd44fda 100644
--- a/doc/api/HowToAddProgrammingLanguages.dox
+++ b/doc/api/HowToAddProgrammingLanguages.dox
@@ -6,7 +6,7 @@
 
 \section LSupport List of things to have "complete" support of a given language in KDevelop
 
-  - Implement interface KDevLanguageSupport
+  - Implement interface TDevLanguageSupport
   - \ref sectionClassWizard
   - \ref sectionAttributeMethodWizard
   - \ref sectionQtUiSubclassing - (if the language has Qt bindings)
@@ -43,7 +43,7 @@ Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to se
 \section sectionLanguageSupport Language Support
 
 Any language support should be written as a tdevelop part and implement
-KDevLanguageSupport interface (<code>lib/interfaces/kdevlanguagesupport.h</code>).
+TDevLanguageSupport interface (<code>lib/interfaces/tdevlanguagesupport.h</code>).
 
 Implementing methods:
  - <code>virtual Features features();</code>
@@ -54,7 +54,7 @@ Should be enough for a language support to start working.
 
 KDevelop ships with KDevLang project template. It is a simple language support prototype that can be used when developing language support plugins with KDevelop.
 To use it, start a New Project and select: <code>C++->KDevelop->KDevelop Language Support Plugin</code> in the application wizard.
-The template is located in <code>languages/cpp/app_templates/kdevlang</code>, you can change it there if you need.
+The template is located in <code>languages/cpp/app_templates/tdevlang</code>, you can change it there if you need.
 
 
 You should look at <code>languages/ruby</code> for a simple language support
@@ -177,7 +177,7 @@ write a <b>Debugger </b>. KDevelop already provides GDB support
 \subsection sectionCompilerPlugins Compiler plugins
 
 There is an ability to create compiler plugin for KDevelop. Compiler plugin provides the compiler configuration dialog which implements command line compiler options.
-Compiler plugins must implement KDevCompilerOptions interface.
+Compiler plugins must implement TDevCompilerOptions interface.
 
 
 \section MiscInf Other Info
@@ -226,7 +226,7 @@ currently provides several build tools. They are:
     - see GenericProjectPart at <code>buildtools/generic</code>
     - Offers build tool facilities using project files in xml format (dtd is located in <code>buildtools/generic/kdevxmlproject.dtd</code>).
       Those xml files can be converted into makefiles, ant xml files or simply shell scripts using build system plugins.
-      Build system plugin is an object that implements KDevBuildSystem interface. Build system plugins are located in <code>buildtools/generic/buildsystem</code>.
+      Build system plugin is an object that implements TDevBuildSystem interface. Build system plugins are located in <code>buildtools/generic/buildsystem</code>.
     .
   - QMake build tool
     - see TrollProjectPart at <code>buildtools/qmake</code>