README.txt in sup-0.10.2 vs README.txt in sup-0.11

@@ -10,12 +10,11 @@
 email as an extension of your long-term memory, Sup is for you.
 
 Sup makes it easy to:
 - Handle massive amounts of email.
 
-- Mix email from different sources: mbox files (even across different
-  machines), Maildir directories, IMAP folders, and GMail accounts.
+- Mix email from different sources: mbox files and Maildirs.
 
 - Instantaneously search over your entire email collection. Search over
   body text, or use a query language to combine search predicates in any
   way.
 
@@ -37,11 +36,11 @@
 
 - Scalability to massive amounts of email. Immediate startup and
   operability, regardless of how much amount of email you have.
 
 - Immediate full-text search of your entire email archive, using the
-  Ferret query language. Search over message bodies, labels, from: and
+  Xapian query language. Search over message bodies, labels, from: and
   to: fields, or any combination thereof.
 
 - Thread-centrism. Operations are performed at the thread, not the
   message level. Entire threads are manipulated and viewed (with
   redundancies removed) at a time.
@@ -71,17 +70,10 @@
 
 - Sup doesn't play nicely with other mail clients. If you alter a mail
   source (read, move, delete, etc) with another client Sup will punish
   you with a lengthy reindexing process.
 
-- Support for mbox, Maildir, and IMAP only at this point. No support for
-  POP or mh.
-
-- IMAP support is very slow due mostly to Ruby's IMAP library.  You may
-  consider something like offlineimap to mirror your IMAP folders with
-  local Maildir ones.
-
 - Unix-centrism in MIME attachment handling and in sendmail invocation.
 
 == SYNOPSYS:
 
   0. sup-config
@@ -94,10 +86,10 @@
   load messages from that source and will ask you to run sup-sync
   --changed.
 
 == REQUIREMENTS:
 
- - ferret >= 0.11.6
+ - xapian-full >= 1.1.3.2
  - ncurses >= 0.9.1
  - rmail >= 0.17
  - highline
  - net-ssh
  - trollop >= 1.12