9 files changed, 41 insertions, 41 deletions
diff --git a/doc/tdeprint/add-printer-wiz.docbook b/doc/tdeprint/add-printer-wiz.docbook
index 28d5791d2..176fc6371 100644
--- a/doc/tdeprint/add-printer-wiz.docbook
+++ b/doc/tdeprint/add-printer-wiz.docbook
@@ -1,7 +1,7 @@
 <chapter id="add-printer-wizard-2">
 <title>The <quote>Add Printer Wizard</quote> for &CUPS;</title>
 
-<para>Clicking on the leftmost icon on the toolbar
+<para>Clicking on the left-most icon on the toolbar
 <inlinemediaobject><imageobject> <imagedata
 fileref="cr32-action-wizard.png" format="PNG"/></imageobject>
 </inlinemediaobject> in the upper part of the window starts the
diff --git a/doc/tdeprint/cups-config.docbook b/doc/tdeprint/cups-config.docbook
index 304fe9514..3dba500c8 100644
--- a/doc/tdeprint/cups-config.docbook
+++ b/doc/tdeprint/cups-config.docbook
@@ -50,7 +50,7 @@ class="directory">/usr/share/doc/cups/</filename> or
 
 <para>For the best, most detailed and most recent information you should
 always refer to the original &CUPS; documentation.  &CUPS; is, much like
-&kde; in a rapid development process.  There are constantly new features
+&tde; in a rapid development process.  There are constantly new features
 being added. New features might for times be only configurable by
 directly editing the configuration files. The &tdeprint; &GUI; might not
 have caught up with &CUPS; development.</para>
diff --git a/doc/tdeprint/final-word.docbook b/doc/tdeprint/final-word.docbook
index 175afb2f1..86da77762 100644
--- a/doc/tdeprint/final-word.docbook
+++ b/doc/tdeprint/final-word.docbook
@@ -45,7 +45,7 @@ interested in &CUPS; <quote>backfired</quote> on me - one editor
 squeezed me into writing a series on the subject myself.  And this is
 how some people started to give me the nickname <quote>CUPS
 Evangelist</quote>. I will not get rid of this nick anytime soon, now
-that even the &kde; people wedged me into their timeframe of
+that even the &tde; people wedged me into their timeframe of
 releases. Oh, boy...</para>
 
 <para>Anyway, &CUPS; is now making its way around the world and it
@@ -56,7 +56,7 @@ supported and contributed to this from near the beginning.</para>
 users than you are skeptical about it, and even if your programming
 skills are next to zero (like mine) - there are a lot of tasks and
 jobs and ideas, and talent that you can contribute to the Free Software
-community. Not least within the &kde; project... ;-)
+community. Not least within the &tde; project... ;-)
 </para>
 
 </sect1>
@@ -82,7 +82,7 @@ and <application>qtcups</application>, the predecessors of
 </listitem>
 <listitem>
 <para>Sven Guckes for teaching me a few things about the art of <quote>survival
-on the terminal</quote> (just in case &kde; is not there ;-) )</para>
+on the terminal</quote> (just in case &tde; is not there ;-) )</para>
 </listitem>
 <listitem>
 <para>...too numerous others to mention who also let me snatch bits
diff --git a/doc/tdeprint/getting-started.docbook b/doc/tdeprint/getting-started.docbook
index 9ef1500b7..d1ed5bfd8 100644
--- a/doc/tdeprint/getting-started.docbook
+++ b/doc/tdeprint/getting-started.docbook
@@ -22,7 +22,7 @@ from the print dialog.</para>
 <guisubmenu>Preferences</guisubmenu> <guisubmenu>System</guisubmenu>
 <guimenuitem>Printing Manager</guimenuitem></menuchoice>.  At the bottom
 you can see a button that lets you select which printing subsystem you
-want to use.  In &kde; 2.2 you can choose from the following
+want to use.  In &tde; 2.2 you can choose from the following
 alternatives:</para>
 
 <itemizedlist>
@@ -75,7 +75,7 @@ your selection.  The author's personal recommendation is
 &CUPS;.</para>
 
 <para>Once autodetected, chosen, or changed, the active print
