Fix help files, kdevelop->tdevelop branding, fix startup.

4 files changed, 6 insertions, 6 deletions

diff --git a/doc/tdevelop/listplugins.sh b/doc/tdevelop/listplugins.sh
index f916b7fe..22251293 100755
--- a/doc/tdevelop/listplugins.sh
+++ b/doc/tdevelop/listplugins.sh
@@ -26,7 +26,7 @@ for defscope in Core Global Project; do
 	# echo $dfile | wc -w
 	if [ `echo $dfile | wc -w` -gt 1 ]; then continue; fi
 	if [ ! -f $dfile ]; then continue; fi
-	scope=`cat $dfile | grep "X-KDevelop-Scope=" | cut -d= -f2-`
+	scope=`cat $dfile | grep "X-TDevelop-Scope=" | cut -d= -f2-`
 	if [ $scope != $defscope ]; then continue; fi
 	comment=`cat $dfile | grep "Comment=" | cut -d= -f2-`
 	name=`cat $dfile | egrep "^Name=" | cut -d= -f2- | tr " " _`
diff --git a/doc/tdevelop/plugin-tools.docbook b/doc/tdevelop/plugin-tools.docbook
index 35e2c206..a05c1e7c 100644
--- a/doc/tdevelop/plugin-tools.docbook
+++ b/doc/tdevelop/plugin-tools.docbook
@@ -18,8 +18,8 @@ it's enabled in the Project - Project Options dialog.
 lib/interfaces/kdevplugin.h. The following is taken from a comment from there.</para>
 
 <para> 
-KDevPlugin is the base class for all KDevelop plugins.
-A plugin is a component which is loaded into KDevelop shell at startup or by request.
+KDevPlugin is the base class for all TDevelop plugins.
+A plugin is a component which is loaded into TDevelop shell at startup or by request.
 A plugin has a scope that can be either:
 <itemizedlist>
 <listitem><simpara>Core</simpara></listitem>
diff --git a/doc/tdevelop/project-management.docbook b/doc/tdevelop/project-management.docbook
index 69ca9474..e70d07dc 100644
--- a/doc/tdevelop/project-management.docbook
+++ b/doc/tdevelop/project-management.docbook
@@ -126,7 +126,7 @@ One of these four alternatives must be chosen when you create a project and <emp
 There are several tutorials available on the &GNU; Build System (<command>Autoconf</command>, <command>Automake</command> and <command>Libtool</command>) of which the &automanag; makes use.
 </para>
 <itemizedlist>
-  <listitem><para>A short <ulink url="http://www.tdevelop.org/index.html?filename=tutorial_autoconf.html">autoconf tutorial</ulink> written by Christopher W. Curtis available on the &tdevelop; home page. It concentrates on some basic steps to modify a <filename>Makefile</filename>.
+  <listitem><para>A short <ulink url="http://www.kdevelop.org/index.html?filename=tutorial_autoconf.html">autoconf tutorial</ulink> written by Christopher W. Curtis available on the &tdevelop; home page. It concentrates on some basic steps to modify a <filename>Makefile</filename>.
   </para></listitem>
   <listitem><para>
   A more detailed tutorial can be found in a greater set of tutorials on  <ulink url="http://www.amath.washington.edu/~lf/tutorials/autoconf/toolsmanual_toc.html"><quote>Developing software with GNU</quote></ulink>.
diff --git a/doc/tdevelop/tdevelop-install.docbook b/doc/tdevelop/tdevelop-install.docbook
index 05f6ef5a..5e07b0b6 100644
--- a/doc/tdevelop/tdevelop-install.docbook
+++ b/doc/tdevelop/tdevelop-install.docbook
@@ -45,7 +45,7 @@ In this chapter we will discuss the steps necessary to compile and install the &
 &tdevelop; is available in binary form from many different &Linux; distributions such as <!--&SuSE;, &RedHat;//--> SuSE, RedHat and others. These binaries are packed in some convenient format, mostly RPM, for easy installation. To install, follow the standard instructions given in your distribution.
 </para>
 <para>
-You may as well obtain the &tdevelop; sources, compile and install them by yourself. These sources can be found via the project home page at <ulink url="http://www.tdevelop.org"> http://www.tdevelop.org</ulink> or via the <ulink url="http://download.kde.org">&kde; ftp site</ulink>.
+You may as well obtain the &tdevelop; sources, compile and install them by yourself. These sources can be found via the project home page at <ulink url="http://www.kdevelop.org"> http://www.kdevelop.org</ulink> or via the <ulink url="http://download.kde.org">&kde; ftp site</ulink>.
 </para>
 
 <sect2 id="howto-svn">
@@ -699,7 +699,7 @@ The <command>kbuildsycoca</command> command does not run from within the root. Y
 API is the short form of <quote>Application Program Interface</quote>. Actually such an API cotains a series of descriptions (&ie; calling conventions) by which an application program can access the operating system and other services. In our context, however, a broader definition was adopted. The API of a &kde; or &Qt; application is an abstract of the classes and methods interfaces, a synopsis to be used like a dictionary to navigate the sources.
 </para>
 <para>
-There is a version of the most current API available at the <ulink url="http://www.tdevelop.org/HEAD/doc/api/html/index.html">KDevelop-Home website</ulink>. It will be automatically updated every 24 hours so you can keep up.
+There is a version of the most current API available at the <ulink url="http://www.kdevelop.org/HEAD/doc/api/html/index.html">KDevelop-Home website</ulink>. It will be automatically updated every 24 hours so you can keep up.
 </para>
 <para>
 Alas, this version is best used read-only over the internet. If you do not always have internet access you may as well build your own API documentation from the &tdevelop; sources. To do so, you must tell the automake system where to find the KDELIBS API in your system. This is accomplished by the special option <option>--with-tdelibsdoxy-dir</option> in the <command>configure</command> command when you prepare to compile the &tdevelop; sources: