14 files changed, 74 insertions, 71 deletions
diff --git a/doc/api/Architecture.dox b/doc/api/Architecture.dox
index ae4ef73d..ccf09093 100644
--- a/doc/api/Architecture.dox
+++ b/doc/api/Architecture.dox
@@ -1,15 +1,15 @@
 /** \file  Architecture.dox
-  * \brief KDevelop architecture
+  * \brief TDevelop architecture
   */
 
-/** \page architecture KDevelop 3 Architecture
+/** \page architecture TDevelop 3 Architecture
 
-KDevelop uses a plugin based architecture. This will be explained in more
+TDevelop uses a plugin based architecture. This will be explained in more
 detail in the next sections. To add a new plugin check the \ref howToAddPlugins page.
 
 \section devteammodel Development Team cooperation model
 
-KDevelop is the result of the work of many people. To help syncronize the effords and to automate
+TDevelop is the result of the work of many people. To help syncronize the effords and to automate
 some tasks, the team uses many tools:
 
   - CVS servers
@@ -22,7 +22,7 @@ some tasks, the team uses many tools:
   - LXR
   - E-mail :)
   - Cron Jobs
-  - and of course KDevelop :)
+  - and of course TDevelop :)
   .
 
 They get interconnected like this:
@@ -34,11 +34,11 @@ They get interconnected like this:
 
 \subsection source-division Main Source Divisions
 
-The KDevelop 3 source is divided into several parts which correspond to
-subdirectories in the KDevelop project directory. There are several main
+The TDevelop 3 source is divided into several parts which correspond to
+subdirectories in the TDevelop project directory. There are several main
 parts to distinguish, mainly:
 
-  - src            = The core part of KDevelop
+  - src            = The core part of TDevelop
   - lib/interfaces = Plugin handler interface classes
   - parts          = The various parts using the KParts framework ( KDevPlugin children )
   - languages      = \ref language-parts
@@ -51,7 +51,7 @@ parts to distinguish, mainly:
 
 This image is not complete there are parts that are not displayed. See below for a more detailed description.
 
-\subsection core-part The Core Part of KDevelop
+\subsection core-part The Core Part of TDevelop
 
 \subsubsection mainwindows Main Window Objects
 
@@ -72,11 +72,11 @@ access to common window features.
 
 \subsubsection toplevel The TopLevel Object
 
-There is only one toplevel object of class KDevMainWindow in KDevelop. It can
+There is only one toplevel object of class KDevMainWindow in TDevelop. It can
 be accessed through the static function TopLevel::getInstance() (see the
 TopLevel class).
 
-\subsection parts-overview KDevelop Parts Overview
+\subsection parts-overview TDevelop Parts Overview
 
 All parts reside in dedicated subdirectories acording to their function. They can
 be viewed according to their functionalities as follows.
@@ -85,7 +85,7 @@ be viewed according to their functionalities as follows.
 
 These parts implement a KDevLanguageSupport Class interface.
 To add support for a new programming language check the \ref howToAddProgrammingLanguages page (doc/api/HowToAddProgrammingLanguages.dox file).
-Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to see the current status/features of the programming languages currently supported by KDevelop.
+Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to see the current status/features of the programming languages currently supported by TDevelop.
 
   - languages/ada = Support for Ada
     - (see AdaSupportPart)
@@ -192,7 +192,7 @@ These parts implement a KDevVersionControl Class interface.
 \subsubsection editor-parts editor support Specific Parts
 
 These parts implement a KTextEditor Class interface.
-Take a look at \ref EditorsSupportStatus (doc/api/EditorsSupportStatus.dox file) to see the current status/features of the editors currently supported by KDevelop.
+Take a look at \ref EditorsSupportStatus (doc/api/EditorsSupportStatus.dox file) to see the current status/features of the editors currently supported by TDevelop.
 
   - editors/editor-chooser = Chooses an internal text editor
     - (see EditorChooserPart)
@@ -209,7 +209,7 @@ Take a look at \ref EditorsSupportStatus (doc/api/EditorsSupportStatus.dox file)
 \subsubsection global-parts Global Parts
 
 Some of the parts are considered global - that is, they effect the entire
-operation of KDevelop.
+operation of TDevelop.
 
 These parts implement a KDevPlugin Class interface.
 
diff --git a/doc/api/EditorsSupportStatus.dox b/doc/api/EditorsSupportStatus.dox
index e826471c..41a72314 100644
--- a/doc/api/EditorsSupportStatus.dox
+++ b/doc/api/EditorsSupportStatus.dox
@@ -4,9 +4,9 @@
 
 /** \page EditorsSupportStatus Editors Support Status
 
-Kate and Kvim are part of KDE and KDevelop just uses them.
+Kate and Kvim are part of KDE and TDevelop just uses them.
 
-qeditor and Nedit are interfaced via KDevelop's code. You can look at their code at <code>editors/qeditor</code> and <code>editors/nedit</code>.
+qeditor and Nedit are interfaced via TDevelop's code. You can look at their code at <code>editors/qeditor</code> and <code>editors/nedit</code>.
 
 <table border="1" style="text-align: left; margin-left: auto; margin-right: auto;" cellpadding="2" cellspacing="2">
     <tr>
diff --git a/doc/api/FutureTasks.dox b/doc/api/FutureTasks.dox
index 1d7f7f26..dbf81c66 100644
--- a/doc/api/FutureTasks.dox
+++ b/doc/api/FutureTasks.dox
@@ -1,7 +1,7 @@
 /** \file FutureTasks.dox
-  * \brief Future tasks and ideas for the next release of KDevelop
+  * \brief Future tasks and ideas for the next release of TDevelop
   */
-/** \page FutureTasks Future tasks and ideas for the next release of KDevelop
+/** \page FutureTasks Future tasks and ideas for the next release of TDevelop
 
 \section codereftodo Code Refactoring / Improvements:
 
@@ -20,7 +20,7 @@
         tool (qmake, automake,...?), etc.., too.
     - use mimetype to determine code files, not extension
       (see bug #
-    - Make the help buttons (that we already have) open the KDevelop Handbook on
+    - Make the help buttons (that we already have) open the TDevelop Handbook on
       the correct page (or the index if the subject is not covered yet).
     - New and improved VCS framework (Needs better description)
     - Another look at the plugin system (Nees better description)
diff --git a/doc/api/HighPriTasks.dox b/doc/api/HighPriTasks.dox
index 062b3b06..850053f9 100644
--- a/doc/api/HighPriTasks.dox
+++ b/doc/api/HighPriTasks.dox
@@ -12,8 +12,8 @@
     This way the .tdevelop file can be shared in teams of developers.
 
 
-\section KDevelop2compat KDevelop 2 compatibility
-(These are things that must be accomplished before we can say that KDevelop 3
+\section TDevelop2compat TDevelop 2 compatibility
+(These are things that must be accomplished before we can say that TDevelop 3
 &gt;= tdevelop 2.x UI-wise and functionality-wise!)
 
   - general UI issues:
diff --git a/doc/api/HowToAddApplicationTemplates.dox b/doc/api/HowToAddApplicationTemplates.dox
index f53ce4f8..4b77b9e2 100644
--- a/doc/api/HowToAddApplicationTemplates.dox
+++ b/doc/api/HowToAddApplicationTemplates.dox
@@ -162,13 +162,13 @@ echo "done"
 \n
 \attention Please test your template whether it installs and behaves correctly! Test, test and test again! ;)
 
-\section templates_3 III. How To Add The Template To KDevelop CVS HEAD
+\section templates_3 III. How To Add The Template To TDevelop CVS HEAD
 
 This section is for tdevelop developers only. Most probably you don't have to read this!.\n
 Move the directory <code>"template-khello"</code> to <code>tdevelop/languages/cpp/app_templates/</code>
 and then add the following files in <code>tdevelop/languages/cpp/app_templates/template-khello/</code>
 (in this example the language is c++ if you use other language replace cpp with the language name):
-    - <code>".kdev_ignore"</code> is an empty file. It prevents KDevelop's
+    - <code>".kdev_ignore"</code> is an empty file. It prevents TDevelop's
     C++-parser from parsing the C++ template files. This is necessary because the template files are just code templates and not real code (yet).
     - <code>".cvsignore"</code> looks like this:
 \code
diff --git a/doc/api/HowToAddFileTemplates.dox b/doc/api/HowToAddFileTemplates.dox
index fa6e630b..cb9ee17b 100644
--- a/doc/api/HowToAddFileTemplates.dox
+++ b/doc/api/HowToAddFileTemplates.dox
@@ -14,15 +14,15 @@ source files.
 
 Sometimes, different 'flavours' of template are required for a particular file type. In these
 instances, 'subtypes' can be defined to allow several different templates for a file type. An example
-of this are QT designer '.ui' files. KDevelop supplies several different templates for .ui
+of this are QT designer '.ui' files. TDevelop supplies several different templates for .ui
 files. Subtypes are named by the file type extension followed by a hyphen followed by an identifier
 for the subtype. E.g. ui-widget, ui-dialog
 
 The description of the prototypes is placed in <code>parts/filecreate/template-info.xml</code>. This
 file is fairly self-explanatory if you take a look at it.
 
-Note that templates and templates information can be edited within KDevelop itself. The global
-templates that can be made available to any project can be changed in Settings / Configure KDevelop... / New File
+Note that templates and templates information can be edited within TDevelop itself. The global
+templates that can be made available to any project can be changed in Settings / Configure TDevelop... / New File
 Wizard; and project related settings can be changed in Project / Project Options / New File Wizard.
 
 That's all! :)
diff --git a/doc/api/HowToAddGenericBuildTools.dox b/doc/api/HowToAddGenericBuildTools.dox
index b073cf0f..ce5d045e 100644
--- a/doc/api/HowToAddGenericBuildTools.dox
+++ b/doc/api/HowToAddGenericBuildTools.dox
@@ -11,7 +11,7 @@ Build system plugins are located in buildtools/generic/buildsystem.
 
 \section sectionStep1 Step 1: Make your plugin loadable
 
-For a plugin <code>foo</code>, create a file <code>foo.desktop</code> which contains KDevelop/Part in its list of ServiceTypes.
+For a plugin <code>foo</code>, create a file <code>foo.desktop</code> which contains TDevelop/Part in its list of ServiceTypes.
 
 The rest of this document is to be written.
 
diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox
index fa7f74e2..012cb5d0 100644
--- a/doc/api/HowToAddPlugins.dox
+++ b/doc/api/HowToAddPlugins.dox
@@ -1,12 +1,12 @@
 /** \file HowToAddPlugins.dox
-  * \brief How to extend KDevelop via plugins
+  * \brief How to extend TDevelop via plugins
   */
 
