[gimp-web/testing] Adjust the wording, remove forgotten para



commit a008d15af4ce34d7975463d47ea977f72e7027fb
Author: Alexandre Prokoudine <alexandre prokoudine gmail com>
Date:   Thu May 5 21:23:35 2016 +0300

    Adjust the wording, remove forgotten para

 content/docs/userfaq.md |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)
---
diff --git a/content/docs/userfaq.md b/content/docs/userfaq.md
index 6678588..1bb0591 100644
--- a/content/docs/userfaq.md
+++ b/content/docs/userfaq.md
@@ -182,9 +182,7 @@ We made a preliminary port of GIMP to GTK+3 a few years ago and intend to comple
 
 The reason we prioritize it that way is that users who don't make a heavy use of Wacom tablets on Windows 
can live with GTK+2 based GIMP another year or so. However not providing high bit depth precision for editing 
makes GIMP unusable in professional workflows involving color grading and retouching.
 
-The completion of the GTK+3 port will lead to API/ABI changes: we intend to break a few things to make 
GIMP's architecture cleaner and prepare it for non-destructive editing (a feature currently planned for 
v3.2), and we **have** to break ABI it to make GIMP's custom widgets work with GTK+3.
-
-When completing the GTK+3 port, we will have to break API/ABI compatibility to make GIMP's custom widgets 
work with GTK+3. Moreover, we intend to break a few more things to make GIMP's architecture cleaner and 
prepare it for non-destructive editing (a feature currently planned for v3.2).
+When completing the GTK+3 port, we will have to break API/ABI compatibility to make GIMP's custom widgets 
work with GTK+3. Moreover, we need to break a few more things to make GIMP's architecture cleaner and prepare 
it for non-destructive editing (a feature currently planned for v3.2).
 
 ## Tips
 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]