README.md in assetify-0.7.0.rc1 vs README.md in assetify-1.0.0.rc1

@@ -16,22 +16,22 @@
 On any project`s root:
 
     assetify
 
 
-This will create a Jsfile if not found.
+This will create a `Jsfile` if not found.
 
 
 Jsfile
 ======
 
-Just like a Gemfile, but you choose the filetype (or extension) before:
+Like a `Gemfile`, but you choose the filetype (or extension) before:
 
     type "name", "url", <"version"> or <:options>
 
     js "jquery", "http://code.jquery.com/jquery-{VERSION}.min.js", "1.6"
-    js "tipsy", "https://github.com/jaz303/tipsy/.../jquery.tipsy.js"
+    js "tipsy",  "https://github.com/jaz303/tipsy/.../jquery.tipsy.js"
 
 Stylesheets:
 
     css "tipsy", "https://github.com/jaz303/tipsy/.../jquery.tipsy.css"
 
@@ -44,26 +44,26 @@
 
 
 Groups
 ------
 
-When using some compressor/minimizer (Jammit/Smurf...) namespaces come
-in handy:
+Use groups/namespaces to group related assets together:
 
     group "forms" do
-      js "validator", "link"
+      js "validator", url
+      js "textmask",  url
     end
 
 
 This will install as "vendor/assets/javascripts/forms/validator.js"
 
 You can nest groups too:
 
     group "forms" do
-      js "validator", "link"
+      js "validator", url
       group "extra" do
-        js "another", "link"
+        js "another", url
       end
     end
 
 
 Pkgs
@@ -113,9 +113,28 @@
 
 Note: Have in mind that the "link" inside dir/packages *is a regex*
 that returns the *first match* inside the archive. Check out libarchive
 or the pkg.rb source for more info.
 
+
+Global 'a'
+----------
+
+If the link contains the file extension, say: 'fu.com/lib.js'
+You can use just 'a' to specify each asset:
+
+
+    a  "tipsy", "http://...tipsy.js"
+    a  "tipsy", "http://...tipsy.css"
+    a  "video", "http://...video.mpeg"
+
+
+Versions
+--------
+
+Assetify first recognizes the file as text or binary.
+If the file is human readable, try a X.X.Xxx pattern match
+that if found, is used, otherwise use md5sum.
 
 
 Other
 -----