Part 1 of 2 of kdm rename

4 files changed, 235 insertions, 235 deletions

diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.am b/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.am
index d54600f7b69..bd0d1eb0c27 100644
--- a/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.am
+++ b/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.am
@@ -1,4 +1,4 @@
 KDE_LANG = en_GB
 SUBDIRS = $(AUTODIRS)
-KDE_DOCS = kdm
+KDE_DOCS = tdm
 KDE_MANS = AUTO
diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.in b/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.in
index eea41964b53..d9e7e8726f1 100644
--- a/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.in
+++ b/tde-i18n-en_GB/docs/tdebase/kdm/Makefile.in
@@ -30,7 +30,7 @@ POST_INSTALL = :
 NORMAL_UNINSTALL = :
 PRE_UNINSTALL = :
 POST_UNINSTALL = :
-subdir = docs/tdebase/kdm
+subdir = docs/tdebase/tdm
 DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
@@ -188,7 +188,7 @@ KDE_LANG = en_GB
 #>- SUBDIRS = $(AUTODIRS)
 #>+ 1
 SUBDIRS =.
-KDE_DOCS = kdm
+KDE_DOCS = tdm
 KDE_MANS = AUTO
 #>- all: all-recursive
 #>+ 1
@@ -204,9 +204,9 @@ $(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
 #>- 	      exit 1;; \
 #>- 	  esac; \
 #>- 	done; \
-#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/kdm/Makefile'; \
+#>- 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/tdm/Makefile'; \
 #>- 	cd $(top_srcdir) && \
-#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/kdm/Makefile
+#>- 	  $(AUTOMAKE) --gnu  docs/tdebase/tdm/Makefile
 #>+ 12
 	@for dep in $?; do \
 	  case '$(am__configure_deps)' in \
@@ -216,10 +216,10 @@ $(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
 	      exit 1;; \
 	  esac; \
 	done; \
-	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/kdm/Makefile'; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/tdm/Makefile'; \
 	cd $(top_srcdir) && \
-	  $(AUTOMAKE) --gnu  docs/tdebase/kdm/Makefile
-	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/kdm/Makefile.in
+	  $(AUTOMAKE) --gnu  docs/tdebase/tdm/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/tdm/Makefile.in
 .PRECIOUS: Makefile
 Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
 	@case '$?' in \
@@ -525,28 +525,28 @@ uninstall-am:
 .NOEXPORT:
 
 #>+ 2
-KDE_DIST=kdmrc-ref.docbook Makefile.in index.docbook Makefile.am index.cache.bz2 
+KDE_DIST=tdmrc-ref.docbook Makefile.in index.docbook Makefile.am index.cache.bz2 
 
 #>+ 24
-index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) kdmrc-ref.docbook index.docbook 
+index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) tdmrc-ref.docbook index.docbook 
 	@if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi
 
 docs-am: index.cache.bz2
 
 install-docs: docs-am install-nls
-	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm
 	@if test -f index.cache.bz2; then \
-	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/; \
-	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/; \
+	echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/; \
+	$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/; \
 	elif test -f  $(srcdir)/index.cache.bz2; then \
-	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/; \
-	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/; \
+	echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/; \
+	$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/; \
 	fi
-	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/common
-	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/common
+	-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/common
+	$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/common
 
 uninstall-docs:
-	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm
+	-rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm
 
 clean-docs:
 	-rm -f index.cache.bz2
@@ -554,21 +554,21 @@ clean-docs:
 
 #>+ 13
 install-nls:
-	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm
-	@for base in kdmrc-ref.docbook index.docbook ; do \
-	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/$$base ;\
-	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/$$base ;\
+	$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm
+	@for base in tdmrc-ref.docbook index.docbook ; do \
+	  echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/$$base ;\
+	  $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/$$base ;\
 	done
 
 uninstall-nls:
-	for base in kdmrc-ref.docbook index.docbook ; do \
-	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kdm/$$base ;\
+	for base in tdmrc-ref.docbook index.docbook ; do \
+	  rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/tdm/$$base ;\
 	done
 
 
 #>+ 5
 distdir-nls:
-	for file in kdmrc-ref.docbook index.docbook ; do \
+	for file in tdmrc-ref.docbook index.docbook ; do \
 	  cp $(srcdir)/$$file $(distdir); \
 	done
 
@@ -582,10 +582,10 @@ force-reedit:
 	      exit 1;; \
 	  esac; \
 	done; \
-	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/kdm/Makefile'; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  docs/tdebase/tdm/Makefile'; \
 	cd $(top_srcdir) && \
-	  $(AUTOMAKE) --gnu  docs/tdebase/kdm/Makefile
-	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/kdm/Makefile.in
+	  $(AUTOMAKE) --gnu  docs/tdebase/tdm/Makefile
+	cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdebase/tdm/Makefile.in
 
 
 #>+ 21
diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook b/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
index 8a207a0ffa8..c0c5a7e2a2a 100644
--- a/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
+++ b/tde-i18n-en_GB/docs/tdebase/kdm/index.docbook
@@ -1,10 +1,10 @@
 <?xml version="1.0" ?>
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
 "dtd/kdex.dtd" [
-  <!ENTITY kappname "&kdm;">
+  <!ENTITY kappname "&tdm;">
   <!ENTITY package "tdebase">
-  <!ENTITY kdmrc "<filename
->kdmrc</filename
+  <!ENTITY tdmrc "<filename
+>tdmrc</filename
 >">
   <!ENTITY XDMCP "<acronym
 >XDMCP</acronym
@@ -12,7 +12,7 @@
   <!ENTITY xdm "<application
 >xdm</application
 >">
-  <!ENTITY kdmrc-ref SYSTEM "kdmrc-ref.docbook">
+  <!ENTITY tdmrc-ref SYSTEM "tdmrc-ref.docbook">
   <!ENTITY % addindex "INCLUDE">
   <!ENTITY % British-English "INCLUDE"
 > <!-- change language only here -->
@@ -21,7 +21,7 @@
 <book lang="&language;">
 <bookinfo>
 <title
->The &kdm; Handbook</title>
+>The &tdm; Handbook</title>
 
 <authorgroup>
 <author
@@ -85,7 +85,7 @@
 
 <abstract>
 <para
->This document describes &kdm; the &kde; Display Manager. &kdm; is also known as the <quote
+>This document describes &tdm; the &kde; Display Manager. &tdm; is also known as the <quote
 >Login Manager</quote
 >.</para>
 </abstract>
@@ -94,7 +94,7 @@
 <keyword
 >KDE</keyword>
 <keyword
->kdm</keyword>
+>tdm</keyword>
 <keyword
 >xdm</keyword>
 <keyword
@@ -110,9 +110,9 @@
 >Introduction</title>
 
 <para
->&kdm; provides a graphical interface that allows you to log in to a system. It prompts for login (username) and password, authenticates the user and starts a <quote
+>&tdm; provides a graphical interface that allows you to log in to a system. It prompts for login (username) and password, authenticates the user and starts a <quote
 >session</quote
->. &kdm; is superior to &xdm;, the X Display Manager, in a number of ways.</para>
+>. &tdm; is superior to &xdm;, the X Display Manager, in a number of ways.</para>
 
 </chapter>
 
@@ -120,7 +120,7 @@
 <!-- * Just enough config to get it to run and login to KDE 
      * Adding more session types (GNOME, etc)
      * Adding other customizations to XSession (ssh/gpg-agent, etc)
-     * Further customization to KDM (via the kcontrol module, and by 
+     * Further customization to TDM (via the kcontrol module, and by 
        hand)
      * XDMCP by query
      * XDMCP by broadcast
@@ -201,14 +201,14 @@
 ><command
 >startx</command
 ></userinput
-> on the commandline should start X, with a &kde; session. The next task is to try &kdm;.</para>
+> on the commandline should start X, with a &kde; session. The next task is to try &tdm;.</para>
 
 <para
 >As <systemitem class="username"
 >root</systemitem
 >, type <userinput
 ><command
->kdm</command
+>tdm</command
 ></userinput
 > at the prompt.</para>
 
@@ -225,7 +225,7 @@
 
 <note>
 <para
->This is a quick guide to getting up and running only. You probably will want to customise &kdm; further, for example, to hide the names of the system accounts, to allow further sessions, and much more. Please read through the rest of this manual to find out how to do these things.</para>
+>This is a quick guide to getting up and running only. You probably will want to customise &tdm; further, for example, to hide the names of the system accounts, to allow further sessions, and much more. Please read through the rest of this manual to find out how to do these things.</para>
 </note>
 
 </chapter>
@@ -237,7 +237,7 @@
 > 
 
 <para
->The user interface to &kdm; consists of two dialogue boxes. The main dialogue box has these controls:</para>
+>The user interface to &tdm; consists of two dialogue boxes. The main dialogue box has these controls:</para>
 
 <itemizedlist
 > 
@@ -266,7 +266,7 @@
 <para
 >A <guilabel
 >Menu</guilabel
-> drop-down box that allows &kdm; to be used to start sessions with various different window managers or desktop environments installed on the system.</para>
+> drop-down box that allows &tdm; to be used to start sessions with various different window managers or desktop environments installed on the system.</para>
 </listitem>
 
 <listitem>
@@ -333,7 +333,7 @@
 <para
 >(Optionally on local displays) A <guimenuitem
 >Console Mode</guimenuitem
-> item that terminates the currently running &X-Server; and leaves you alone with a console login. &kdm; will resume the graphical login if nobody is logged in at the console for some time. To make this work, you need to use the local@&lt;console&gt; syntax in the <filename
+> item that terminates the currently running &X-Server; and leaves you alone with a console login. &tdm; will resume the graphical login if nobody is logged in at the console for some time. To make this work, you need to use the local@&lt;console&gt; syntax in the <filename
 >Xservers</filename
 > file (see comments in that file).</para>
 </listitem>
@@ -398,39 +398,39 @@
 >OK</guibutton
 > button initiates the selected action; pressing the <guibutton
 >Cancel</guibutton
-> button returns to the main &kdm; dialogue box. </para>
+> button returns to the main &tdm; dialogue box. </para>
 
 </chapter>
 
 <!-- *********************************************************************** -->
-<chapter id="configuring-kdm">
+<chapter id="configuring-tdm">
 <title
->Configuring &kdm;</title>
+>Configuring &tdm;</title>
 
 <para
->This chapter assumes that &kdm; is already up and running on your system, and that you simply want to change its behaviour in some way.</para>
+>This chapter assumes that &tdm; is already up and running on your system, and that you simply want to change its behaviour in some way.</para>
 
 <para
->When &kdm; starts up, it reads its configuration from the folder <filename class="directory"
->$TDEDIR/share/config/kdm/</filename
+>When &tdm; starts up, it reads its configuration from the folder <filename class="directory"
+>$TDEDIR/share/config/tdm/</filename
 > (this may be <filename class="directory"
->/etc/kde3/kdm/</filename
+>/etc/kde3/tdm/</filename
 > or something else on your system).</para>
 
 <para
->The main configuration file is &kdmrc;; all other files are referenced from there and could be stored under any name anywhere on the system - but usually that would not make much sense for obvious reasons (one particular exception is referencing configuration files of an already installed &xdm; - however when a new &kdm; is installed, it will import settings from those files if it finds an already installed &xdm;).</para>
+>The main configuration file is &tdmrc;; all other files are referenced from there and could be stored under any name anywhere on the system - but usually that would not make much sense for obvious reasons (one particular exception is referencing configuration files of an already installed &xdm; - however when a new &tdm; is installed, it will import settings from those files if it finds an already installed &xdm;).</para>
 
 <para
->Since &kdm; must run before any user is logged in, it is not associated with any particular user. Therefore, it is not possible to have user-specific configuration files; all users share the common &kdmrc;. It follows from this that the configuration of &kdm; can only be altered by those users that have write access to <filename
+>Since &tdm; must run before any user is logged in, it is not associated with any particular user. Therefore, it is not possible to have user-specific configuration files; all users share the common &tdmrc;. It follows from this that the configuration of &tdm; can only be altered by those users that have write access to <filename
 >$<envar
 >TDEDIR</envar
->/share/config/kdm/kdmrc</filename
+>/share/config/tdm/tdmrc</filename
 > (normally restricted to system administrators logged in as <systemitem class="username"
 >root</systemitem
 >).</para>
 
 <para
->You can view the &kdmrc; file currently in use on your system, and you can configure &kdm; by editing this file. Alternatively, you can use the graphical configuration tool provided by the &kcontrolcenter; (under <menuchoice
+>You can view the &tdmrc; file currently in use on your system, and you can configure &tdm; by editing this file. Alternatively, you can use the graphical configuration tool provided by the &kcontrolcenter; (under <menuchoice
 ><guisubmenu
 >System Administration</guisubmenu
 ><guimenuitem
@@ -441,11 +441,11 @@
 >. </para>
 
 <para
->The remainder of this chapter describes configuration of &kdm; via the &kcontrol; module, and the <link linkend="kdm-files"
+>The remainder of this chapter describes configuration of &tdm; via the &kcontrol; module, and the <link linkend="tdm-files"
 >next chapter</link
-> describes the options available in &kdmrc; itself. If you only need to configure for local users, the &kcontrol; module should be sufficient for your needs. If you need to configure remote logins, or have multiple &kdm; sessions running, you will need to read on.</para>
+> describes the options available in &tdmrc; itself. If you only need to configure for local users, the &kcontrol; module should be sufficient for your needs. If you need to configure remote logins, or have multiple &tdm; sessions running, you will need to read on.</para>
 
-<sect1 id="kdm-kcontrol-module">
+<sect1 id="tdm-kcontrol-module">
 <sect1info>
 <authorgroup>
 <author
@@ -476,38 +476,38 @@
 >The Login Manager &kcontrol; Module</title>
 
 <para
->Using this module, you can configure the &kde; graphical login manager, &kdm;. You can change how the login screen looks, who has access using the login manager and who can shutdown the computer.</para>
+>Using this module, you can configure the &kde; graphical login manager, &tdm;. You can change how the login screen looks, who has access using the login manager and who can shutdown the computer.</para>
 
 <note
 ><para
->All settings will be written to the configuration file &kdmrc;, which in it's original state has many comments to help you configure &kdm;. Using this &kcontrol; module will strip these comments from the file. All available options in &kdmrc; are covered in <xref linkend="kdm-files"/>.</para>
+>All settings will be written to the configuration file &tdmrc;, which in it's original state has many comments to help you configure &tdm;. Using this &kcontrol; module will strip these comments from the file. All available options in &tdmrc; are covered in <xref linkend="tdm-files"/>.</para>
 
 <para
->The options listed in this chapter are cross referenced with their equivalents in &kdmrc;. All options available in the &kcontrol; module are also available directly in &kdmrc; but the reverse is not true.</para
+>The options listed in this chapter are cross referenced with their equivalents in &tdmrc;. All options available in the &kcontrol; module are also available directly in &tdmrc; but the reverse is not true.</para
 ></note>
 
 <para
->In order to organise all of these options, this module is divided into several sections: <link linkend="kdmconfig-appearance"
+>In order to organise all of these options, this module is divided into several sections: <link linkend="tdmconfig-appearance"
 ><guilabel
 >Appearance</guilabel
 ></link
->, <link linkend="kdmconfig-font"
+>, <link linkend="tdmconfig-font"
 ><guilabel
 >Font</guilabel
 ></link
->, <link linkend="kdmconfig-background"
+>, <link linkend="tdmconfig-background"
 ><guilabel
 >Background</guilabel
 ></link
->, <link linkend="kdmconfig-shutdown"
+>, <link linkend="tdmconfig-shutdown"
 ><guilabel
 >Shutdown</guilabel
 ></link
->, <link linkend="kdmconfig-users"
+>, <link linkend="tdmconfig-users"
 ><guilabel
 >Users</guilabel
 ></link
-> and <link linkend="kdmconfig-convenience"
+> and <link linkend="tdmconfig-convenience"
 ><guilabel
 >Convenience</guilabel
 ></link
@@ -523,12 +523,12 @@
 > Button. You will then be asked for a superuser password. Entering a correct password will allow you to modify the settings of this module.</para
 ></note>
 
-<sect2 id="kdmconfig-appearance">
+<sect2 id="tdmconfig-appearance">
 <title
 >Appearance</title>
 
 <para
->From this page you can change the visual appearance of &kdm;, &kde;'s graphical login manager.</para>
+>From this page you can change the visual appearance of &tdm;, &kde;'s graphical login manager.</para>
 
 <para
 >The <guilabel
@@ -537,7 +537,7 @@
 ><option
 >GreetString</option
 ></link
-> in &kdmrc;. </para>
+> in &tdmrc;. </para>
 
 <para
 >You can then choose to show either the current system time, a logo or nothing special in the login box. Make your choice in the radio buttons labelled <guilabel
@@ -546,7 +546,7 @@
 ><option
 >LogoArea</option
 ></link
-> in &kdmrc;</para>
+> in &tdmrc;</para>
 
 <para
 >If you chose <guilabel
@@ -568,7 +568,7 @@
 >If you do not specify a logo the default <filename
 >$<envar
 >TDEDIR</envar
->/share/apps/kdm/pics/kdelogo.xpm</filename
+>/share/apps/tdm/pics/kdelogo.xpm</filename
 > will be displayed.</para>
 
 <para
@@ -582,10 +582,10 @@
 ><option
 >GreeterPos</option
 ></link
-> in &kdmrc;.</para>
+> in &tdmrc;.</para>
 
 <para
->While &kde;'s style depends on the settings of the user logged in, the style used by &kdm; can be configured using the <guilabel
+>While &kde;'s style depends on the settings of the user logged in, the style used by &tdm; can be configured using the <guilabel
 >GUI Style:</guilabel
 > and <guilabel
 >Colour Scheme:</guilabel
@@ -597,16 +597,16 @@
 ><option
 >ColorScheme</option
 ></link
-> in &kdmrc; respectively.</para>
+> in &tdmrc; respectively.</para>
 
 <para
 >Below that, you have a dropdown box to choose the language for your login box, corresponding to setting <option
 >Language</option
-> in &kdmrc;.</para>
+> in &tdmrc;.</para>
 
 </sect2>
 
-<sect2 id="kdmconfig-font">
+<sect2 id="tdmconfig-font">
 <title
 >Font</title>
 
@@ -657,7 +657,7 @@
 
 </sect2>
 
-<sect2 id="kdmconfig-background">
+<sect2 id="tdmconfig-background">
 <title
 >Background</title>
 
@@ -856,7 +856,7 @@
 
 </sect2>
 
-<sect2 id="kdmconfig-shutdown">
+<sect2 id="tdmconfig-shutdown">
 <title
 ><guilabel
 >Shutdown</guilabel
@@ -873,19 +873,19 @@
 <para
 ><guilabel
 >Nobody</guilabel
->: No one can shutdown the computer using &kdm;. You must be logged in, and execute a command.</para>
+>: No one can shutdown the computer using &tdm;. You must be logged in, and execute a command.</para>
 </listitem>
 <listitem>
 <para
 ><guilabel
 >Everybody</guilabel
->: Everyone can shutdown the computer using &kdm;.</para>
+>: Everyone can shutdown the computer using &tdm;.</para>
 </listitem>
 <listitem
 ><para
 ><guilabel
 >Only Root</guilabel
->: &kdm; requires that the <systemitem
+>: &tdm; requires that the <systemitem
 >root</systemitem
 > password be entered before shutting down the computer.</para
 ></listitem
@@ -917,12 +917,12 @@
 <para
 >When <guilabel
 >Show boot options</guilabel
-> is enabled, &kdm; will on reboot offer you options for the lilo boot manager. For this feature to work, you will need to supply the correct paths to your <command
+> is enabled, &tdm; will on reboot offer you options for the lilo boot manager. For this feature to work, you will need to supply the correct paths to your <command
 >lilo</command
 > command and to lilo's map file.</para>
 
 
-<sect3 id="kdmconfig-sess">
+<sect3 id="tdmconfig-sess">
 <title
 >Session types</title>
 
@@ -952,7 +952,7 @@
 
 </sect3>
 </sect2>
-<sect2 id="kdmconfig-users">
+<sect2 id="tdmconfig-users">
 <title
 >Users</title>
 
@@ -960,7 +960,7 @@
 >From here you can change the way users are represented in the login window.</para>
 
 <para
->You may disable the user list in &kdm; entirely in the <guilabel
+>You may disable the user list in &tdm; entirely in the <guilabel
 >Show Users</guilabel
 > section. You can choose from:</para>
 <variablelist>
@@ -1028,7 +1028,7 @@
 <para
 >If you choose not to show users, then the login window will be more traditional. Users will need to type their username and password to gain entrance. This is the preferred way if you have many users on this terminal.</para>
 
-<sect3 id="kdmconfig-showusers">
+<sect3 id="tdmconfig-showusers">
 <title
 >To show (and sort) or not to show users</title>
 
@@ -1049,7 +1049,7 @@
 
 </sect3>
 
-<sect3 id="kdmconfig-whichusers">
+<sect3 id="tdmconfig-whichusers">
 <title
 >How to determine which users to show and which users to hide</title>
 
@@ -1081,7 +1081,7 @@
 
 </sect3>
 
-<sect3 id="kdmconfig-select">
+<sect3 id="tdmconfig-select">
 <title
 >Select users</title>
 
@@ -1100,7 +1100,7 @@
 
 </sect3>
 
-<sect3 id="kdmconfig-image">
+<sect3 id="tdmconfig-image">
 <title
 >Images</title>
 
@@ -1115,13 +1115,13 @@
 >Every user on the system can be represented by an image. The image for each user is kept in a file called <filename
 >$<envar
 >TDEDIR</envar
->/share/apps/kdm/pics/users/$<envar
+>/share/apps/tdm/pics/users/$<envar
 >USER</envar
 >.xpm</filename
 >. If there is no such file for a particular user, the file <filename
 >$<envar
 >TDEDIR</envar
->/share/apps/kdm/pics/users/default.xpm</filename
+>/share/apps/tdm/pics/users/default.xpm</filename
 > will be used instead.</para>
 
 <para
@@ -1140,7 +1140,7 @@
 </sect3>
 </sect2>
 
-<sect2 id="kdmconfig-convenience">
+<sect2 id="tdmconfig-convenience">
 <title
 >Convenience</title>
 
@@ -1201,13 +1201,13 @@
 <para
 >You can also choose which user is <quote
 >preselected</quote
-> when &kdm; starts. The default is <guilabel
+> when &tdm; starts. The default is <guilabel
 >None</guilabel
 >, but you can choose <guilabel
 >Previous</guilabel
-> to have &kdm; default to the last successfully logged in user, or you can <guilabel
+> to have &tdm; default to the last successfully logged in user, or you can <guilabel
 >Specify</guilabel
-> a particular user to always be selected from the list. You can also have &kdm; set the focus to the password field, so that when you reach the &kdm; login screen, you can type the password immediately.</para>
+> a particular user to always be selected from the list. You can also have &tdm; set the focus to the password field, so that when you reach the &tdm; login screen, you can type the password immediately.</para>
 
 </sect3>
 
@@ -1217,19 +1217,19 @@
 
 </chapter>
 
-&kdmrc-ref;
+&tdmrc-ref;
 
 <!-- ************************************************************ -->   
-<chapter id="configuring-your-system-for-kdm">
+<chapter id="configuring-your-system-for-tdm">
 <title
->Configuring your system to use &kdm;</title>
+>Configuring your system to use &tdm;</title>
 
 <para
 >This chapter assumes that your system is already configured to run the X Window System, and that you only need to reconfigure it to allow graphical login.</para>
 
-<sect1 id="setting-up-kdm">
+<sect1 id="setting-up-tdm">
 <title
->Setting up &kdm;</title>
+>Setting up &tdm;</title>
 
 <para
 >The fundamental thing that controls whether your computer boots to a terminal prompt (console mode) or a graphical login prompt is the default runlevel. The runlevel is set by the program <application
@@ -1277,10 +1277,10 @@ id:3:initdefault:
 </itemizedlist>
 
 <para
->The first step in configuring your system is to ensure that you can start &kdm; from the command line. Once this is working, you can change your system configuration so that &kdm; starts automatically each time you reboot your system.</para>
+>The first step in configuring your system is to ensure that you can start &tdm; from the command line. Once this is working, you can change your system configuration so that &tdm; starts automatically each time you reboot your system.</para>
 
 <para
->To test &kdm;, you must first bring your system to a runlevel that does not run &xdm;. To do so, issue a command like this:</para>
+>To test &tdm;, you must first bring your system to a runlevel that does not run &xdm;. To do so, issue a command like this:</para>
 
 <screen
 ><command
@@ -1303,7 +1303,7 @@ id:3:initdefault:
 >kde</literal
 >. If you previously used &xdm; successfully, you should not need to make any changes to your <abbrev
 >PAM</abbrev
-> configuration in order to use &kdm;. <filename
+> configuration in order to use &tdm;. <filename
 >/etc/pam.conf</filename
 > or <filename
 >/etc/pam.d/kde</filename
@@ -1316,18 +1316,18 @@ id:3:initdefault:
 >).</para>
 
 <para
->Now it's time for you to test &kdm; by issuing the following command:</para>
+>Now it's time for you to test &tdm; by issuing the following command:</para>
 
 <screen
 ><command
->kdm <option
+>tdm <option
 >-nodaemon</option
 ></command
 >
 </screen>
 
 <para
->If you get a &kdm; login dialogue and you are able to log in, things are going well. The main thing that can go wrong here is that the run-time linker might not find the shared &Qt; or &kde; libraries. If you have a binary distribution of the &kde; libraries, make sure &kdm; is installed where the libraries believe &kde; is installed and try setting some environment variables to point to your &kde; and &Qt; libraries.</para>
+>If you get a &tdm; login dialogue and you are able to log in, things are going well. The main thing that can go wrong here is that the run-time linker might not find the shared &Qt; or &kde; libraries. If you have a binary distribution of the &kde; libraries, make sure &tdm; is installed where the libraries believe &kde; is installed and try setting some environment variables to point to your &kde; and &Qt; libraries.</para>
 
 <para
 >For example:</para>
@@ -1368,14 +1368,14 @@ id:3:initdefault:
 >If you are still unsuccessful, try starting &xdm; instead, to make sure that you are not suffering from a more serious X configuration problem.</para>
 
 <para
->When you are able to start &kdm; successfully, you can start to replace &xdm; by &kdm;. Again, this is distribution-dependent.</para>
+>When you are able to start &tdm; successfully, you can start to replace &xdm; by &tdm;. Again, this is distribution-dependent.</para>
 
 <itemizedlist>
 <listitem>
 <para
 >For &RedHat;, edit <filename
 >/etc/inittab</filename
->, look for the string xdm and replace it with &kdm; (including all paths).</para>
+>, look for the string xdm and replace it with &tdm; (including all paths).</para>
 </listitem>
 <listitem>
 <para
@@ -1383,7 +1383,7 @@ id:3:initdefault:
 >/etc/inittab</filename
 > invokes the shell script <filename
 >/etc/X11/prefdm</filename
->, which is set up to select from amongst several display managers, including &kdm;. Make sure that all the paths are correct for your installation.</para
+>, which is set up to select from amongst several display managers, including &tdm;. Make sure that all the paths are correct for your installation.</para
 > 
 </listitem>
 <listitem>
@@ -1394,7 +1394,7 @@ id:3:initdefault:
 
 <screen
 >. /etc/rc.config
-DISPLAYMANAGER=kdm
+DISPLAYMANAGER=tdm
 export DISPLAYMANAGER</screen>
 </listitem>
 <listitem
@@ -1404,7 +1404,7 @@ export DISPLAYMANAGER</screen>
 > and find the line like this: <screen
 >ttyv8   "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure</screen
 > and edit it to this: <screen
->ttyv8   "/usr/local/bin/kdm -nodaemon"  xterm   on secure</screen>
+>ttyv8   "/usr/local/bin/tdm -nodaemon"  xterm   on secure</screen>
 </para>
 </listitem>
 
@@ -1415,7 +1415,7 @@ export DISPLAYMANAGER</screen>
 </itemizedlist>
 
 <para
->At this stage, you can test &kdm; again by bringing your system to the runlevel that should now run &kdm;. To do so, issue a command like this:</para>
+>At this stage, you can test &tdm; again by bringing your system to the runlevel that should now run &tdm;. To do so, issue a command like this:</para>
 
 <screen
 ><command
@@ -1449,7 +1449,7 @@ export DISPLAYMANAGER</screen>
 ></warning>
 
 <para
->When you reboot your system, you should end up with the graphical &kdm; login dialogue.</para>
+>When you reboot your system, you should end up with the graphical &tdm; login dialogue.</para>
 
 <para
 >If this step is unsuccessful the most likely problem is that the environment used at boot time differs from the environment that you used for testing at the command line. If you are trying to get two versions of KDE to co-exist, be particularly careful that the settings you use for your <envar
@@ -1462,26 +1462,26 @@ export DISPLAYMANAGER</screen>
 
 </chapter>
 
-<chapter id="different-window-managers-with-kdm">
+<chapter id="different-window-managers-with-tdm">
 <title
 >Supporting multiple window managers</title>
 
 <para
->The main dialogue box for &kdm; includes a <guilabel
+>The main dialogue box for &tdm; includes a <guilabel
 >Session Type:</guilabel
 > drop-down box, which allows you to select a window manager to use for your session. This chapter describes the changes that you must make to your configuration files in order to support this feature.</para>
 
 <para
 >The options that appear in the <guilabel
 >Session Type:</guilabel
-> drop-down box are <ulink url="KDM"
+> drop-down box are <ulink url="TDM"
 >configured</ulink
 > by entries in the <literal
->KDM</literal
-> section of &kdmrc;.</para>
+>TDM</literal
+> section of &tdmrc;.</para>
 
 <para
->When you log in using &kdm;, the shell script <filename
+>When you log in using &tdm;, the shell script <filename
 >Xsession</filename
 > is executed. The session type that you select is passed as a command-line argument. (<filename
 >Xsession</filename
@@ -1511,7 +1511,7 @@ export DISPLAYMANAGER</screen>
 >:</para>
 
 <screen
-># now, we see if xdm/gdm/kdm has asked for a specific environment
+># now, we see if xdm/gdm/tdm has asked for a specific environment
 case $# in
 1)
     case $1 in
@@ -1638,9 +1638,9 @@ exec $WINDOWMANAGER
 
 </chapter>
 
-<chapter id="xdmcp-with-kdm">
+<chapter id="xdmcp-with-tdm">
 <title
->Using &kdm; for Remote Logins (&XDMCP;)</title>
+>Using &tdm; for Remote Logins (&XDMCP;)</title>
 
 <para
 >&XDMCP; is the Open Group standard, the <quote
@@ -1662,13 +1662,13 @@ exec $WINDOWMANAGER
 >Other sources of information</title>
 
 <para
->Since &kdm; is descended from &xdm;, the <ulink url="man:xdm"
+>Since &tdm; is descended from &xdm;, the <ulink url="man:xdm"
 >xdm man page</ulink
 > may provide useful background information. For X-related problems try the man pages <ulink url="man:X"
 >X</ulink
 > and <ulink url="man:startx"
 >startx</ulink
->. If you have questions about &kdm; that are not answered by this handbook, take advantage of the fact the &kdm; is provided under the terms of the <abbrev
+>. If you have questions about &tdm; that are not answered by this handbook, take advantage of the fact the &tdm; is provided under the terms of the <abbrev
 >GNU</abbrev
 > General Public Licence: look at the source code. </para>
 
@@ -1680,18 +1680,18 @@ exec $WINDOWMANAGER
 >Credits and Licence</title>
 
 <para
->&kdm; is derived from, and includes code from, &xdm; (C) Keith Packard, MIT X Consortium.</para>
+>&tdm; is derived from, and includes code from, &xdm; (C) Keith Packard, MIT X Consortium.</para>
 
 <para
->&kdm; 0.1 was written by Matthias Ettrich. Later versions till &kde; 2.0.x were written by Steffen Hansen. Some new features for &kde; 2.1.x and a major rewrite for &kde; 2.2.x made by Oswald Buddenhagen.</para>
+>&tdm; 0.1 was written by Matthias Ettrich. Later versions till &kde; 2.0.x were written by Steffen Hansen. Some new features for &kde; 2.1.x and a major rewrite for &kde; 2.2.x made by Oswald Buddenhagen.</para>
 
 <para
->Other parts of the &kdm; code are copyright by the authors, and licensed under the terms of the <ulink url="common/gpl-license.html"
+>Other parts of the &tdm; code are copyright by the authors, and licensed under the terms of the <ulink url="common/gpl-license.html"
 >GNU GPL</ulink
->. Anyone is allowed to change &kdm; and redistribute the result as long as the names of the authors are mentioned.</para>
+>. Anyone is allowed to change &tdm; and redistribute the result as long as the names of the authors are mentioned.</para>
 
 <para
->&kdm; requires the Qt library, which is copyright Troll Tech AS.</para>
+>&tdm; requires the Qt library, which is copyright Troll Tech AS.</para>
 
 <para
 >Documentation contributors: <itemizedlist>
@@ -1737,12 +1737,12 @@ exec $WINDOWMANAGER
 > 
 &underFDL; &underGPL; </chapter>
 
-<appendix id="building-and-installing-kdm">
+<appendix id="building-and-installing-tdm">
 <title
->Building and Installing kdm</title>
+>Building and Installing tdm</title>
 
 <para
->&kdm; is part of the KDE project. The various component parts of the KDE project are broken into sections, called packages. &kdm; is part of the package called tdebase. You can get KDE source code from various Linux and BSD distribution CDs, or by download from <ulink url="http://www.kde.org"
+>&tdm; is part of the KDE project. The various component parts of the KDE project are broken into sections, called packages. &tdm; is part of the package called tdebase. You can get KDE source code from various Linux and BSD distribution CDs, or by download from <ulink url="http://www.kde.org"
 >www.kde.org</ulink
 > or its mirrors. If you have an out-of-date source code tree, you can use one of the KDE cvsup servers to bring it up-to-date whilst using minimal network bandwidth. </para>
 
@@ -1760,7 +1760,7 @@ exec $WINDOWMANAGER
 >If the last few paragraphs seemed like a foreign language, then either you have strayed into an Inappropriate Area of this handbook, or you are about to undergo a Great Learning Experience.</para>
 
 <para
->If you managed to satisfy all of the prerequisites, you are unlikely to have any problems with building and installing tdebase. &kdm; is installed in your <filename
+>If you managed to satisfy all of the prerequisites, you are unlikely to have any problems with building and installing tdebase. &tdm; is installed in your <filename
 >$TDEDIR/bin</filename
 > folder.</para>
 
@@ -1772,7 +1772,7 @@ exec $WINDOWMANAGER
 ></command
 > will <emphasis
 >not</emphasis
-> overwrite your previous &kdm; config files including &kdmrc;.</para
+> overwrite your previous &tdm; config files including &tdmrc;.</para
 ></note>
 
 </appendix>
@@ -1786,7 +1786,7 @@ exec $WINDOWMANAGER
 >greeter</glossterm>
 <glossdef
 ><para
->The greeter is the login dialogue, &ie; the part of &kdm; which the user sees.</para>
+>The greeter is the login dialogue, &ie; the part of &tdm; which the user sees.</para>
 </glossdef>
 </glossentry>
 
diff --git a/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook b/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook
index 18d6a847588..a778a4b0d2f 100644
--- a/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook
+++ b/tde-i18n-en_GB/docs/tdebase/kdm/kdmrc-ref.docbook
@@ -1,20 +1,20 @@
-<!-- generated from ../../kdm/kfrontend/config.def - DO NOT EDIT! -->
+<!-- generated from ../../tdm/kfrontend/config.def - DO NOT EDIT! -->
 
-<chapter id="kdm-files">
+<chapter id="tdm-files">
 <title
->The Files &kdm; Uses for Configuration</title>
+>The Files &tdm; Uses for Configuration</title>
 
 <para
->This chapter documents the files that control &kdm;'s behaviour. Some of this can be also controlled from the &kcontrol; module, but not all.</para>
+>This chapter documents the files that control &tdm;'s behaviour. Some of this can be also controlled from the &kcontrol; module, but not all.</para>
 
 <sect1>
 <title
->&kdmrc; - The &kdm; master configuration file</title>
+>&tdmrc; - The &tdm; master configuration file</title>
 
 <para
 >The basic format of the file is <quote
 >INI-like</quote
->. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. Syntactic errors and unrecognised key/section identifiers cause &kdm; to issue non-fatal error messages.</para>
+>. Options are key/value pairs, placed in sections. Everything in the file is case sensitive. Syntactic errors and unrecognised key/section identifiers cause &tdm; to issue non-fatal error messages.</para>
 
 <para
 >Lines beginning with <literal
@@ -161,13 +161,13 @@
 
 <note
 ><para
->A pristine &kdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend.</para
+>A pristine &tdmrc; is very thoroughly commented. All comments will be lost if you change this file with the kcontrol frontend.</para
 ></note>
 
 
-<sect2 id="kdmrc-general">
+<sect2 id="tdmrc-general">
 <title
->The [General] section of &kdmrc;</title>
+>The [General] section of &tdmrc;</title>
 
 <para
 >This section contains global options that do not fit into any specific section. </para>
@@ -183,7 +183,7 @@
 <para
 >This option exists solely for the purpose of clean automatic upgrades. <emphasis
 >Do not</emphasis
-> change it, you may interfere with future upgrades and this could result in &kdm; failing to run. </para>
+> change it, you may interfere with future upgrades and this could result in &tdm; failing to run. </para>
 </listitem>
 </varlistentry>
 
@@ -194,9 +194,9 @@
 ></term>
 <listitem>
 <para
->If the value starts with a slash (/), it specifies a file to read &X-Server; definitions from; otherwise, it is an &X-Server; definition by itself. See <xref linkend="kdmrc-xservers"/> for the details. </para
+>If the value starts with a slash (/), it specifies a file to read &X-Server; definitions from; otherwise, it is an &X-Server; definition by itself. See <xref linkend="tdmrc-xservers"/> for the details. </para
 ><para
->The default is an &X-Server; definition that is usually reasonable for the system on which &kdm; was built. </para>
+>The default is an &X-Server; definition that is usually reasonable for the system on which &tdm; was built. </para>
 </listitem>
 </varlistentry>
 
@@ -209,7 +209,7 @@
 <para
 >List of Virtual Terminals to allocate to &X-Server;s. For negative numbers the absolute value is used, and the <acronym
 >VT</acronym
-> will be allocated only if the kernel says it is free. If &kdm; exhausts this list, it will allocate free <acronym
+> will be allocated only if the kernel says it is free. If &tdm; exhausts this list, it will allocate free <acronym
 >VT</acronym
 >s greater than the absolute value of the last entry in this list. </para>
 <para
@@ -224,7 +224,7 @@
 ></term>
 <listitem>
 <para
->The filename specified will be created to contain an ASCII representation of the process ID of the main &kdm; process; the PID will not be stored if the filename is empty. </para>
+>The filename specified will be created to contain an ASCII representation of the process ID of the main &tdm; process; the PID will not be stored if the filename is empty. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -237,7 +237,7 @@
 ></term>
 <listitem>
 <para
->This option controls whether &kdm; uses file locking to keep multiple display managers from running onto each other. </para>
+>This option controls whether &tdm; uses file locking to keep multiple display managers from running onto each other. </para>
 <para
 >The default is <quote
 >true</quote
@@ -252,7 +252,7 @@
 ></term>
 <listitem>
 <para
->This names a directory under which &kdm; stores &X-Server; authorisation files while initialising the session. &kdm; expects the system to clean up this directory from stale files on reboot. </para
+>This names a directory under which &tdm; stores &X-Server; authorisation files while initialising the session. &tdm; expects the system to clean up this directory from stale files on reboot. </para
 ><para
 >The authorisation file to be used for a particular display can be specified with the <option
 >AuthFile</option
@@ -271,7 +271,7 @@
 ></term>
 <listitem>
 <para
->This boolean controls whether &kdm; automatically re-reads its configuration files if it finds them to have changed. </para>
+>This boolean controls whether &tdm; automatically re-reads its configuration files if it finds them to have changed. </para>
 <para
 >The default is <quote
 >true</quote
@@ -286,7 +286,7 @@
 ></term>
 <listitem>
 <para
->Additional environment variables &kdm; should pass on to all programs it runs. <envar
+>Additional environment variables &tdm; should pass on to all programs it runs. <envar
 >LD_LIBRARY_PATH</envar
 > and <envar
 >XCURSOR_THEME</envar
@@ -309,7 +309,7 @@
 >PrngdSocket</option
 > and <option
 >PrngdPort</option
->) is running, &kdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). </para
+>) is running, &tdm; will fall back to its own pseudo-random number generator that will, among other things, successively checksum parts of this file (which, obviously, should change frequently). </para
 ><para
 >This option does not exist on Linux and various BSDs. </para>
 <para
