From 406bc2a9ec700970c57c5063ec4645e9576bc335 Mon Sep 17 00:00:00 2001
From: Michele Calgaro <michele.calgaro@yahoo.it>
Date: Fri, 28 Sep 2018 14:43:07 +0900
Subject: [PATCH] qt -> tqt conversion: kdeqt -> kdetqt qtkde -> tqtkde
 qtdesigner -> tqtdesigner

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
---
 kspread/DESIGN.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kspread/DESIGN.html b/kspread/DESIGN.html
index 3c43a860c..3cd509e21 100644
--- a/kspread/DESIGN.html
+++ b/kspread/DESIGN.html
@@ -730,7 +730,7 @@ because of the term <i>Tabelle</i> (German, literally means table). The correct
 term is <i>sheet</i> or <i>worksheet</i>. The English version of Microsoft
 uses <i>sheet</i> while the German version uses <i>Tabelle</i>.</p>
 
-<p>Use <a href="http://developer.kde.org/documentation/library/kdeqt/trinityarch/devel-binarycompatibility.htm">d-pointer</a> trick (also known pimpl) whenever possible. Such practice will help when later on
+<p>Use <a href="http://developer.kde.org/documentation/library/kdetqt/trinityarch/devel-binarycompatibility.htm">d-pointer</a> trick (also known pimpl) whenever possible. Such practice will help when later on
 we want to expose the API and need to maintain binary compatibility. But the
 most important thing is to separate the interface and the implementation.
 Furthermore, build time is reduced since modification on the implementation