From d4e929fce4c64bc3d93f053f7274a7bfe4ee2dcd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lubo=C5=A1=20Lu=C5=88=C3=A1k?= Date: Mon, 14 Jan 2008 10:12:20 +0000 Subject: [PATCH] Fix typo. svn path=/trunk/KDE/kdebase/workspace/; revision=761263 --- NOTES_4_0 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NOTES_4_0 b/NOTES_4_0 index 60cad76df2..7b36ead261 100644 --- a/NOTES_4_0 +++ b/NOTES_4_0 @@ -241,7 +241,7 @@ plugins from KWin would essentially require KWin to become Compiz. == Why add compositing support to KWin when Compiz is better ? == -There can be different ideas about what better means, but regardless of that, to main aim of KWin +There can be different ideas about what better means, but regardless of that, the main aim of KWin is not to replace Compiz. Many users have asked for compositing support in KDE, and, as explained in 'Why not Compiz?', the best way to achieve that is considered to be adding compositing support to KWin. KWin aims to provide compositing support, focusing on providing useful compositing