summaryrefslogtreecommitdiffstats
path: root/tde-i18n-en_GB/docs/tdepim/kalarm
diff options
context:
space:
mode:
Diffstat (limited to 'tde-i18n-en_GB/docs/tdepim/kalarm')
-rw-r--r--tde-i18n-en_GB/docs/tdepim/kalarm/index.docbook18
1 files changed, 9 insertions, 9 deletions
diff --git a/tde-i18n-en_GB/docs/tdepim/kalarm/index.docbook b/tde-i18n-en_GB/docs/tdepim/kalarm/index.docbook
index 25d0de600c2..c11f6c247d8 100644
--- a/tde-i18n-en_GB/docs/tdepim/kalarm/index.docbook
+++ b/tde-i18n-en_GB/docs/tdepim/kalarm/index.docbook
@@ -3923,30 +3923,30 @@ to trigger them when they become due.</para>
<para>What configuration files does &kalarm; use?</para>
</question>
<answer>
-<para>The file <filename>$KDEHOME/share/config/kalarmrc</filename>
+<para>The file <filename>$TDEHOME/share/config/kalarmrc</filename>
holds your &kalarm; preferences.</para>
<para>The calendar file which stores your pending alarms is
-<filename>$KDEHOME/share/apps/kalarm/calendar.ics</filename>, unless
+<filename>$TDEHOME/share/apps/kalarm/calendar.ics</filename>, unless
a different calendar file is specified in the preferences file by a
<parameter>Calendar</parameter> entry in the
<parameter>General</parameter> section.</para>
<para>The calendar file which stores your expired alarms is
-<filename>$KDEHOME/share/apps/kalarm/expired.ics</filename>, unless
+<filename>$TDEHOME/share/apps/kalarm/expired.ics</filename>, unless
a different calendar file is specified in the preferences file by an
<parameter>ExpiredCalendar</parameter> entry in the
<parameter>General</parameter> section.</para>
<para>The calendar file which stores your alarm templates is
-<filename>$KDEHOME/share/apps/kalarm/template.ics</filename>, unless
+<filename>$TDEHOME/share/apps/kalarm/template.ics</filename>, unless
a different calendar file is specified in the preferences file by a
<parameter>TemplateCalendar</parameter> entry in the
<parameter>General</parameter> section.</para>
<para>Details of alarms currently being displayed are stored in the
calendar file
-<filename>$KDEHOME/share/apps/kalarm/displaying.ics</filename>.</para>
+<filename>$TDEHOME/share/apps/kalarm/displaying.ics</filename>.</para>
</answer>
</qandaentry>
@@ -3957,7 +3957,7 @@ calendar file
daemon</application> use?</para>
</question>
<answer>
-<para>The file <filename>$KDEHOME/share/config/kalarmdrc</filename>
+<para>The file <filename>$TDEHOME/share/config/kalarmdrc</filename>
holds your <application>alarm daemon</application> preferences,
together with details of the &kalarm; client application.</para>
</answer>
@@ -4119,14 +4119,14 @@ if your &kde; is installed in <filename>/opt/kde2</filename>:</para>
<warning><para>If you install &kalarm; into a folder different from
where &kde; is installed, it will not run correctly unless you make
its location known to &kde;. To do this, you must prefix the
-<envar>KDEDIRS</envar> environment variable with &kalarm;'s location,
+<envar>TDEDIRS</envar> environment variable with &kalarm;'s location,
each time before you start &kde;.</para>
<para>For example, if &kde; is installed in
-<literal>/opt/kde</literal>, <envar>KDEDIRS</envar> might normally
+<literal>/opt/kde</literal>, <envar>TDEDIRS</envar> might normally
be set to <literal>/etc/opt/kde:/opt/kde</literal>. If you install
&kalarm; into <literal>/usr/local</literal>, you would need to set
-<envar>KDEDIRS</envar> to
+<envar>TDEDIRS</envar> to
<literal>/usr/local:/etc/opt/kde:/opt/kde</literal> before starting
&kde;.</para></warning>