-subsystem will take effect for all &kde; applications.  Different
+subsystem will take effect for all &tde; applications.  Different
 users may have different print subsystems in use, if those do exist on
 the computer and are compliant with each other.  Their settings are
 stored in the <filename>tdeprintrc</filename>.  This file is unique to
diff --git a/doc/tdeprint/highlights.docbook b/doc/tdeprint/highlights.docbook
index 72982c10c..4e8a0af91 100644
--- a/doc/tdeprint/highlights.docbook
+++ b/doc/tdeprint/highlights.docbook
@@ -49,7 +49,7 @@ as never before on any &Linux;-like system.</para>
 <title>Full Print Job Control</title>
 
 <para>The Print Job Viewer is automatically started by &kprinter;.  It
-may be docked into the &kde; panel (in the system tray).  The Print Job
+may be docked into the &tde; panel (in the system tray).  The Print Job
 Viewer allows full job management, if supported by the print
 subsystem.</para>
 
@@ -142,9 +142,9 @@ Modules for other print subsystems, such as <acronym>PLP</acronym>,
 <acronym>PPR</acronym> and <acronym>PDQ</acronym> may be available
 later.</para>
 
-<para>&tdeprint; makes &kde; much more flexible.  It gives freedom of
-choice to &kde; 2.2 users.  To use different available print subsystems,
-these must, of course, be installed independently from &kde;.  In
+<para>&tdeprint; makes &tde; much more flexible.  It gives freedom of
+choice to &tde; 2.2 users.  To use different available print subsystems,
+these must, of course, be installed independently from &tde;.  In
 former versions, users were stuck with the old <acronym>LPD</acronym>
 style print subsystems.  Now they can even use &CUPS;. In the future,
 there will be easy integration of new subsystems, as they
@@ -159,7 +159,7 @@ appear on the scene.</para>
 <para>Some specific features of &tdeprint; depend on the chosen print
 subsystem.  This dependency might exist because those features are only
 implemented there; remember, &tdeprint; is an intermediate layer between
-&kde; applications, and the print subsystem, but it's no replacement for
+&tde; applications, and the print subsystem, but it's no replacement for
 any print subsystem by itself.  Such dependency may exist for another
 reason: that &tdeprint; has not yet implemented an interface to all the
 features of all the subsystems.</para>
@@ -327,11 +327,11 @@ Protocol, the newly emerging standard for the future of network
 printing. &CUPS; is clearly the print system of choice for Michael
 Goffioul, the principal &tdeprint; developer.</para>
 
-<para>Experienced &kde; users may already be familiar with Michael's
+<para>Experienced &tde; users may already be familiar with Michael's
 utilities <application>qtcups</application> and
 <application>kups</application> (co-developed with Jean-Eric Cuendet).
 These were, up until now, the graphical
-&GUI; front ends for &CUPS; with a strong relation to &kde;.</para>
+&GUI; front ends for &CUPS; with a strong relation to &tde;.</para>
 
 <sect2>
 <title><application>qtcups</application> and
@@ -364,7 +364,7 @@ restart it.</para>
 
 <para>The &CUPS; Module in &tdeprint; now contains all (and more)
 functions that were provided by <application>qtcups</application> and
-<application>kups</application> in former &kde; versions.</para>
+<application>kups</application> in former &tde; versions.</para>
 
 <para>Instead of <command>qtcups</command> you can now use the
 <command>kprinter</command> command.  And in place of
@@ -389,10 +389,10 @@ different default setting of print options.</para>
 print command</quote>, like <application>qtcups</application> did
 before.</para>
 
-<para>Use &kprinter; in any application, even a non-&kde;
+<para>Use &kprinter; in any application, even a non-&tde;
 application, that lets you configure your print command.  Examples of
 these are &Netscape; and <application>StarOffice</application>, but
-<emphasis>not</emphasis> most pre-&kde; 2.2 programs.</para>
+<emphasis>not</emphasis> most pre-&tde; 2.2 programs.</para>
 
 <para>A screenshot how to use the new <command>kprinter</command>
 print command instead of the old-fashioned <command>lpr</command>...
diff --git a/doc/tdeprint/index.docbook b/doc/tdeprint/index.docbook
index 70d9f8388..cc3eef929 100644
--- a/doc/tdeprint/index.docbook
+++ b/doc/tdeprint/index.docbook
@@ -73,8 +73,8 @@
 
 <abstract>
 <para>This handbook describes &tdeprint;. &tdeprint; is not a standalone
