--- CV/bin/cv	2005/08/19 00:19:52	1.54
+++ CV/bin/cv	2005/08/22 00:30:58	1.55
@@ -162,7 +162,7 @@
 
 =item * optimized directory scanning algorithm
 
-The directory scanning in CV plays some tricks that - on most modern
+The directory scanning in CV uses some tricks that - on most modern
 filesystems - makes it possible to detect filetypes faster than stat()'ing
 every file. This makes CV suitable for directories with lots of files
 (10000+).
@@ -171,6 +171,10 @@
 files, device nodes, symlinks and the like, and filetype detection is done
 using the file extension only.
 
+On the positive side, it is usually many orders of magnitude faster than
+traditional scanning techniques (good for directories with 10000 or
+100000+ files).
+
 =item * queuing for all time-consuming background tasks
 
 All tasks, such as unlinking files or generating thumbnails, that can be
@@ -190,17 +194,20 @@
 The time span between the user issuing a command and displaying the new
 image should be as small as possible. CV uses optimized (especially
 for JPEG) loading functions and sacrifices some quality (e.g no gamma
-correction) to achieve this speed.
+correction, although this might change) to achieve this speed.
 
 =item * fast thumbnail creation
 
-Thumbnail creation is crucial for me, so it's better be fast. Thumbnail
-creation for JPEGs has been specially optimized.
+Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both, so
+on modern CPUs, thumbnailing is usually limited by I/O speed. Thumbnail
+creation for JPEGs has been specially optimized and can even take
+advantage of multiple CPUs.
 
 =item * minimum optical clutter
 
 CV has no menus or other user interface elements that take up a lot of
-screen space. The schnauzer windows can also be somewhat crowded.
+screen space (or are useful for beginning users). The schnauzer windows
+can also be somewhat crowded.
 
 The point of an image viewer is viewing images, not a nice GUI. This is
 similar to XV's behaviour.
@@ -211,11 +218,17 @@
 will find most of these keys familiar. If not, CV might be hard to use at
 first, but will be an efficient tool later.
 
+=item * multi-window GUI
+
+CV doesn't force you to use a specific layout, instead it relies on your
+window manager, thus enabling you to chose whatever layout that suits you
+most.
+
 =item * i18n'ed filename handling throughout
 
 As long as glib can recognize your filename encoding (either UTF-8 or
-locale-specific, depending on your settings) and you have the relevant
-fonts, CV will display your filenames correctly.
+locale-specific, depending on the setting of G_BROKEN_FILENAMES) and you
+have the relevant fonts, CV will display your filenames correctly.
 
 =item * extensible through plug-ins