Rename some instances of kde to tde in Ubuntu and Debian

1 files changed, 10 insertions, 10 deletions

diff --git a/ubuntu/maverick/tdelibs/debian/man/kdeinit-trinity.1 b/ubuntu/maverick/tdelibs/debian/man/kdeinit-trinity.1
index 1e1e10adf..1c3861783 100644
--- a/ubuntu/maverick/tdelibs/debian/man/kdeinit-trinity.1
+++ b/ubuntu/maverick/tdelibs/debian/man/kdeinit-trinity.1
@@ -1,21 +1,21 @@
 .\" This file was generated by (a slightly modified) kdemangen.pl and edited by hand
-.TH KDEINIT 1 "Jun 2006" "K Desktop Environment" "process launcher"
+.TH TDEINIT 1 "Jun 2006" "K Desktop Environment" "process launcher"
 .SH NAME
-kdeinit
+tdeinit
 \- KDE process launcher
 .SH SYNOPSIS
-\fBkdeinit\fP [options]
+\fBtdeinit\fP [options]
 .SH DESCRIPTION
-\fBkdeinit\fP is a process launcher similar to \fBinit\fP used for booting UNIX.
+\fBtdeinit\fP is a process launcher similar to \fBinit\fP used for booting UNIX.
 .sp 1
-\fBkdeinit\fP is used to start all other KDE programs. It can start binary program files as well as kdeinit loadable modules (KLMs).
+\fBtdeinit\fP is used to start all other KDE programs. It can start binary program files as well as tdeinit loadable modules (KLMs).
 .sp 1
-When \fBkdeinit\fP starts for the first time it launches \fBdcopserver\fP, \fBklauncher\fP, \fBkded\fP and some additional programs specified on its command line in the \fBstartkde\fP script (normally \fBkcminit\fP and \fBknotify\fP).
+When \fBtdeinit\fP starts for the first time it launches \fBdcopserver\fP, \fBklauncher\fP, \fBkded\fP and some additional programs specified on its command line in the \fBstartkde\fP script (normally \fBkcminit\fP and \fBknotify\fP).
 .sp 1
-The \fBkdeinit\fP master process can be used to start additional KDE programs via \fBkdeinit_wrapper\fP, \fBkshell\fP and \fBkwrapper\fP.
+The \fBtdeinit\fP master process can be used to start additional KDE programs via \fBtdeinit_wrapper\fP, \fBkshell\fP and \fBkwrapper\fP.
 .sp 1
 KLMs are dynamic libraries that work like binary programs but can be started more efficiently.
-Starting KLMs via \fBkdeinit\fP is much faster and more memory efficient because \fBkdeinit\fP is linked against all libraries a standard KDE application needs. To start a KLM \fBkdeinit\fP forks and loads the dynamic library.
+Starting KLMs via \fBtdeinit\fP is much faster and more memory efficient because \fBtdeinit\fP is linked against all libraries a standard KDE application needs. To start a KLM \fBtdeinit\fP forks and loads the dynamic library.
 .SH OPTIONS
 .TP
 .B \-\-no\-kded
@@ -27,9 +27,9 @@ Terminate when no KDE applications are left running
 .SH FILES
 .TP
 .I /usr/lib/trinity
-directory with KLMs (kdeinit loadable modules)
+directory with KLMs (tdeinit loadable modules)
 .SH SEE ALSO
-.BR dcopserver (1),\  kded (1),\  kcminit (1),\  kdeinit_wrapper (1),\  klauncher (1),\  kshell (1),\  kwrapper (1),\  startkde (1)
+.BR dcopserver (1),\  kded (1),\  kcminit (1),\  tdeinit_wrapper (1),\  klauncher (1),\  kshell (1),\  kwrapper (1),\  startkde (1)
 .SH AUTHORS
 .nf
 Waldo Bastian <bastian@kde.org>