-program. It is the new printing framework for &kde; 2.2. &tdeprint;
-is an intermediate layer between &kde; (or other) applications and the selected
+program. It is the new printing framework for &tde; 2.2. &tdeprint;
+is an intermediate layer between &tde; (or other) applications and the selected
 (and installed) print subsystem of your OS (&OS;).</para>
 </abstract>
 
@@ -94,8 +94,8 @@ is an intermediate layer between &kde; (or other) applications and the selected
 <title>Introduction</title>
 
 <para>This handbook describes &tdeprint;. &tdeprint; is not a standalone
-program. It is the new printing framework for &kde; 2.2. &tdeprint;
-is an intermediate layer between &kde; (or other) applications and the selected
+program. It is the new printing framework for &tde; 2.2. &tdeprint;
+is an intermediate layer between &tde; (or other) applications and the selected
 (and installed) print subsystem of your OS (&OS;).</para>
 
 <para>It should be noted that both the developer of this application,
@@ -113,7 +113,7 @@ Manager</guilabel> module in &kcontrol;, and you will find its
 operation to hopefully be fairly self evident, no matter what printing
 subsystem you use.</para>
 
-<para>Lauri Watts, &kde; documentation team</para>
+<para>Lauri Watts, &tde; documentation team</para>
 
 <!-- Insert here screenshot : <steinbruch_scaled.png> -->
 
diff --git a/doc/tdeprint/lprng.docbook b/doc/tdeprint/lprng.docbook
index 78db2615b..c30391dab 100644
--- a/doc/tdeprint/lprng.docbook
+++ b/doc/tdeprint/lprng.docbook
@@ -2,6 +2,6 @@
 <title><application>LPRng</application></title>
 
 <para>An <application>LPRng</application> module for &tdeprint; is in
-development, and hopefully available for the &kde; 2.3 release.</para>
+development, and hopefully available for the &tde; 2.3 release.</para>
 
 </chapter>
diff --git a/doc/tdeprint/tech-overview.docbook b/doc/tdeprint/tech-overview.docbook
index 7a81a48a2..40eacc2d0 100644
--- a/doc/tdeprint/tech-overview.docbook
+++ b/doc/tdeprint/tech-overview.docbook
@@ -5,7 +5,7 @@
 non-programmers can comprehend.</para>
 
 <para>&tdeprint; is a new and revolutionary tool to give easy access to
-printing services for both &kde; users and &kde; developers.</para>
+printing services for both &tde; users and &tde; developers.</para>
 
 <sect1 id="brief-description">
 <title>A Brief Description of &tdeprint;</title>
@@ -30,17 +30,17 @@ other print data.</para>
 <title>What it <emphasis>is</emphasis></title>
 <para>&tdeprint; is an intermediate layer between the spooling and the
 data processing print subsystem (as installed), and the application that
-seeks to print.  &tdeprint; provides a common interface for &kde;
-developers and &kde; users, to various supported print subsystems.  At
+seeks to print.  &tdeprint; provides a common interface for &tde;
+developers and &tde; users, to various supported print subsystems.  At
 the same time, it is customizable, and highly configurable.</para>
 
-<para>&tdeprint; is easy to use for both &kde; developers and end-users.
+<para>&tdeprint; is easy to use for both &tde; developers and end-users.
 Developers can port their applications, with minimal changes, to use
 &tdeprint; instead of the old &Qt; print <quote>system</quote>. Users
 can easily choose and configure their print subsystem.</para>
 
-<para>For a reference to new &kde; users: &Qt; is the basic library and
-graphical toolkit, which is used by all &kde; applications; &Qt; is
+<para>For a reference to new &tde; users: &Qt; is the basic library and
+graphical toolkit, which is used by all &tde; applications; &Qt; is
 developed by TrollTech, a Norwegian software company.</para>
 
 </sect2>