@@ -356,7 +356,7 @@
 ></term>
 <listitem>
 <para
->The path to a character device which KDM should read random data from. Empty means to use the system's preferred entropy device if there is one. </para
+>The path to a character device which TDM should read random data from. Empty means to use the system's preferred entropy device if there is one. </para
 ><para
 >This option does not exist on OpenBSD, as it uses the arc4_random function instead. </para>
 <para
@@ -401,10 +401,10 @@
 ></term>
 <listitem>
 <para
->The directory in which &kdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. </para>
+>The directory in which &tdm; should store persistent working data; such data is, for example, the previous user that logged in on a particular display. </para>
 <para
 >The default is <quote
->/var/lib/kdm</quote
+>/var/lib/tdm</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -416,7 +416,7 @@
 ></term>
 <listitem>
 <para
->The directory in which &kdm; should store users' <filename
+>The directory in which &tdm; should store users' <filename
 >.dmrc</filename
 > files. This is only needed if the home directories are not readable before actually logging in (like with AFS). </para>
 <para
@@ -428,12 +428,12 @@
 </sect2>
 
 
-<sect2 id="kdmrc-xdmcp">
+<sect2 id="tdmrc-xdmcp">
 <title
->The [Xdmcp] section of &kdmrc;</title>
+>The [Xdmcp] section of &tdmrc;</title>
 
 <para
