updated readme with the api additions ( both of em! :P )

README.md

@@ -32,7 +32,7 @@ Support & Caveats
 
 Some notes to keep in mind:
 
-- This script's focus is purposely very narrow: only min-width and max-width media queries (along with their media type) are translated to non-supporting browsers. I wanted to keep things simple for filesize, maintenance, and performance, so I've intentionally limited support to queries that are essential to building a mobile-first responsive design. In the future, I may rework things a bit to include a hook for patching-in additional media query features - stay tuned!
+- This script's focus is purposely very narrow: only min-width and max-width media queries and media types (screen, print, etc) are translated to non-supporting browsers. I wanted to keep things simple for filesize, maintenance, and performance, so I've intentionally limited support to queries that are essential to building a mobile-first responsive design. In the future, I may rework things a bit to include a hook for patching-in additional media query features - stay tuned!
 
 - Browsers that natively support CSS3 Media Queries are opted-out of running this script as quickly as possible. In testing for support, I immediately pass browsers that support the window.matchMedia API (such as recent Chrome releases), and Internet Explorer 9+. Internet Explorer 8 and under are immediately flagged for failed media query support. All other browsers are subjected to a quick feature test to determine whether they support media queries or not before proceeding to run the script.
 
@@ -57,6 +57,15 @@ Basically, the script loops through the CSS referenced in the page and runs a re
 
 From there, each query block is appended to the head in order via style elements, and those style elements are enabled and disabled (read: appended and removed from the DOM) depending on how their min/max width compares with the browser width. The media attribute on the style elements will match that of the query in the CSS, so it could be "screen", "projector", or whatever you want. Any relative paths contained in the CSS will be prefixed by their stylesheet's href, so image paths will direct to their proper destination
 
+API Options?
+======
+Sure, a couple:
+
+- respond.update() : rerun the parser (helpful if you added a stylesheet to the page and it needs to be translated)
+- respond.mediaQueriesSupported: set to true if the browser natively supports media queries
+
+
+
 
 Alternatives to this script
 ======