From b1c6ea23c4e7f1939dcade2b86c31c864a2e4e6b Mon Sep 17 00:00:00 2001
From: Timothy Pearson <kb9vqf@pearsoncomputing.net>
Date: Sun, 6 Nov 2011 02:23:21 -0600
Subject: Additional kde to tde renaming

---
 doc/en/index.docbook | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc/en/index.docbook')

diff --git a/doc/en/index.docbook b/doc/en/index.docbook
index d29f63d..95612b5 100644
--- a/doc/en/index.docbook
+++ b/doc/en/index.docbook
@@ -5114,9 +5114,9 @@ Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)</errortext></screen>
 <listitem id="trouble_shooting_unmounting_resource_busy">
 <para><emphasis role="bold">Problem:</emphasis> Unmounting a share fails with the following error message:</para>
 <para><screen><errortext>Could not unmount &#060;PATH&#062;: Device or resource busy</errortext></screen></para>
-<para><emphasis role="bold">Solution:</emphasis> First of all, check that you do not access any directory or file of the share with any program. If this isn't the case, you might have encountered a problem, that is known but not related to &smb4k;. It seems that under certain circumstances (that we could not figure out exactly) kdeinit background processes access files and/or directories of the share and keep them open (&kde; &#060; 3.4). Unmounting is not possible unless you send
+<para><emphasis role="bold">Solution:</emphasis> First of all, check that you do not access any directory or file of the share with any program. If this isn't the case, you might have encountered a problem, that is known but not related to &smb4k;. It seems that under certain circumstances (that we could not figure out exactly) tdeinit background processes access files and/or directories of the share and keep them open (&kde; &#060; 3.4). Unmounting is not possible unless you send
 <screen><prompt>$</prompt> <userinput><command>kill</command> -HUP PID</userinput></screen>
-to each kdeinit instance that has access to the share or its files. Replace PID by the pid of the kdeinit instance. You can find it out by using e. g. &ksysguard;.</para>
+to each tdeinit instance that has access to the share or its files. Replace PID by the pid of the tdeinit instance. You can find it out by using e. g. &ksysguard;.</para>
 <para>Alternatively, you can force the unmounting of the share (not recommended). Highlight the share and use the <menuchoice><guimenu>Shares</guimenu><guimenuitem>Force Unmounting</guimenuitem></menuchoice> menu item or press <keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo>.</para>
 <para><emphasis role="bold">Note:</emphasis> Linux and similar operating systems</para>
 </listitem>
-- 
cgit v1.2.1