->This section contains options that control &kdm;'s handling of &XDMCP; requests. </para>
+>This section contains options that control &tdm;'s handling of &XDMCP; requests. </para>
 
 <variablelist>
 
@@ -444,7 +444,7 @@
 ></term>
 <listitem>
 <para
->Whether &kdm; should listen to incoming &XDMCP; requests. </para>
+>Whether &tdm; should listen to incoming &XDMCP; requests. </para>
 <para
 >The default is <quote
 >true</quote
@@ -459,7 +459,7 @@
 ></term>
 <listitem>
 <para
->This indicates the UDP port number which &kdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. </para>
+>This indicates the UDP port number which &tdm; uses to listen for incoming &XDMCP; requests. Unless you need to debug the system, leave this with its default value. </para>
 <para
 >The default is <quote
 >177</quote
@@ -474,7 +474,7 @@
 ></term>
 <listitem>
 <para
->XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private key to be shared between &kdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. </para>
+>XDM-AUTHENTICATION-1 style &XDMCP; authentication requires a private key to be shared between &tdm; and the terminal. This option specifies the file containing those values. Each entry in the file consists of a display name and the shared key. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -487,12 +487,12 @@
 ></term>
 <listitem>
 <para
->To prevent unauthorised &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is described in <xref linkend="kdmrc-xaccess"/>. </para>
+>To prevent unauthorised &XDMCP; service and to allow forwarding of &XDMCP; IndirectQuery requests, this file contains a database of hostnames which are either allowed direct access to this machine, or have a list of hosts to which queries should be forwarded to. The format of this file is described in <xref linkend="tdmrc-xaccess"/>. </para>
 <para
 >The default is <quote
 >${<envar
 >kde_confdir</envar
->}/kdm/Xaccess</quote
+>}/tdm/Xaccess</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -519,7 +519,7 @@
 ></term>
 <listitem>
 <para