@@ -58,7 +58,7 @@ developed by TrollTech, a Norwegian software company.</para>
 <para>&tdeprint; allows users and/or administrators, depending on their
 rights, access to printing subsystems (&CUPS;, <acronym>LPD</acronym>,
 <acronym>RLPR</acronym>, <application>LPRng</application>,
-<application>PDQ</application> &etc;) through a &kde; graphical user
+<application>PDQ</application> &etc;) through a &tde; graphical user
 interface (&GUI;).  Using &tdeprint;, they can print, administer jobs,
 printers and the printing daemon, all in a comfortable manner.</para>
 
@@ -72,10 +72,10 @@ on.</para>
 
 
 <sect2 id="what-developers-can-do">
-<title>What &kde; developers can do with it...</title>
+<title>What &tde; developers can do with it...</title>
 
-<para>If a &kde; developer needs printing access for his application, he
-does not code the printing functions from scratch. Before &kde; 2.2 this
+<para>If a &tde; developer needs printing access for his application, he
+does not code the printing functions from scratch. Before &tde; 2.2 this
 service was provided by the <classname>QPrinter</classname> class, a
 library function of the &Qt; Toolkit. The
 <classname>QPrinter</classname> class relied on the out-moded
@@ -86,7 +86,7 @@ compatibility with <acronym>LPD</acronym> and other legacy, or less
 elaborate, print systems. It also <quote>leaves the door open</quote>
 for any new development that might occur.</para>
 
-<para>For &kde; developers to use the new &tdeprint; class in their
+<para>For &tde; developers to use the new &tdeprint; class in their
 applications, they require only minimal changes to their code: for every
 call of <classname>QPrinter</classname>, they just need to change this to
 <classname>KPrinter</classname>.  Replacing one (!) letter in a few
@@ -101,7 +101,7 @@ extensions to the standard &tdeprint; will feel right at home.</para>
 
 
 <para>This last mentioned feature has not been used widely inside
-&kde; so far, as developers are not yet fully aware of &tdeprint;'s
+&tde; so far, as developers are not yet fully aware of &tdeprint;'s
 power. Expect more of this in the near future. One example I
 discovered is the &kcron; application. It lets you edit the crontab
 through a &GUI;. The developers have implemented a printing feature
@@ -113,7 +113,7 @@ in the following screenshots.</para>
 <para>This shot shows a sample from the &kcron; utility.
 <screenshot>
 <screeninfo>&kcron; utility: a small sample of a system's cronjobs as
-shown through the &kde; <acronym>GUI</acronym>&GUI;.</screeninfo>
+shown through the &tde; <acronym>GUI</acronym>&GUI;.</screeninfo>
 <mediaobject>
 <imageobject>
 <imagedata fileref="kcron_to_be_printed.png"
diff --git a/doc/tdeprint/theory.docbook b/doc/tdeprint/theory.docbook
index 7b137f1c3..8bdce1ea5 100644
--- a/doc/tdeprint/theory.docbook
+++ b/doc/tdeprint/theory.docbook
@@ -564,12 +564,12 @@ internet and printed.</para>
 
 <!--
 <sect2>
-<title>&CUPS;, &IPP; and &kde;</title>
+<title>&CUPS;, &IPP; and &tde;</title>
 
 <para>&CUPS; is the most advanced implementation of &IPP; on all &OS;
 platforms.  That makes &CUPS; a crucial ally to help "conquer the
-desktop" for projects like &kde;. &tdeprint; is the best utility to
-make &CUPS; core functionality available to &kde; Desktop
+desktop" for projects like &tde;. &tdeprint; is the best utility to
+make &CUPS; core functionality available to &tde; Desktop
 users.</para>
 
 </sect2> -->
@@ -582,10 +582,10 @@ the network?  You must have been quite impressed if you didn't know in
 advance what to expect.</para>
 
 <para>Imagine you as the administrator of a <quote>LAN</quote>.  For
-testing purposes you fully installed one &kde;/&CUPS; box on your net,
+testing purposes you fully installed one &tde;/&CUPS; box on your net,
 complete with a dozen printers configured and functional:
 &PostScript;, LaserJets, InkJets and BubbleJets, and so on.  Your
-&kde; users on that box are very happy, they can print like never
+&tde; users on that box are very happy, they can print like never
 before, <quote>ringing all the bells and whistles</quote> of every
 printer.  It took you 2 hours to make everything run perfectly... and
 now all the other 100 users on the network want the same.  Two hours