summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2014-06-08 17:25:00 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2014-06-08 17:25:00 +0900
commit1ffbd5dc64bf39f6a41e8ec99d8a4c1d34ba50fe (patch)
tree726d4172a7a2ecad8a9898a50761e2344629c670
parent869412aa4d10b5229fea732bc99ddd6a358f1f56 (diff)
downloadpytdeextensions-1ffbd5dc.tar.gz
pytdeextensions-1ffbd5dc.zip
Rebranding: TDE Control Center --> Trinity Control Center
-rw-r--r--doc/en/index.docbook8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/en/index.docbook b/doc/en/index.docbook
index fc64296..f6da2f0 100644
--- a/doc/en/index.docbook
+++ b/doc/en/index.docbook
@@ -368,9 +368,9 @@ needed by the application at runtime.
<!-- Kcontrol modules -->
<chapter id="kcontrol-modules">
-<title>TDE Control Center Modules</title>
+<title>Trinity Control Center Modules</title>
<para>
-&appname; can also help create modules for the TDE Control Center.
+&appname; can also help create modules for the Trinity Control Center.
C++ glue code is needed when writing in module in Python. Fortunately
&appname; can generate this glue for you automatically.
</para>
@@ -402,7 +402,7 @@ design a KControl module that fits into the rest of TDE.
<para>
&appname; typically installs the <literal role="extension">.desktop</literal>
file into the <filename>/usr/share/applications/tde/</filename> directory.
-This is normally enough to make the module appear in the TDE Control Center.
+This is normally enough to make the module appear in the Trinity Control Center.
But for some distributions, most notably <ulink url="http://www.mandriva.com/">
Mandriva</ulink> but probably others too, this isn't enough. Mandriva in
particular uses the <ulink url="http://alioth.debian.org/projects/menu/">
@@ -572,7 +572,7 @@ are defined using XML.
<title>Kcontrol Module Application Template</title>
<para>
The <filename>kcontrol_module</filename> application template is a simple
-module for the TDE Control Center. The module can also be run as a separate
+module for the Trinity Control Center. The module can also be run as a separate
application outside of KControl to ease development and debugging.
</para>
</sect1>