->When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is sometimes confusing, &kdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. </para>
+>When computing the display name for &XDMCP; clients, the name resolver will typically create a fully qualified host name for the terminal. As this is sometimes confusing, &tdm; will remove the domain name portion of the host name if it is the same as the domain name of the local host when this option is enabled. </para>
 <para
 >The default is <quote
 >true</quote
@@ -563,9 +563,9 @@
 </sect2>
 
 
-<sect2 id="kdmrc-shutdown">
+<sect2 id="tdmrc-shutdown">
 <title
->The [Shutdown] section of &kdmrc;</title>
+>The [Shutdown] section of &tdmrc;</title>
 
 <para
 >This section contains global options concerning system shutdown. </para>
@@ -581,7 +581,7 @@
 <para
 >The command to run to halt/poweroff the system. </para
 ><para
->The default is something reasonable for the system on which &kdm; was built, like <command
+>The default is something reasonable for the system on which &tdm; was built, like <command
 >/sbin/shutdown&nbsp;<option
 >-h</option
 >&nbsp;<parameter
@@ -600,7 +600,7 @@
 <para
 >The command to run to reboot the system. </para
 ><para
->The default is something reasonable for the system &kdm; on which was built, like <command
+>The default is something reasonable for the system &tdm; on which was built, like <command
 >/sbin/shutdown&nbsp;<option
 >-r</option
 >&nbsp;<parameter