-/** \page howToAddPlugins How to extend KDevelop via plugins
+/** \page howToAddPlugins How to extend TDevelop via plugins
 
 \section createDesktop Step 1: Make your plugin loadable
 
-For a plugin <code>foo</code>, create a file <code>foo.desktop</code> which contains KDevelop/Part in its list of ServiceTypes.
+For a plugin <code>foo</code>, create a file <code>foo.desktop</code> which contains TDevelop/Part in its list of ServiceTypes.
 
   - See <code>parts/doctreeview/kdevdoctreeview.desktop</code> for an example.
   .
@@ -118,7 +118,7 @@ Take attention to the issue that the project file usually is shared in a team of
 developers (e.g. via version control application CVS). So some user preferences might be
 very individual, and some may be valid for all of the team - project-wide so to speak.
 
-That's why the KDevelop architecture makes a difference here and supports two files
+That's why the TDevelop architecture makes a difference here and supports two files
 which will be stored in the project root directory. They are the project file (*.tdevelop)
 and the session (*.kdevses) file. The later is for individual settings, not to be thought
 to be shared.
@@ -159,7 +159,7 @@ The base class of all TDevelop plugins is KDevPlugin. It provides two virtual me
 restorePartialProjectSession(..) and savePartialProjectSession(..)
 that you should reimplement in your special plugin to attach to session loading and saving.
 
-When KDevelop loads or closes a project, the program's project session manager
+When TDevelop loads or closes a project, the program's project session manager
 (class ProjectSession) calls them for each plugin. That manager gives a QDOM node to the
 plugin where it can read out or build up its partial DOM subtree with the session settings.
 That subtree will be stored in the .kdevses file by that session manager.
diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox
index a5840885..1926d811 100644
--- a/doc/api/HowToAddProgrammingLanguages.dox
+++ b/doc/api/HowToAddProgrammingLanguages.dox
@@ -4,7 +4,7 @@
 
 /** \page howToAddProgrammingLanguages How to add support for a programming language
 
-\section LSupport List of things to have "complete" support of a given language in KDevelop
+\section LSupport List of things to have "complete" support of a given language in TDevelop
 
   - Implement interface KDevLanguageSupport
   - \ref sectionClassWizard
@@ -30,12 +30,12 @@
   - \ref sectionCompilerPlugins
   .
 
-List of optional things to support a given language in KDevelop:
+List of optional things to support a given language in TDevelop:
   - \ref sectionEditor - Syntax highlighter - (add to QEditor if not available elsewhere)
   - \ref sectionBuildTool (make/ant/etc)
   .
 
-Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to see the current status/features of the programming languages currently supported by KDevelop.
+Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to see the current status/features of the programming languages currently supported by TDevelop.
 
 
 
@@ -52,8 +52,8 @@ Implementing methods:
 
 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.
+TDevelop ships with KDevLang project template. It is a simple language support prototype that can be used when developing language support plugins with TDevelop.
+To use it, start a New Project and select: <code>C++->TDevelop->TDevelop 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.
 
 
@@ -93,7 +93,7 @@ See <code>cpp</code> and <code>java</code> for examples.
 
 In general, class stores can be filled with information without specialized
 and complex language parsers (take a look at <code>languages/python</code> that have a very simple python parser) but your language support will surely benefit
-from having such. There is a hand-written c/c++ parser (<code>lib/cppparser</code>) in KDevelop that might be used for ObjC or related C-based languages.
+from having such. There is a hand-written c/c++ parser (<code>lib/cppparser</code>) in TDevelop that might be used for ObjC or related C-based languages.
 
 Other (not so complex as c++) languages can be parsed by ANTLR based parsers (library is in lib/antlr).
 Consult www.antlr.org for a ANTLR documentation and look at <code>languages/java</code>, <code>languages/ada</code> and <code>languages/pascal</code> for an example of using such parsers.
@@ -106,13 +106,13 @@ If you write (or have) a language parser, your language support can have
 and methods - their names, names of source files, location in source files,
 etc.). Class store libraries can be found at <code>lib/catalog</code> (Catalog) and <code>lib/interfaces</code> (CodeModel).
 
-KDevelop provides class browsers that extract information from a <b>class store</b> and display it in a tree view and toolbar selectors of scopes, classes and methods.
+TDevelop provides class browsers that extract information from a <b>class store</b> and display it in a tree view and toolbar selectors of scopes, classes and methods.
 
 \subsubsection sectionMemoryClassStore Memory class store
 CodeModel is the memory class store. It is very efficient and thus it is recommended for using as a project class store. CodeModel libraries are located in <code>lib/interfaces/codemodel.h</code>. The class browser for a CodeModel based stores is <code>parts/classview</code>.
 
 \subsubsection sectionPersistantClassStore Persistant class store
-Catalog is the persistant class store for KDevelop. Persistant class store can be used as an information storage for code completion but it also can be used as a class store for the project. Take a look at
+Catalog is the persistant class store for TDevelop. Persistant class store can be used as an information storage for code completion but it also can be used as a class store for the project. Take a look at
 <code>languages/cpp</code> for an example of using catalog. Catalog is stored on disk in the database file (Berkeley db) If you use catalog with the project, your class browser will be <code>parts/classbrowser</code>.
 
 \subsection sectionCodeCompletion Code completion
@@ -136,12 +136,12 @@ and look at <code>languages/ruby/app_templates/rubyhello</code>, <code>languages
 
 \subsubsection sectionApplicationImportTemplates Application import templates
 
-KDevelop has the ability to <b>create a new project from existing projects or source code</b>.
+TDevelop has the ability to <b>create a new project from existing projects or source code</b>.
 It scans for project files ('*.tdevelop, *.kdevprj, *.studio, *.pro) and if
   - it finds a project it extracts the necessary information
   - it does not find project files it scans for source files (*.cpp, *.java, *.pl, *.py, ...)
   .
-and creates a new KDevelop project in the direcotry the user has chosen.
+and creates a new TDevelop project in the direcotry the user has chosen.
 
 \subsubsection sectionSourceFileTemplates Source file templates
 
@@ -153,14 +153,14 @@ Consult FileCreatePart (parts/filecreate/README.dox file) and \ref howToAddFileT
 
 \subsubsection sectionAbbreviationTemplates Code abbreviation templates
 
-KDevelop has a support for <b>code abbreviations</b> so you can add some predefined abbreviations to your language support. Take <code>languages/cpp/cpptemplates</code> as an example.
+TDevelop has a support for <b>code abbreviations</b> so you can add some predefined abbreviations to your language support. Take <code>languages/cpp/cpptemplates</code> as an example.
 
 
 \subsection sectionSourceCodeFormater Source code formater
 
 Implement a KDevSourceFormater class interface.
 To obtain source formater functionality (that is already available to
-c-based languages) you can extend astyle library (<code>lib/astyle</code>) that is used by KDevelop to format sources.
+c-based languages) you can extend astyle library (<code>lib/astyle</code>) that is used by TDevelop to format sources.
 Take a look at AStylePart for an example how to do it.
 
 \subsection sectionDocumentationTopics Documentation topics
@@ -170,13 +170,13 @@ In the end you need to edit the <code>languages/YOURLANGUAGE/doc/Makefile.am</co
 
 \subsection sectionDebugger Debugger
 
-The last thing to have a complete language support in KDevelop is to
-write a <b>Debugger </b>. KDevelop already provides GDB support
+The last thing to have a complete language support in TDevelop is to
+write a <b>Debugger </b>. TDevelop already provides GDB support
 (<code>languages/cpp/debugger</code>) and JDB (java debugger) support (<code>languages/java/debugger</code>). Take a look at them to get inspiration.
 
 \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.
+There is an ability to create compiler plugin for TDevelop. Compiler plugin provides the compiler configuration dialog which implements command line compiler options.
 Compiler plugins must implement KDevCompilerOptions interface.
 
 
@@ -192,14 +192,14 @@ See also \ref howToAddPlugins (doc/api/HowToAddPlugins.dox file) for an informat
 
 \section sectionEditor Language Editor
 
-To edit source files KDevelop uses any editor that supports the KTextEditor
+To edit source files TDevelop uses any editor that supports the KTextEditor
 interface. The current supported editors and their features are listed
 in the \ref EditorsSupportStatus (doc/api/EditorsSupportStatus.dox file) page.
 
 In case none of the editors does support advanced editing of sources
 written in your language (like code folding, syntax highlighting, line
-indentation) you can improve QEditor included in KDevelop (<code>editors/qeditor</code>).
-By creating QEditorIndenter and QSourceColorizer descendants you can provide the support for an automatic indentation and syntax highlighting that will be available for sure in KDevelop.
+indentation) you can improve QEditor included in TDevelop (<code>editors/qeditor</code>).
+By creating QEditorIndenter and QSourceColorizer descendants you can provide the support for an automatic indentation and syntax highlighting that will be available for sure in TDevelop.
 
 
 
@@ -209,7 +209,7 @@ By creating QEditorIndenter and QSourceColorizer descendants you can provide the
 \section sectionBuildTool Build Tool
 
 The language support is important, but it is unusable without a <b>build tool</b>
-that can manage projects written on this language. KDevelop
+that can manage projects written on this language. TDevelop
 currently provides several build tools. They are:
 
   - ANT build tool
diff --git a/doc/api/HowToDocument.dox b/doc/api/HowToDocument.dox
index d606a8bf..d7fa3680 100644
--- a/doc/api/HowToDocument.dox
+++ b/doc/api/HowToDocument.dox
@@ -1,13 +1,13 @@
 /** \file HowToDocument.dox
-  * \brief How to document KDevelop parts
+  * \brief How to document TDevelop parts
   */
