From 0ef0bc641a7b1e7bb3a26118e077d7aa2d854e60 Mon Sep 17 00:00:00 2001
From: tpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>
Date: Sun, 21 Aug 2011 01:43:11 +0000
Subject: Convert remaining references to kde3 (e.g. in paths) to trinity

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kpilot@1248408 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
---
 Documentation/ConduitProgrammingTutorial/index.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'Documentation/ConduitProgrammingTutorial/index.tex')

diff --git a/Documentation/ConduitProgrammingTutorial/index.tex b/Documentation/ConduitProgrammingTutorial/index.tex
index aed082e..66b17f3 100644
--- a/Documentation/ConduitProgrammingTutorial/index.tex
+++ b/Documentation/ConduitProgrammingTutorial/index.tex
@@ -147,7 +147,7 @@ From your system's point of view, a conduit is a shared library which is loaded
 on demand by KPilot. This means that as long as you don't do a sync, the conduit will not 
 be in memory. Once a hotsync is initiated, kpilotDaemon (the process running in 
 the background that does the actual sync) loads the conduit, let's say its name 
-is "malconduit" and it is installed as /opt/kde3/lib/kde3/libmalconduit.so. It 
+is "malconduit" and it is installed as /opt/trinity/lib/trinity/libmalconduit.so. It 
 then calls the function \code{init\_libmalconduit} (the name after init\_ is the 
 filename of the library), which needs to return a pointer to an instance 
 of a \class{KLibFactory} subclass. 
-- 
cgit v1.2.3