@@ -655,7 +655,7 @@
 ></term>
 <listitem>
 <para
->Instructs &kdm; to offer LiLo boot options in the shutdown dialogue. </para
+>Instructs &tdm; to offer LiLo boot options in the shutdown dialogue. </para
 ><para
 >Only available on Linux i386 &amp; x86-64. </para>
 <para
@@ -703,12 +703,12 @@
 </sect2>
 
 
-<sect2 id="kdmrc-core">
+<sect2 id="tdmrc-core">
 <title
->The [X-*-Core] section class of &kdmrc;</title>
+>The [X-*-Core] section class of &tdmrc;</title>
 
 <para
->This section class contains options concerning the configuration of the &kdm; backend (core). </para>
+>This section class contains options concerning the configuration of the &tdm; backend (core). </para>
 
 <variablelist>
 
@@ -753,7 +753,7 @@
 ></term>
 <listitem>
 <para
->These options control the behaviour of &kdm; when attempting to open a connection to an &X-Server;. <option
+>These options control the behaviour of &tdm; when attempting to open a connection to an &X-Server;. <option
 >OpenDelay</option
 > is the length of the pause (in seconds) between successive attempts, <option
 >OpenRepeat</option
@@ -778,7 +778,7 @@
 ></term>
 <listitem>
 <para
->How many times &kdm; should attempt to start a <literal
+>How many times &tdm; should attempt to start a <literal
 >foreign</literal
 > display listed in the <filename
 >Xservers</filename
@@ -799,7 +799,7 @@
 ></term>
 <listitem>
 <para
->How many times &kdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. </para>
+>How many times &tdm; should attempt to start up a local &X-Server;. Starting up includes executing it and waiting for it to come up. </para>
 <para
 >The default is <quote
 >1</quote
@@ -814,7 +814,7 @@
 ></term>
 <listitem>
 <para
->How many seconds &kdm; should wait for a local &X-Server; to come up. </para>
+>How many seconds &tdm; should wait for a local &X-Server; to come up. </para>
 <para
 >The default is <quote
 >15</quote
@@ -848,7 +848,7 @@
 <para
 >To discover when <emphasis
 >remote</emphasis
-> displays disappear, &kdm; regularly pings them. <option
+> displays disappear, &tdm; regularly pings them. <option
 >PingInterval</option
 > specifies the time (in minutes) between the pings and <option
 >PingTimeout</option
@@ -869,7 +869,7 @@
 ></term>
 <listitem>
 <para
->Whether &kdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. </para>
+>Whether &tdm; should restart the local &X-Server; after session exit instead of resetting it. Use this if the &X-Server; leaks memory or crashes the system on reset attempts. </para>
 <para
 >The default is <quote
 >false</quote
@@ -914,7 +914,7 @@
 ></term>
 <listitem>
 <para
->Controls whether &kdm; generates and uses authorisation for <emphasis
+>Controls whether &tdm; generates and uses authorisation for <emphasis
 >local</emphasis
 > &X-Server; connections. For &XDMCP; displays the authorisation requested by the display is used; foreign non-&XDMCP; displays do not support authorisation at all. </para>
 <para
@@ -950,7 +950,7 @@
 <para
 >Some <emphasis
 >old</emphasis
-> &X-Server;s re-read the authorisation file at &X-Server; reset time, instead of when checking the initial connection. As &kdm; generates the authorisation information just before connecting to the display, an old &X-Server; would not get up-to-date authorisation information. This option causes &kdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorisation information will be read. </para>
+> &X-Server;s re-read the authorisation file at &X-Server; reset time, instead of when checking the initial connection. As &tdm; generates the authorisation information just before connecting to the display, an old &X-Server; would not get up-to-date authorisation information. This option causes &tdm; to send SIGHUP to the &X-Server; after setting up the file, causing an additional &X-Server; reset to occur, during which time the new authorisation information will be read. </para>
 <para
 >The default is <quote
 >false</quote
@@ -965,7 +965,7 @@
 ></term>
 <listitem>
 <para
->This file is used to communicate the authorisation data from &kdm; to the &X-Server;, using the <option
+>This file is used to communicate the authorisation data from &tdm; to the &X-Server;, using the <option
 >-auth</option
 > &X-Server; command line option. It should be kept in a directory which is not world-writable as it could easily be removed, disabling the authorisation mechanism in the &X-Server;. If not specified, a random name is generated from <option
 >AuthDir</option