-/** \page howToDocument How to document KDevelop parts
+/** \page howToDocument How to document TDevelop parts
 
 You should add a README and a README.dox file to your part (KDevPlugin).
 
 On the README file put this text:
 \verbatim
-Please read the on-line, automaticaly updated KDevelop API documentation at:
+Please read the on-line, automaticaly updated TDevelop API documentation at:
 http://www.kdevelop.org
 or read the README.dox file.
 \endverbatim
diff --git a/doc/api/LangSupportStatus.dox b/doc/api/LangSupportStatus.dox
index fa08cc67..967bd886 100644
--- a/doc/api/LangSupportStatus.dox
+++ b/doc/api/LangSupportStatus.dox
@@ -318,7 +318,7 @@ Legend:
     </tr>
     <tr>
       <td>cppparser</td>
-      <td>New c/c++ parser written by Roberto Raggi for KDevelop</td>
+      <td>New c/c++ parser written by Roberto Raggi for TDevelop</td>
     </tr>
     <tr>
       <td>Internal</td>
diff --git a/doc/api/Mainpage.dox b/doc/api/Mainpage.dox
index 262cd2ed..f399fb40 100644
--- a/doc/api/Mainpage.dox
+++ b/doc/api/Mainpage.dox
@@ -3,24 +3,24 @@
 */
 
 /**
-\mainpage The KDevelop %API %Documentation
+\mainpage The TDevelop %API %Documentation
 
-KDevelop is an easy to use IDE (Integrated Development Environment) for developing applications under X11.
+TDevelop is an easy to use IDE (Integrated Development Environment) for developing applications under X11.
 
 \section intro Introduction
 
-This document is targeted at all those that want to add or improve KDevelop's source code.
-If you are instead looking for a user manual, just go to the help menu of your KDevelop and select KDevelop handbook.
-This documentation contains the KDevelop online class reference for the current
-development version of KDevelop.  Additionally, you
+This document is targeted at all those that want to add or improve TDevelop's source code.
+If you are instead looking for a user manual, just go to the help menu of your TDevelop and select TDevelop handbook.
+This documentation contains the TDevelop online class reference for the current
+development version of TDevelop.  Additionally, you
 can subscribe or read the <a href="http://www.kdevelop.org/index.html?filename=mailinglist.html">mailing list</a> for any additions and/or
 modifications to the %API.
 
 An on-line, updated every 24H, html version of this documentation can be found at: http://www.kdevelop.org/HEAD/doc/api/html/index.html
 
-More information about the KDevelop architecture in form of tutorials, HOWTOs,
+More information about the TDevelop architecture in form of tutorials, HOWTOs,
 and FAQs can be found at
-the <a href="http://www.kdevelop.org">KDevelop website</a>.
+the <a href="http://www.kdevelop.org">TDevelop website</a>.
 
 
 \section status Current Status
@@ -29,9 +29,9 @@ Here you can see the current \ref requirements and the \ref features.
 There is also a \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) page and a \ref EditorsSupportStatus (doc/api/EditorsSupportStatus.dox file) page.
 
 
-\section expand How to expand KDevelop
+\section expand How to expand TDevelop
 
-First of all read the \ref architecture (doc/api/Architecture.dox file) then you can find more information on how to expand KDevelop:
+First of all read the \ref architecture (doc/api/Architecture.dox file) then you can find more information on how to expand TDevelop:
   - \ref howToAddPlugins (doc/api/HowToAddPlugins.dox file)
   - \ref howToAddProgrammingLanguages (doc/api/HowToAddProgrammingLanguages.dox file)
   - \ref howToAddApplicationTemplates (doc/api/HowToAddApplicationTemplates.dox file)
@@ -49,8 +49,8 @@ Here is a priority ordered list:
   -# fix the bugs in the \ref bug
   -# fix the dispersed \ref todo all over the code.
   .
-There are some \ref unmaintained parts in KDevelop. You migth want to "adopt" one. :)\n
-There is also \ref FutureTasks (doc/api/FutureTasks.dox file). Put all ideas for the future KDevelop releases there. It is also a good place to comment on those ideas.
+There are some \ref unmaintained parts in TDevelop. You migth want to "adopt" one. :)\n
+There is also \ref FutureTasks (doc/api/FutureTasks.dox file). Put all ideas for the future TDevelop releases there. It is also a good place to comment on those ideas.
 
 \section misc Misc
 
@@ -59,7 +59,7 @@ There is also \ref FutureTasks (doc/api/FutureTasks.dox file). Put all ideas for
   - \ref FAQ
   - \ref deprecated
 
-\section misc_libs Miscellaneous libraries included in KDevelop
+\section misc_libs Miscellaneous libraries included in TDevelop
   - \ref PropEditor
 
 \section howTobuildAPIlocalcopy How to build a local copy of this documentation
diff --git a/doc/api/Makefile.am b/doc/api/Makefile.am
new file mode 100644
index 00000000..14b399c7
--- /dev/null
+++ b/doc/api/Makefile.am
@@ -0,0 +1,3 @@
+DOXYGEN_PROJECTNAME = TDevelop API Documentation 
+DOXYGEN_DOCDIRPREFIX = kdev
+include ../../Doxyfile.am
diff --git a/doc/api/PropEditor.dox b/doc/api/PropEditor.dox
index 676e634c..40ce4261 100644
--- a/doc/api/PropEditor.dox
+++ b/doc/api/PropEditor.dox
@@ -1,8 +1,8 @@
 /** \file PropEditor.dox
-    \brief The KDevelop Property Editor library description page
+    \brief The TDevelop Property Editor library description page
 */
 
-/** \page PropEditor KDevelop Property Editor library description
+/** \page PropEditor TDevelop Property Editor library description
 
 \section whatis What is Property Editor?
 
@@ -10,7 +10,7 @@
 properties of an object. For example, look at %Qt Designer. Each widget
 has a list of properties that can be edited in a nice table form.
 Same ideology is used to edit properties in Kugar Report Designer
-(from KOffice distribution). In KDevelop project manager can also display
+(from KOffice distribution). In TDevelop project manager can also display
 the properties of currently selected build item in property editor.
 
 \section over Library Overview