moved caveats in README to the sections to which they apply

README.md

@@ -64,10 +64,6 @@ Vijay can bump the deployment percentage up to 50%. A few more days go by
 and they clean up the last few bugs they found with the "live_postings"
 feature and deploy it to all users.
 
-**Note**: the following is the **intended** use of Arturo. It is not yet
-complete and neither the 1.0 version of the gem nor the Rails 2.3-specific
-branch is available.
-
 ## Installation
 
 ### In Rails 3, with Bundler
@@ -78,6 +74,9 @@ branch is available.
 
     $ gem install arturo --version="~> 1.0"
 
+**Note**: the following two sections describe the **intended** use of
+Arturo with Rails 2. Arturo does not yet have Rails 2 support.
+
 ### In Rails 2, with Bundler
 
     gem 'arturo', :git => 'git://github.com/jamesarosen/arturo.git',
@@ -257,6 +256,12 @@ The latter can be used like so:
 
 #### Caching
 
+**Note**: Arturo does not yet have caching support. Be very careful when
+caching actions or pages that involve feature detection as you will get
+strange behavior when a use who has access to a feature requests a page
+just after one who does not (and vice versa). The following is the
+**intended** support for caching.
+
 Both the `require_feature!` before filter and the `if_feature_enabled` block
 evaluation automatically append a string based on the feature's
 `last_modified` timestamp to cache keys that Rails generates. Thus, you don't