@@ -1026,7 +1026,7 @@
 >xconsole</command
 > here). The conventional name for a file used here is <command
 >Xsetup</command
->. See <xref linkend="kdmrc-xsetup"/>. </para>
+>. See <xref linkend="tdmrc-xsetup"/>. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -1043,7 +1043,7 @@
 >root</systemitem
 >) after the user authentication process succeeds. The conventional name for a file used here is <command
 >Xstartup</command
->. See <xref linkend="kdmrc-xstartup"/>. </para>
+>. See <xref linkend="tdmrc-xstartup"/>. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -1060,7 +1060,7 @@
 >root</systemitem
 >) after the session terminates. The conventional name for a file used here is <command
 >Xreset</command
->. See <xref linkend="kdmrc-xreset"/>. </para>
+>. See <xref linkend="tdmrc-xreset"/>. </para>
 <para
 >Empty by default.</para>
 </listitem>
@@ -1075,7 +1075,7 @@
 <para
 >This specifies the session program to be executed (as the user owning the session). The conventional name for a file used here is <command
 >Xsession</command
->. See <xref linkend="kdmrc-xsession"/>. </para>
+>. See <xref linkend="tdmrc-xsession"/>. </para>
 <para
 >The default is <quote
 >${<envar
@@ -1094,7 +1094,7 @@
 <para
 >If the <option
 >Session</option
-> program fails to execute, &kdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had (see <xref linkend="kdmrc-xsession"/>). </para>
+> program fails to execute, &tdm; will fall back to this program. This program is executed with no arguments, but executes using the same environment variables as the session would have had (see <xref linkend="tdmrc-xsession"/>). </para>
 <para
 >The default is <quote
 >${<envar
@@ -1119,7 +1119,7 @@
 >Session</option
 >s. </para
 ><para
->The default depends on the system &kdm; was built on. </para>
+>The default depends on the system &tdm; was built on. </para>
 </listitem>
 </varlistentry>
 
@@ -1140,7 +1140,7 @@
 >.</literal
 > (the current directory) into this entry. </para
 ><para
->The default depends on the system &kdm; was built on. </para>
+>The default depends on the system &tdm; was built on. </para>
 </listitem>
 </varlistentry>
 
@@ -1170,7 +1170,7 @@
 ></term>
 <listitem>
 <para
->When &kdm; is unable to write to the usual user authorisation file ($<envar
+>When &tdm; is unable to write to the usual user authorisation file ($<envar
 >HOME</envar
 >/.Xauthority), it creates a unique file name in this directory and points the environment variable <envar
 >XAUTHORITY</envar
@@ -1189,7 +1189,7 @@
 ></term>
 <listitem>
 <para
->If enabled, &kdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). </para>
+>If enabled, &tdm; will automatically restart a session after an &X-Server; crash (or if it is killed by Alt-Ctrl-BackSpace). Note that enabling this feature opens a security hole: a secured display lock can be circumvented (unless &kde;'s built-in screen locker is used). </para>
 <para
 >The default is <quote
 >false</quote
@@ -1514,7 +1514,7 @@
 >chmod&nbsp;<option
 >600</option
 >&nbsp;<filename
->kdmrc</filename
+>tdmrc</filename
 ></command
 > for obvious reasons. </para>
 <para
@@ -1534,7 +1534,7 @@
 >The default is <quote
 >${<envar
 >kde_datadir</envar
->}/kdm/sessions</quote
+>}/tdm/sessions</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -1564,12 +1564,12 @@
 </sect2>
 
 
-<sect2 id="kdmrc-greeter">
+<sect2 id="tdmrc-greeter">
 <title
->The [X-*-Greeter] section class of &kdmrc;</title>
+>The [X-*-Greeter] section class of &tdmrc;</title>
 
 <para
->This section class contains options concerning the configuration of the &kdm; frontend (greeter). </para>
+>This section class contains options concerning the configuration of the &tdm; frontend (greeter). </para>
 
 <variablelist>
 
@@ -1678,7 +1678,7 @@
 ></term>
 <listitem>
 <para
->The relative coordinates (percentages of the screen size; X,Y) at which the centre of the greeter is put. &kdm; aligns the greeter to the edges of the screen it would cross otherwise. </para>
+>The relative coordinates (percentages of the screen size; X,Y) at which the centre of the greeter is put. &tdm; aligns the greeter to the edges of the screen it would cross otherwise. </para>
 <para
 >The default is <quote
 >50,50</quote
@@ -2069,7 +2069,7 @@
 <para
 >If <option
 >UserList</option
-> is enabled, this specifies where &kdm; gets the images from: </para>
+> is enabled, this specifies where &tdm; gets the images from: </para>
 <variablelist>
 <varlistentry>
 <term
@@ -2128,7 +2128,7 @@
 </variablelist>
 
 <para
->The images can be in any format Qt recognises, but the filename must match &kdm;'s expectations: <literal
+>The images can be in any format Qt recognises, but the filename must match &tdm;'s expectations: <literal
 >.face.icon</literal
 > should be a 48x48 icon, while <literal
 >.face</literal
@@ -2154,7 +2154,7 @@
 >The default is <quote
 >${<envar
 >kde_datadir</envar
->}/kdm/faces</quote
+>}/tdm/faces</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -2312,7 +2312,7 @@
 ></term>
 <listitem>
 <para
->If enabled, &kdm; will automatically start the <command
+>If enabled, &tdm; will automatically start the <command
 >krootimage</command
 > program to set up the background; otherwise, the <option
 >Setup</option
@@ -2342,7 +2342,7 @@
 >The default is <quote
 >${<envar
 >kde_confdir</envar
->}/kdm/backgroundrc</quote
+>}/tdm/backgroundrc</quote
 >.</para>
 </listitem>
 </varlistentry>
@@ -2378,7 +2378,7 @@
 ></term>
 <listitem>
 <para
->This option specifies the maximum time &kdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by a look-alike window on the display. If a grab fails, &kdm; kills and restarts the &X-Server; (if possible) and the session. </para>
+>This option specifies the maximum time &tdm; will wait for the grabs to succeed. A grab may fail if some other X-client has the &X-Server; or the keyboard grabbed, or possibly if the network latencies are very high. You should be cautious when raising the timeout, as a user can be spoofed by a look-alike window on the display. If a grab fails, &tdm; kills and restarts the &X-Server; (if possible) and the session. </para>
 <para
 >The default is <quote
 >3</quote
@@ -2515,12 +2515,12 @@
 ></term>
 <listitem>
 <para
->Enable &kdm;'s built-in <command
+>Enable &tdm;'s built-in <command
 >xconsole</command
->. Note that this can be enabled for only one display at a time. This option is available only if &kdm; was <command
+>. Note that this can be enabled for only one display at a time. This option is available only if &tdm; was <command
 >configure</command
 >d with <option
->--enable-kdm-xconsole</option
+>--enable-tdm-xconsole</option
 >. </para>
 <para
 >The default is <quote
@@ -2536,7 +2536,7 @@
 ></term>
 <listitem>
 <para
->The data source for &kdm;'s built-in <command
+>The data source for &tdm;'s built-in <command
 >xconsole</command
 >. If empty, a console log redirection is requested from <filename
 >/dev/console</filename
@@ -2618,7 +2618,7 @@
 <para
 >Show the <guilabel
 >Console Login</guilabel
-> action in the greeter. For this to work, a console must be configured for this particular display, see <xref linkend="kdmrc-xservers"/>. </para>
+> action in the greeter. For this to work, a console must be configured for this particular display, see <xref linkend="tdmrc-xservers"/>. </para>
 <para
 >The default is <quote
 >true</quote
@@ -2665,12 +2665,12 @@
 
 </sect1>
 
-<sect1 id="kdmrc-xservers">
+<sect1 id="tdmrc-xservers">
 <title
 >Specifying permanent &X-Server;s</title>
 
 <para
->Each specification indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for local &X-Server;s that are started by &kdm;, but &kdm; can manage externally started (<quote
+>Each specification indicates a display which should constantly be managed and which is not using &XDMCP;. This method is typically used only for local &X-Server;s that are started by &tdm;, but &tdm; can manage externally started (<quote
 >foreign</quote
 >) &X-Server;s as well, may they run on the local machine or rather remotely.</para>
 
@@ -2714,12 +2714,12 @@
 >localhost</literal
 > prefix from locally running &XDMCP; displays is <emphasis
 >not</emphasis
-> stripped to make them distinguishable from local &X-Server;s started by &kdm;.</para>
+> stripped to make them distinguishable from local &X-Server;s started by &tdm;.</para>
 
 <para
 >The <replaceable
 >display class</replaceable
-> portion is also used in the display-specific sections. This is useful if you have a large collection of similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display class string for your device. If it does not, you can run &kdm; in debug mode and <command
+> portion is also used in the display-specific sections. This is useful if you have a large collection of similar displays (such as a corral of X terminals) and would like to set options for groups of them. When using &XDMCP;, the display is required to specify the display class, so the manual for your particular X terminal should document the display class string for your device. If it does not, you can run &tdm; in debug mode and <command
 >grep</command
 > the log for <quote
 >class</quote
@@ -2730,7 +2730,7 @@
 >tty</replaceable
 > specifies which text console an &X-Server; is <quote
 >covering</quote
->, so &kdm; knows which console it should monitor for activity after switching to <guilabel
+>, so &tdm; knows which console it should monitor for activity after switching to <guilabel
 >Console login</guilabel
 > to find out when the console session ends. Note that this concept (originating from Solaris) is not perfectly suited for Linux, as there &X-Server;s run on separate virtual terminals and consequently do not actually cover consoles (<command
 >getty</command
@@ -2739,7 +2739,7 @@
 <para
 >The <literal
 >reserve</literal
-> keyword instructs &kdm; to start the display not when &kdm; starts up, but when it is explicitly requested via the command <acronym
+> keyword instructs &tdm; to start the display not when &tdm; starts up, but when it is explicitly requested via the command <acronym
 >FiFo</acronym
 >. If reserve displays are specified, the &kde; menu will have a <guilabel
 >Start New Session</guilabel
@@ -2748,7 +2748,7 @@
 <para
 >The <replaceable
 >server command</replaceable
-> specifies the complete &X-Server; command line, including a display number for secondary displays. When &kdm; starts a session, it sets up authorisation data for the &X-Server;. For local servers, &kdm; passes <command
+> specifies the complete &X-Server; command line, including a display number for secondary displays. When &tdm; starts a session, it sets up authorisation data for the &X-Server;. For local servers, &tdm; passes <command
 ><option
 >-auth</option
 >&nbsp;<filename
@@ -2756,20 +2756,20 @@
 >filename</replaceable
 ></filename
 ></command
-> on the &X-Server;'s command line to point it at its authorisation data. For &XDMCP; displays, &kdm; passes the authorisation data to the &X-Server; via the <quote
+> on the &X-Server;'s command line to point it at its authorisation data. For &XDMCP; displays, &tdm; passes the authorisation data to the &X-Server; via the <quote
 >Accept</quote
 > &XDMCP; message.</para>
 
 </sect1>
 
-<sect1 id="kdmrc-xaccess">
+<sect1 id="tdmrc-xaccess">
 <title
 >&XDMCP; access control</title>
 
 <para
 >The file specified by the <option
 >AccessFile</option
-> option provides information which &kdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to <quote
+> option provides information which &tdm; uses to control access from displays requesting service via &XDMCP;. The file contains four types of entries: entries which control the response to <quote
 >Direct</quote
 > and <quote
 >Broadcast</quote
@@ -2777,7 +2777,7 @@
 >Indirect</quote
 > queries, macro definitions for <quote
 >Indirect</quote
-> entries and entries which control on which network interfaces &kdm; listens for &XDMCP; queries. Blank lines are ignored, <literal
+> entries and entries which control on which network interfaces &tdm; listens for &XDMCP; queries. Blank lines are ignored, <literal
 >#</literal
 > is treated as a comment delimiter causing the rest of that line to be ignored and <literal
 >\</literal
@@ -2796,7 +2796,7 @@
 >Direct</quote
 > queries for a host or pattern, it can be followed by the optional <literal
 >NOBROADCAST</literal
-> keyword. This can be used to prevent a &kdm; server from appearing on menus based on <quote
+> keyword. This can be used to prevent a &tdm; server from appearing on menus based on <quote
 >Broadcast</quote
 > queries.</para>
 
@@ -2811,7 +2811,7 @@
 >CHOOSER</literal
 >, <quote
 >Indirect</quote
-> queries are not forwarded, but instead a host chooser dialogue is displayed by &kdm;. The chooser will send a <quote
+> queries are not forwarded, but instead a host chooser dialogue is displayed by &tdm;. The chooser will send a <quote
 >Direct</quote
 > query to each of the remaining host names in the list and offer a menu of all the hosts that respond. The host list may contain the keyword <literal
 >BROADCAST</literal
@@ -2848,19 +2848,19 @@
 </screen
 > If one or more <literal
 >LISTEN</literal
-> lines are specified, &kdm; listens for &XDMCP; requests only on the specified interfaces. <replaceable
+> lines are specified, &tdm; listens for &XDMCP; requests only on the specified interfaces. <replaceable
 >interface</replaceable
 > may be a hostname or IP address representing a network interface on this machine, or the wildcard <literal
 >*</literal
 > to represent all available network interfaces. If multicast group addresses are listed on a <literal
 >LISTEN</literal
-> line, &kdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0<replaceable
+> line, &tdm; joins the multicast groups on the given interface. For IPv6 multicasts, the IANA has assigned ff0<replaceable
 >X</replaceable
 >:0:0:0:0:0:0:12b as the permanently assigned range of multicast addresses for &XDMCP;. The <replaceable
 >X</replaceable
-> in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope definitions). &kdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. If no <literal
+> in the prefix may be replaced by any valid scope identifier, such as 1 for Node-Local, 2 for Link-Local, 5 for Site-Local, and so on (see IETF RFC 2373 or its replacement for further details and scope definitions). &tdm; defaults to listening on the Link-Local scope address ff02:0:0:0:0:0:0:12b to most closely match the IPv4 subnet broadcast behavior. If no <literal
 >LISTEN</literal
-> lines are given, &kdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a <literal
+> lines are given, &tdm; listens on all interfaces and joins the default &XDMCP; IPv6 multicast group (when compiled with IPv6 support). To disable listening for &XDMCP; requests altogether, a <literal
 >LISTEN</literal
 > line with no addresses may be specified, but using the <literal
 >[Xdmcp]</literal
@@ -2875,7 +2875,7 @@
 >Supplementary programs</title>
 
 <para
->The following programs are run by &kdm; at various stages of a session. They typically are shell scripts. </para>
+>The following programs are run by &tdm; at various stages of a session. They typically are shell scripts. </para>
 
 <para
 >The Setup, Startup and Reset programs are run as <systemitem class="username"
@@ -2884,7 +2884,7 @@
 >auto</literal
 > if the session results from an automatic login; otherwise, no arguments are passed to them. </para>
 
-<sect2 id="kdmrc-xsetup">
+<sect2 id="tdmrc-xsetup">
 <title
 >Setup program</title>
 
@@ -2949,7 +2949,7 @@
 </variablelist>
 
 <para
->Note that since &kdm; grabs the keyboard, any other windows will not be able to receive keyboard input. They will be able to interact with the mouse, however; beware of potential security holes here. If <option
+>Note that since &tdm; grabs the keyboard, any other windows will not be able to receive keyboard input. They will be able to interact with the mouse, however; beware of potential security holes here. If <option
 >GrabServer</option
 > is set, <filename
 >Xsetup</filename
@@ -2959,7 +2959,7 @@
 
 </sect2>
 
-<sect2 id="kdmrc-xstartup">
+<sect2 id="tdmrc-xstartup">
 <title
 >Startup program</title>
 
@@ -3054,11 +3054,11 @@
 </variablelist>
 
 <para
->&kdm; waits until this program exits before starting the user session. If the exit value of this program is non-zero, &kdm; discontinues the session and starts another authentication cycle.</para>
+>&tdm; waits until this program exits before starting the user session. If the exit value of this program is non-zero, &tdm; discontinues the session and starts another authentication cycle.</para>
 
 </sect2>
 
-<sect2 id="kdmrc-xsession">
+<sect2 id="tdmrc-xsession">
 <title
 >Session program</title>
 
@@ -3190,7 +3190,7 @@
 
 </sect2>
 
-<sect2 id="kdmrc-xreset">
+<sect2 id="tdmrc-xreset">
 <title
 >Reset program</title>